User Rollbackers

User Rollbackers are a fictional global user-group. The intention was to come up with a fictional global user-group that was based around the extension of the same name. So therefore the idea was a fictional volunteer user-group whose primary task was to quickly revert all edits made by a specific user across all wikis when FANDOM Staff, FANDOM Helpers, and Volunteer Spam Task Force members aren't around to take bigger action against global vandals.

Inspiration
The inspiration for the fictional user-group started sometime in March 2016 when I was researching all the user-group rights that all the user-groups had on FANDOM. I was checking the Special:Listgrouprights page in order to update my own article page that listed all the permissions that each user-group has or had since September 2014. Then I noticed the Userrollback permission that had been added on the list of permissions that FANDOM Utilities had.

There was no description on the special page as to what the permission did, and because the permission had "rollback" in its name, I became curious as to what the permission did. I knew that it must have been a permission that only Utilities should have, but that was literally it. It wasn't too long though before I was told what the permission did. To quickly revert all edits made by a specific user across all wikis.

Less than two months after the permission was added to the Utility user-group, and less than a month after I got the idea for the fictional User Rollback user-group, the permission was removed from the Utility user-group in April 2016. In fact the extension was removed altogether. While it was around, the extension didn't seem to be added anywhere outside FANDOM Community Central.

Despite this all being in 2016, past MediaWiki messages indicate that the extension dated back from June 2015 at the latest. While various archives on GitHub confirm that the extension dated back from December 2011 at the latest. Even though the idea was that the fictional volunteer user-group would be for non-Staff, it is highly unlikely that anyone without Staff or Utility rights would be given access to the user-group, if the user-group existed.

Abilities that the User Rollback user-group has
Since the User Rollback user-group is based around the userrollback extension, it does not have many abilities. In fact most of the abilities currently extended to User Rollbackers aren't permissions that they had at the time of the user-group's creation.

As the User Rollback user-group has "rollback" in its name, and since the user-group is intended to deal with global vandalism against specific global vandals from all affected wikis, I felt that User Rollbackers should have global access to the Rollback permission. However, unlike local Administrators, Assistants, Content Moderators, and Rollbackers, User Rollbackers are only permitted to use their rollback rights on quiet or inactive wikis, and only against obvious spam and vandalism.
 * Rollback

User Rollbackers do not replace or outrank local users with rollback rights. Any users that are part of the User Rollback user-group must have Administrator, Assistant, Content Moderator, and/or Rollback rights on a wiki in order for them to be able to use rollback for the same reasons that a local user with rollback rights would on the said wiki.

User Rollbackers were subsequently granted the ability to delete pages. However, unlike local Administrators and Content Moderators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete pages in case they were unable to delete pages with the Userrollback extension alone.
 * Delete

Since the Userrollback extension is relatively obscure and not widely known, I haven't been able to find any information that can confirm whether or not users with the Userrollback permission would need to have the Delete permission in order to use the extension effectively. Despite having the ability to delete pages, User Rollbackers are only permitted to delete pages if for some reason they run into a page that the Userrollback extension is unable to revert and delete.

User Rollbackers were subsequently granted the ability to delete pages with large histories. However, unlike local Administrators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete pages with large histories in case they were unable to delete pages with large histories with the Userrollback extension, and with the Delete permission alone.
 * Bigdelete

Since the Userrollback extension is relatively obscure and not widely known, I haven't been able to find any information that can confirm whether or not users with the Userrollback permission would need to have the Delete or Bigdelete permissions in order to use the extension effectively. Despite having both the ability to delete pages, and the ability to delete pages with large histories, User Rollbackers are only permitted to delete pages with large histories if for some reason they run into a page that the Userrollback extension is unable to revert and delete, and the page history is too long for the page to be deleted with the Delete permission.

Since User Rollbackers have the ability to delete pages with large histories on all wikis, including those wikis where they have Content Moderator rights, they are still able to delete pages with large histories on those said wikis, although this isn't something that User Rollbackers with local Content Moderator rights were intended to be able to do.

User Rollbackers were subsequently granted the ability to delete article comments. However, unlike local Administrators, Content Moderators, and Discussion Moderators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete article comments in case they were unable to delete article comments with the Userrollback extension alone.
 * Commentdelete

Since the Userrollback extension is relatively obscure and not widely known, I haven't been able to find any information that can confirm whether or not users with the Userrollback permission would need to have the Commentdelete permission in order to use the extension effectively. Despite having the ability to delete article comments, User Rollbackers are only permitted to delete article comments if for some reason they run into anything that the Userrollback extension is unable to revert and delete.

User Rollbackers were subsequently granted the ability to delete comments from blog articles. However, unlike local Administrators and Discussion Moderators, User Rollbackers are actually almost never permitted to use their delete tools. User Rollbackers were granted the ability to delete blog comments in case they were unable to delete blog comments with the Userrollback extension alone.
 * Blog-comments-delete

