 | Warning: You take full responsibility for any actions taken using WikiLoop DoubleCheck. You must read and understand all relevant Wikipedia policies and abide by them when using this tool; failure to do so may result in you losing access to the tool or being blocked from editing. |
| WikiLoop DoubleCheck | |
|---|---|
 | |
 WikiLoop DoubleCheck will now show vandalism | |
| Developer(s) | Zainan Zhou |
| Initial release | June 2019 |
| Stable release | 1.2.0-beta
/ August 2, 2019 |
| Written in | JavaScript |
| Platform | Nuxt.js/Vue.js |
| Type | Vandalism detection on Wikipedia |
| License | Apache 2.0 |
| Website | doublecheck |
WikiLoop DoubleCheck (previously WikiLoop Battlefield) is an open-source, crowd-sourced, counter vandalism tool for Wikipedia and Wikidata.org. Built on web technology, it allows a quick launch from either desktop or mobile phone without needing to install resident software. Its objective is to reduce the barrier for patrolling Wikipedia revisions.
Different from other tools like STiki and Huggle, which both require WP:Rollback permission to start using, WikiLoop DoubleCheck intends to move to a tiered, trusted model. That is, just like Wikipedia aspires to be something "anyone can edit", with tiered assets allocated to tiered users, WikiLoop DoubleCheck explores how to grant everyone an ability to review and label a revision with their opinion, while allowing higher tier of trusted editors (such as admins or those with WP:Rollback permissions) to conduct faster and more powerful actions like direct-revert. It allows anonymous users or less-experienced (or not-yet-trusted) users to review and conduct actions with lower risks, while gradually building up their credit using the tool.
You can visit WikiLoop DoubleCheck production. The direct-revert feature is available to advanced users, and is hosted on the Wikimedia Foundation's Cloud VPS.
© MMXXIII Rich X Search. We shall prevail. All rights reserved. Rich X Search