Page semi-protected

Mickopedia:Rollback

From Mickopedia, the oul' free encyclopedia
(Redirected from Mickopedia:RBK)
Jump to navigation Jump to search

Wikipedia Rollbacker.svg

The rollback user right provides users with a bleedin' button that will revert, with a holy single click, the bleedin' last edit to a feckin' given page, along with any consecutive previous edits made by the same editor to that page. It is used to undo problematic edits such as vandalism. Some counter-vandalism tools also require the user to possess the bleedin' rollback user-right to use the tool.

An editor with rollback user rights will see a feckin' button rollback n edits next to relevant revisions on pages such as their watchlist, on user contributions pages (includin' their own), and on the feckin' edit history of pages.

Rollback is enabled and available to all administrators automatically and can be given to other users upon request, subject to the bleedin' approval of an administrator, for the craic. A user who has been assigned this right explicitly is called a rollbacker, fair play. There are currently 1,014 administrators and 6,636 rollbackers (7,650 total), not includin' global rollbackers and stewards who have been assigned the oul' right across all Wikimedia projects.

Where the oul' followin' text refers to "Standard" rollback, it means the bleedin' usual form of rollback, which does not include the feckin' option to provide an oul' custom edit summary. Whisht now and eist liom. Standard rollback may only be used in certain situations – editors who misuse standard rollback (for example, by usin' it to reverse good-faith edits in situations where an explanatory edit summary would normally be expected) may have their rollback rights removed, the shitehawk. Since rollback is part of the oul' core administrator tools, an admin could be stripped of their administrative privileges entirely to remove those tools.

How it works

Users with rollback permission have extra "rollback" links next to revisions on the recent changes page, page histories, diffs, user contribution pages, and their watchlist:

Clickin' one of these links restores the page to the bleedin' most recent revision that is not made by the oul' revision's author. G'wan now. This appears in the feckin' page history with an oul' generic summary that looks like this:

m Reverted edits by Vandal (talk) to last version by Helpful contributor

A link to the feckin' reverted user's contribution history is provided, so that it may be easily checked for further problematic edits. It does not appear if you are revertin' contributions done by a bleedin' user whose username is not visible havin' been removed or suppressed prior to the feckin' reversion, the result bein':

m Reverted edits by a hidden user to last version by Helpful contributor

If the oul' username is removed after reversion, the default edit summary remains and will need to be deleted separately in its entirety:

m Reverted edits by Grossly offensive or libellous username (talk) to last version by Helpful contributor

All rollbacks are tagged with the feckin' "Rollback" tag in recent changes and page histories.

Technical limitations:

  • The rollback button only appears next to the most recent revision of a feckin' page.
  • If the bleedin' page is edited again before you click the feckin' rollback link, you will get an error message instead.
  • You cannot choose which revision will be restored. Story? It is always the last revision not made by the feckin' author of the most recent revision. This revision may be problematic too, so be careful.
  • If there are multiple consecutive edits to the bleedin' page by the bleedin' same author, they will all be reverted. To remove only some of them, you must revert the bleedin' changes manually.
  • You cannot use rollback on a page which has only been edited by one person, as there would be nothin' to revert to.
  • You cannot use rollback to restore a revision that has been deleted or suppressed. Whisht now and eist liom. Attemptin' to do so will display an error message.
  • Rollback happens immediately; there is no confirmation or preview (although a page is displayed, allowin' you to see the oul' changes you have made).
  • Rollbacks are automatically marked as a bleedin' "minor edit".

Note that methods exist for performin' rollback with non-generic edit summaries – see the feckin' Additional tools section below.

Mobile

For the standard mobile interface, rollback links are only available on the feckin' user contribution page. Story? Users may want to enable the bleedin' advanced mode in settings to be able to access rollback links on the feckin' recent changes page, page histories, and their watchlist. There are no rollback links that can be found on diffs. Another way is to click desktop view below any Mickopedia page. G'wan now. It will redirect you to the desktop interface, which allows you to access rollback links in all of their intended places on Mickopedia pages.