Since the Userrollback extension is relatively obscure and not widely known, I haven't been able to find any information that can confirm whether or not users with the Userrollback permission would need to have the Blog-comments-delete permission in order to use the extension effectively. Despite having the ability to delete blog comments, User Rollbackers are only permitted to delete blog comments if for some reason they run into anything that the Userrollback extension is unable to revert and delete.

User Rollbackers were subsequently granted the ability to delete message wall messages. However, unlike local Administrators, User Rollbackers are actually almost never permitted to use their message wall delete tools. User Rollbackers were granted the ability to delete message wall messages in case they were unable to delete message wall messages with the Userrollback extension alone.
 * Walladmindelete

Since the Userrollback extension is relatively obscure and not widely known, I haven't been able to find any information that can confirm whether or not users with the Userrollback permission would need to have the Walladmindelete permission in order to use the extension effectively. Despite having the ability to delete message wall messages, User Rollbackers are only permitted to delete message wall messages if for some reason they run into anything that the Userrollback extension is unable to revert and delete.

FANDOM Staff, FANDOM Helpers, and Volunteer Spam Task Force members have the ability to view IP actions across all wikis.
 * Multilookup

User Rollbackers were subsequently granted the ability to view IP actions across all wikis, so that they would have an easier time finding and reverting edits made by a specific IP address across all wikis.

FANDOM Helpers and Volunteer Spam Task Force members have the ability to view a user's contributions across all wikis. FANDOM Staff were subsequently granted the ability sometime between December 2014 and 2015.
 * Lookupcontribs

User Rollbackers were subsequently granted the ability to view a user's contributions across all wikis, so that they would have an easier time finding and reverting edits made by a specific user across all wikis.

FANDOM Utilities previously had the ability to quickly revert all edits made by a specific user across all wikis. However the ability was removed from the Utility user-group in April 2016, and the extension was removed from the FANDOM network. Despite this, User Rollbackers still have access to the ability to this day, because if they didn't still have the ability, the fictional user-group would no longer serve their central purpose.
 * Userrollback

User Rollbackers are able to quickly revert all edits made by a specific user across all wikis whenever they find a user that has engaged in cross-wiki vandalism, and there isn't a VSTF, Helper, or Staff around to take bigger action against the global vandal.

User Rollbackers don't use their Userrollback abilities for any other reason than dealing with global spam and vandalism. They do not use their Userrollback abilities against local spam or vandalism. And they do not use their Userrollback abilities against any global spammers or vandals, or troublesome users that have made any edits that aren't pure spam or vandalism.

Abilities that User Rollbackers previously had
Since the User Rollback user-group is based around the userrollback extension, it isn't supposed to have many abilities as a standalone group. Most of the abilities that were previously included in the User Rollback user-group were removed after it was decided that they weren't relevant to the User Rollback user-group, they allowed them to do things or bypass restrictions that they weren't intended to be able to do or be able to bypass, or they allowed User Rollbackers to do things or bypass restrictions on local wikis that went against the best wishes of their communities.

User Rollbackers were subsequently given the ability to edit semi-protected pages in case their account was less than 4 days old. However they lost the ability in September 2017 after it was decided that being able to edit semi-protected pages was irrelevant to User Rollbackers.
 * Autoconfirmed

Since the odds of User Rollback rights being granted to an account that was less than 4 days old were very small. And even if such odds did happen, User Rollbackers would be able to temporarily flag themselves as a Content Moderator or Assistant, should they be unable to revert vandalism on a semi-protected page.

User Rollbackers were subsequently given the ability to bypass CAPTCHAs in case their account was less than 4 days old. However they lost the ability in September 2017 after it was decided that being able to bypass CAPTCHAs was irrelevant to User Rollbackers.
 * Skipcaptcha

Since the odds of User Rollback rights being granted to an account that was less than 4 days old were very small. And even if such odds did happen, User Rollbackers would be able to temporarily flag themselves as an Assistant, should they ever need to bypass a CAPTCHA. Otherwise they could simply check the confirmation box.

User Rollbackers were subsequently given the ability to use higher limits in API queries. However they lost the ability in May 2017 after it was decided that being able to use higher limits in API queries was irrelevant to User Rollbackers. And even if it were relevant, User Rollbackers would be able to temporarily flag themselves as an Assistant, should they ever need to use higher limits in API queries.
 * Apihighlimits


 * Tboverride


 * Noratelimit


 * Ipblock-exempt


 * Proxyunbannable


 * Deleteinterfacetrusted


 * Phalanxexempt


 * Unblockable

Groups that User Rollbackers are able to add and remove from their own account

 * Assistants


 * Content Moderators

Groups that User Rollbackers were previously able to add or remove from other accounts

 * Rollbackers

Groups that User Rollbackers were previously able to add to their own account

 * Rollbackers

Groups that User Rollbackers were previously able to remove from their own account

 * Rollbackers


 * User Rollbackers