| Description | Highlights revered edits in history pages, contributions, recent changes, and elsewhere |
|---|---|
| Author(s) | Suffusion of Yellow |
| Status | Beta |
| First released | December 6, 2019 |
| Updated | December 6, 2019 |
| Browsers | Tested with Firefox and Chromium. Requires async function support. |
| Skins | Tested with Monobook and Vector |
| Source | User:Suffusion of Yellow/mark-reverted.js |
Mark Reverted helps you sift through pages with large numbers of diffs, by highlighting reverted edits. It works not only on history pages, but also user contributions, recent changes, edit filter logs, and even dramaboards.
Installation
editAdd the line {{subst:iusc|User:Suffusion of Yellow/mark-reverted.js}} to your common.js page.
Activation
editThis script may require hundreds of API calls, so it will not run automatically on every page. To activate it, click on the Mark reverted link under tools.
Uses
editA sneaky IP-hopping vandal leaves behind hundreds of unsourced birthdate changes before being blocked. Most were reverted long ago, but the rest are buried behind other edits, so a script like massRollback is of no use. This script will quickly highlight the ones that need checking.
Other places to try it:
- Recent changes tagged "possible libel or vandalism" (or your favorite tags)
- Recent changes marked as "damaging" by ORES
- Edit filter hits with saved changes (select your favorite filters)
Creating an edit filter? Crowdsource the testing phase: Set the filter to log-only, and wait for a few hundred hits to build up. Go to the log, select "With saved changes only". If the filter has a low false positive rate, Mark Reverted should reveal a sea of (mostly) green, with only a few hits to check manually.
Legend
edit- Live: This revision has the same SHA-1[note 1] as the current revision.
- Reverted: A revision made after this one has the same SHA-1 as one made earlier, but this revision does not share that SHA-1.[note 2]
- Unknown: None of the above.[note 3]
- Error: An error occurred. Perhaps the connection was interrupted, or there is a bug in the script.
Notes
edit- ^ A very small number of revisions may have an incorrect SHA-1 stored in the database. See phab:T239717. The script will give incorrect results on those pages.
- ^ If a revision could be marked both "live" and "reverted", it will always be marked "live"
- ^ Future versions of this script may attempt to analyze the content of these revisions