By default, each click on the oul' rollback link requires confirmation, to prevent misuse of rollback on mobile.

When to use rollback

Standard rollback is a fast way of undoin' problematic edits, but it has the oul' disadvantage that only a holy generic edit summary is generated, with no explanation of the bleedin' reason for the bleedin' change. Jesus Mother of Chrisht almighty. For this reason, it is considered inappropriate to use it in situations where an explanatory edit summary would normally be expected. Standard rollback may be used:

  1. To revert obvious vandalism and other edits where the feckin' reason for revertin' is absolutely clear
  2. To revert edits in your own userspace
  3. To revert edits that you have made (for example, edits that you accidentally made)
  4. To revert edits by banned or blocked users in defiance of their block or ban (but be prepared to explain this use of rollback when asked to)
  5. To revert widespread edits (by a misguided editor or malfunctionin' bot) unhelpful to the feckin' encyclopedia, provided that you supply an explanation in an appropriate location, such as at the feckin' relevant talk page[1]

Use of standard rollback for any other purposes – such as revertin' good-faith changes which you happen to disagree with – is likely to be considered misuse of the tool, what? When in doubt, use another method of reversion and supply an edit summary to explain your reasonin'. Also, do not use the default rollback edit summary when it will contain disruptive text which may need to be revision-deleted. An example of this would be to use the bleedin' default edit summary to revert edits made by an account with an unambiguously offensive, insultin', or egregious username that maliciously violates Mickopedia's username policy; the bleedin' offendin' username is automatically added as part of the bleedin' default summary.

The above restrictions apply to standard rollback, and usin' the oul' generic edit summary that is automatically added when the oul' "rollback" button is clicked. Holy blatherin' Joseph, listen to this. If a tool, manual, or alternative "rollback" or reversion method is used to add an appropriate explanatory edit summary (as described in the oul' Additional tools section below), then rollback may be freely used as with any other method of revertin'.

As with any other methods of revertin', when usin' rollback to restore text to an oul' page, ensure that the oul' content bein' restored does not violate any Mickopedia policies.

Administrators may revoke the rollback user right or impose a holy block in response to a user who is persistently failin' to explain their reverts, regardless of the oul' methods or means that are used to perform the actual reversions. However, they should notify or warn the editor sufficiently first, and allow the editor the oul' time and opportunity to respond and explain their reversions before takin' any action – there may be justification of which the feckin' administrator is not aware (such as reversion of edits made by a holy banned user). Similarly, editors who persistently engage in edit warrin' – especially those who have an oul' repeated history of doin' so – may have their rollback permissions revoked, regardless of the oul' methods or means that were used to engage in the behavior, would ye swally that? Additionally, administrators who persistently misuse rollback may have their administrator permissions revoked, and solely in order to remove the rollback user rights from them (although, in practice, such cases would require the intervention of the feckin' Arbitration Committee).

Requestin' rollback rights

To request rollback rights, ask at Mickopedia:Requests for permissions/Rollback or ask one of the feckin' administrators listed here. Any administrator may grant or revoke rollback rights, usin' the bleedin' user rights page.

While there is no fixed requirement, a feckin' request is unlikely to be successful without a contribution history that demonstrates an ability to distinguish well-intentioned edits with minor issues from unconstructive vandalism. Rollback is not for very new users: it is unlikely that editors with under 200 mainspace edits will have their request granted. In addition, editors with a recent history of edit warrin' will often not be granted rollback given concerns of abuse.

If you have been granted rollback rights, you may wish to test it out here.

Accidental use of rollback

Because rollback only takes a single click, without askin' for confirmation, even experienced users may sometimes accidentally click rollback when attemptin' to click somewhere else. I hope yiz are all ears now. If this occurs, simply revert your edit manually, with an edit summary like "Self-revert accidental use of rollback". Bejaysus. You could rollback the oul' rollback, but this can cause confusion for others who look at the oul' page history.

If rollback is used accidentally instead of undo to revert a holy good faith edit, you could take a quick look to see if there is anythin' in the feckin' article you could improve (like a holy typo) and while makin' that edit also add the feckin' reason for reversion. You could also explain the feckin' reason for reversion on the oul' talk page of the oul' user who made the edit or the article talk page if appropriate, Lord bless us and save us. Alternatively you can follow the feckin' rollback with a dummy edit, with an edit summary like "Accidental use of rollback – reason for reversion". C'mere til I tell ya now. This doesn't work with null edits and won't change the edit summary for the rollback edit.

Editors have the feckin' option of installin' any of the feckin' multiple user scripts that enable mandatory confirmation from the bleedin' user before rollin' back an edit. This is enabled by default on mobile devices via the "Require confirmation before performin' rollback on mobile devices" gadget.

It is possible to hide the [rollback] links at Special:Watchlist, where most accidental clicks happen, while leavin' [rollback] links available in other locations (e.g., diffs), Lord bless us and save us. See WP:Customizin' watchlists for instructions.

Additional tools

It is also possible to use rollback with an explanatory edit summary (instead of the oul' default or standard generic edit summary), begorrah. Various editin' tools let you do this; for example, see this list of tools. Jesus, Mary and holy Saint Joseph. To do it manually, copy the URL of the bleedin' rollback link, paste it into your browser's address bar, and append &summary= followed by your desired summary to the oul' end of the URL.

Twinkle and RedWarn/Ultraviolet

Example diff showin' both Twinkle (top line) and rollback (third line)

The patrollin' tools Twinkle and RedWarn/Ultraviolet add links in similar places to the feckin' "rollback" links, and also call them "rollback". Be the holy feck, this is a quare wan. Unlike true rollback, these scripts may be used by any autoconfirmed user. C'mere til I tell yiz. The links are functionally the same, but differ in their choice of edit summaries, and in some small but significant ways differ in their behavior.[2] Twinkle and RedWarn/Ultraviolet offer additional options. Arra' would ye listen to this shite? (Rollbackers usin' either tool will see two "rollback" links, which can be confusin'; see the oul' picture.) In Twinkle, this can be disabled by untickin' every box in the oul' option Show rollback links on these pages: at Twinkle preferences.

Twinkle and RedWarn/Ultraviolet don't have an official version for the standard mobile interface. Jasus. A mobile user can use those tools in full access by switchin' to desktop view.

User scripts

For further customization, you can use the feckin' followin' user scripts:

See also

Notes

  1. ^ See also WP:Requests for arbitration/Ryulong#Rollback.
  2. ^ Namely:
    • Rollback customization scripts, includin' mass-rollback, only work on true rollback.
    • Twinkle/RedWarn/Ultraviolet rollback is shlightly shlower than true rollback and uses two API calls instead of one, would ye believe it? (RedWarn/Ultraviolet will conduct its rollbacks usin' true rollback, if the oul' user is a bleedin' rollbacker, for the craic. Twinkle will still use the bleedin' shlower form even if the feckin' user is a rollbacker.)
    • True rollback is subject to a feckin' shlightly more forgivin' rate limit (as of April 2022, 100 per minute, versus 90 per minute for all other kinds of edits, includin' Twinkle/RedWarn/Ultraviolet rollback).
    • True rollback edits are exempt from the bleedin' edit filter, while Twinkle/RedWarn/Ultraviolet rollback is not (although some edit filters manually exempt it).
http://mickopedia.org/mickify?topic=Wikipedia:RBK
mickopedia.org
crawl=CC-MAIN-2022-49
118360
application/http; msgtype=response
sha1:U3U2NTHXFOUIBI2IGVKXE5CRLTTGJQ3D
<urn:uuid:203779cc-5cc3-453a-883b-54fde0aafb83>
2022-12-04T20:56:56Z
45.32.181.214
text/html
sha1:AFR27YNSATSWDS2KHOM7FJCDYO6UNJT4
<urn:uuid:f2de044b-8084-4a9b-bd29-5be2d8f80a9e>
http://mickopedia.org/mickify?topic=Wikipedia:RBK
response
<urn:uuid:65ec0653-a794-4a9e-b594-666058cc2827>
isPartOf: CC-MAIN-2022-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-73
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/