- 167,703
- 76,303
Hello.
This is a follow-up to my earlier thread about a new script that allows us to efficiently split the edit-patrolling workload among our large staff.
The previous version of the script could only patrol around 5 hours worth of edits, which was obviously not sufficient to be useful.
However, the programmers who originally developed the script have now created a new improved version that reaches much further back in time, as an assignment from Bert Hall of the official Fandom support team.
To reiterate from the previous thread:
A new script has been installed into the wiki that allows administrators and content moderators to mark series of edits as patrolled in a far more efficient manner, which hides them from other administrators and content moderators who use the hide patrolled edits feature.
This will allow us to avoid performing the same work over and over, without knowing if somebody else has already handled the task.
If a certain series of edits has been inspected and deemed harmless, or easily fixed (By adjusting the grammar and structure, adding the 3 required categories, removing visual editor code, changing illogical statistics to unknown ratings, etcetera), we can easily mark them as patrolled, and nobody else will have to handle it.
Of course, this also means a responsibility to not mark edits as patrolled if you are uncertain about whether or not they are inaccurate or harmful, or what to do about them, as that will allow other staff members to check them up as well, and such instances should preferably also be handled by asking whoever made the edits to clarify/justify why they were made via their message walls.
In any case, here are some instructions about what you need to do in order to easily install and use the script within this wiki:
STEP 1: INSTALLATION
Here is a page with the full updated script:
https://pastebin.com/VRQ9buqb
Copy all of it to your local personal javascript page. Replace the previous javascript text with this, in case you have the old version installed. However, take care to not replace any other important scripts.
Take note that I have been given instructions that you should not under any circumstances make the script public, only private, and only install it within this wiki, as othervise it might cause a severe strain on the Application Programming Interface.
To simplify things, here are all of the relevant personal JS pages. You can click on the one belonging to yourself, click edit, paste the text, and save, in order to access the script:
https://vsbattles.fandom.com/wiki/User:Azathoth_the_Abyssal_Idiot/common.js
https://vsbattles.fandom.com/wiki/User:Ryukama/common.js
https://vsbattles.fandom.com/wiki/User:A6colute/common.js
https://vsbattles.fandom.com/wiki/User:KamiYasha/common.js
https://vsbattles.fandom.com/wiki/User:Promestein/common.js
https://vsbattles.fandom.com/wiki/User:The_Everlasting/common.js
https://vsbattles.fandom.com/wiki/User:Matthew_Schroeder/common.js
https://vsbattles.fandom.com/wiki/User:Reppuzan/common.js
https://vsbattles.fandom.com/wiki/User:SomebodyData/common.js
https://vsbattles.fandom.com/wiki/User:WeeklyBattles/common.js
https://vsbattles.fandom.com/wiki/User:The_real_cal_howard/common.js
https://vsbattles.fandom.com/wiki/User:Darkanine/common.js
https://vsbattles.fandom.com/wiki/User:Dragonmasterxyz/common.js
https://vsbattles.fandom.com/wiki/User:Celestial_Pegasus/common.js
https://vsbattles.fandom.com/wiki/User:Dark649/common.js
https://vsbattles.fandom.com/wiki/User:Soldier_Blue/common.js
https://vsbattles.fandom.com/wiki/User:Monarch_Laciel/common.js
https://vsbattles.fandom.com/wiki/User:Kaltias/common.js
https://vsbattles.fandom.com/wiki/User:ThePerpetual/common.js
https://vsbattles.fandom.com/wiki/User:God-King_Superman77/common.js
https://vsbattles.fandom.com/wiki/User:Burning_Full_Fingers/common.js
https://vsbattles.fandom.com/wiki/User:Fllflourine/common.js
STEP 2: PRACTICAL USAGE
I use the following page to monitor suspicious edits within this wiki, as it hides patrolled edits, which includes those of administrators and content moderators:
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=3000
However, here are some other options, if you prefer:
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=1000
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=2000
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=4000
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=5000
Every morning when I wake up, I first check the notifications for discussion thread replies, and after I am temporarily finished, I then click on the above bookmark, and open all of the potentially suspicious edit histories in separate tabs via the "hist" buttons, along with any new blog posts and their replies, new discussion threads that may need my attention, and the occasional character talk page addition.
There are usually 70-95 tabs to open in the first batch, but there are obviously lots more of them later in the day.
I always write down the time that I left off previously in a personal tablet notepad function, so I know where I should start, and which new edits that I need to inspect in the history sections.
If there is a regular editor who as good as always seems to know what he or she is doing, such as LazyHunter, I tend to filter them away, as they do not need supervision, and there are regrettably not enough hours in the day to check up absolutely everything, so I currently have to focus on the most important parts instead.
In any case, when checking the difference between a series of edits, there should now appear a "Mass Patrol" button that you can click in order to make sure that other staff members do not perform the same work.
However, do not use the old "Mark as patrolled" option, as it will both load slower and only mark this single edit as patrolled, rather than all recent previous ones for the page as well. This will recurrently cause it to show up in the recent changes page anyway.
In addition, Bert Hall told me that he had to remove an old script in order to not conflict with the new one, so it is possible that the old option has ceased to function altogether at this point.
I will supply some screencaptures below that illustrate what I mean in a more easily understood manner.
There used to be a "Fast patrolling" button as well, for when there was only a single edit to inspect, but it has been removed, likely due to being redundant.
IMPORTANT NOTE: Only bureaucrats, administrators, and content moderators are supposed to install this script.
This is a follow-up to my earlier thread about a new script that allows us to efficiently split the edit-patrolling workload among our large staff.
The previous version of the script could only patrol around 5 hours worth of edits, which was obviously not sufficient to be useful.
However, the programmers who originally developed the script have now created a new improved version that reaches much further back in time, as an assignment from Bert Hall of the official Fandom support team.
To reiterate from the previous thread:
A new script has been installed into the wiki that allows administrators and content moderators to mark series of edits as patrolled in a far more efficient manner, which hides them from other administrators and content moderators who use the hide patrolled edits feature.
This will allow us to avoid performing the same work over and over, without knowing if somebody else has already handled the task.
If a certain series of edits has been inspected and deemed harmless, or easily fixed (By adjusting the grammar and structure, adding the 3 required categories, removing visual editor code, changing illogical statistics to unknown ratings, etcetera), we can easily mark them as patrolled, and nobody else will have to handle it.
Of course, this also means a responsibility to not mark edits as patrolled if you are uncertain about whether or not they are inaccurate or harmful, or what to do about them, as that will allow other staff members to check them up as well, and such instances should preferably also be handled by asking whoever made the edits to clarify/justify why they were made via their message walls.
In any case, here are some instructions about what you need to do in order to easily install and use the script within this wiki:
STEP 1: INSTALLATION
Here is a page with the full updated script:
https://pastebin.com/VRQ9buqb
Copy all of it to your local personal javascript page. Replace the previous javascript text with this, in case you have the old version installed. However, take care to not replace any other important scripts.
Take note that I have been given instructions that you should not under any circumstances make the script public, only private, and only install it within this wiki, as othervise it might cause a severe strain on the Application Programming Interface.
To simplify things, here are all of the relevant personal JS pages. You can click on the one belonging to yourself, click edit, paste the text, and save, in order to access the script:
https://vsbattles.fandom.com/wiki/User:Azathoth_the_Abyssal_Idiot/common.js
https://vsbattles.fandom.com/wiki/User:Ryukama/common.js
https://vsbattles.fandom.com/wiki/User:A6colute/common.js
https://vsbattles.fandom.com/wiki/User:KamiYasha/common.js
https://vsbattles.fandom.com/wiki/User:Promestein/common.js
https://vsbattles.fandom.com/wiki/User:The_Everlasting/common.js
https://vsbattles.fandom.com/wiki/User:Matthew_Schroeder/common.js
https://vsbattles.fandom.com/wiki/User:Reppuzan/common.js
https://vsbattles.fandom.com/wiki/User:SomebodyData/common.js
https://vsbattles.fandom.com/wiki/User:WeeklyBattles/common.js
https://vsbattles.fandom.com/wiki/User:The_real_cal_howard/common.js
https://vsbattles.fandom.com/wiki/User:Darkanine/common.js
https://vsbattles.fandom.com/wiki/User:Dragonmasterxyz/common.js
https://vsbattles.fandom.com/wiki/User:Celestial_Pegasus/common.js
https://vsbattles.fandom.com/wiki/User:Dark649/common.js
https://vsbattles.fandom.com/wiki/User:Soldier_Blue/common.js
https://vsbattles.fandom.com/wiki/User:Monarch_Laciel/common.js
https://vsbattles.fandom.com/wiki/User:Kaltias/common.js
https://vsbattles.fandom.com/wiki/User:ThePerpetual/common.js
https://vsbattles.fandom.com/wiki/User:God-King_Superman77/common.js
https://vsbattles.fandom.com/wiki/User:Burning_Full_Fingers/common.js
https://vsbattles.fandom.com/wiki/User:Fllflourine/common.js
STEP 2: PRACTICAL USAGE
I use the following page to monitor suspicious edits within this wiki, as it hides patrolled edits, which includes those of administrators and content moderators:
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=3000
However, here are some other options, if you prefer:
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=1000
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=2000
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=4000
https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=5000
Every morning when I wake up, I first check the notifications for discussion thread replies, and after I am temporarily finished, I then click on the above bookmark, and open all of the potentially suspicious edit histories in separate tabs via the "hist" buttons, along with any new blog posts and their replies, new discussion threads that may need my attention, and the occasional character talk page addition.
There are usually 70-95 tabs to open in the first batch, but there are obviously lots more of them later in the day.
I always write down the time that I left off previously in a personal tablet notepad function, so I know where I should start, and which new edits that I need to inspect in the history sections.
If there is a regular editor who as good as always seems to know what he or she is doing, such as LazyHunter, I tend to filter them away, as they do not need supervision, and there are regrettably not enough hours in the day to check up absolutely everything, so I currently have to focus on the most important parts instead.
In any case, when checking the difference between a series of edits, there should now appear a "Mass Patrol" button that you can click in order to make sure that other staff members do not perform the same work.
However, do not use the old "Mark as patrolled" option, as it will both load slower and only mark this single edit as patrolled, rather than all recent previous ones for the page as well. This will recurrently cause it to show up in the recent changes page anyway.
In addition, Bert Hall told me that he had to remove an old script in order to not conflict with the new one, so it is possible that the old option has ceased to function altogether at this point.
I will supply some screencaptures below that illustrate what I mean in a more easily understood manner.
There used to be a "Fast patrolling" button as well, for when there was only a single edit to inspect, but it has been removed, likely due to being redundant.
IMPORTANT NOTE: Only bureaucrats, administrators, and content moderators are supposed to install this script.