Community Wishlist Survey 2017/Editing/Review individual edits

Review individual edits

  • Problem: Revisions may persist for long periods of time because they're good edits and no one has a problem with them, or they may persist for long periods of time while being bad edits, simply because no one has noticed them and reverted them. Editors waste time verifying revisions that have already (silently) been verified by other people, while not noticing ones that haven't been reviewed.
  • Who would benefit: Editors, everyone
  • Proposed solution: Have an "upvote" or "reviewed" button next to revisions that indicates that you've looked through the diff and verified that it's a good change. A number on the revision history log will indicate how many people have reviewed it.
  • More comments: This would have no bearing on what revision is shown to viewers or anything like that. It would just be a helpful way to see at a glance which revisions have been checked by real human beings and are considered trustworthy/valid, and which diffs have not been viewed, and may need more attention to catch vandalism or poor quality changes. It's also psychologically similar to the "Thanks" feature, in that people can see that their edits were approved/appreciated by others and they aren't laboring in vain. It would also show editors that the revisions they're undoing were approved by multiple other people, making them think twice before wholesale revert warring. It would also help in finding the original source of subtle vandalism that has gone unnoticed for a while, so it can be reverted.
  • Phabricator tickets:


mw:Help:Patrolled_edits exists. Not sure if what you're asking for is covered at least partially by,,, or other tasks that exist on the subject. Elitre (WMF) (talk) 15:31, 13 November 2017 (UTC)

FlaggedRevs can be configured to work like that. --Tgr (WMF) (talk) 12:13, 18 November 2017 (UTC)

@Omegatron: There are already technical solutions to this (as mentioned above). Do either of those meet your requirements? Kaldari (talk) 19:28, 20 November 2017 (UTC)
Those look similar, but no, not the same. This would not "set those revisions as the default revision to show upon normal page view" or require "a 'patrol' permission", and multiple people could approve the same revision, not a binary approved/unapproved state. — Omegatron (talk) 01:41, 21 November 2017 (UTC)

I agree completely with @Omegatron: that users need a way to know whether edits have or have not been reviewed by someone. A solution for this does exist already—it’s called the RCPatrol flag. Almost 100 wikis use RCPatrol today, but it was turned off on English Wikipedia and many others. @Quiddity: researched this situation recently and assembled a very clear analysis, along with recommendations. It’s an enlightening read.

I strongly recommend that RCPatrol be turned on for English and all other wikis. Once it is on, it will be a simple matter to, for example, implement a filter for Patrolled/Unpatrolled on Recent Changes and Watchlist. The various issues that people had with RCPatrol (such as the ! symbol on Recent Changes, which displeased many) can be addressed easily, in my opinion.

The fact that a technological solution exists already for this will help tremendously with getting it done, but it does not negate the value of this proposal. There are technological, design and community issues that must be worked through in order to turn RCPatrol on. Having community behind such a proposal would make success much more likely.

Omegatron, would RCPatrol solve your problem? If it does, perhaps it might be a good idea to rephrase the Solution section somewhat, to make it more about the general goal, and to retitle the proposal along similar lines. E.g., Have a way for editors to know if an edit has been reviewed. JMatazzoni (WMF) (talk) 20:51, 22 November 2017 (UTC)

Both patrolling and FlaggedRevs can be used coordinate one review per revision (without necessarily changing what revision the reader sees) and both are integrated with the existing patrol/review tools. Neither really supports multiple reviews though. Patrolling can't even store them (it's just a per-revision boolean flag); FlaggedRevs allows multiple reviews (with comments, optionally) per revision but only the last one is exposed in the UI, the rest only show up on Special:Logs. Also since English Wikipedia uses FlaggedRevs for flagged protection already, if you want to allow anyone to review revisions without interfering with that, you'd have to introduce a new review level which would make the configuration and UI more convoluted.

OTOH the requirement to have multiple reviews per revision seems somewhat disconnected from the problem statement. --Tgr (WMF) (talk) 00:12, 24 November 2017 (UTC)


  •   Support --Liuxinyu970226 (talk) 13:04, 28 November 2017 (UTC)
  •   Support Also allows to view the list of reviewers and make a comment? --YFdyh000 (talk) 14:06, 28 November 2017 (UTC)
  •   Support Thomas Obermair 4 (talk) 21:46, 28 November 2017 (UTC)
  •   Support Support what I believe is the principle, noting that in the discussion are hints to several implementations, some using existing infrastructure. The main principle to me, is to enhance cooperation and collective assessment. Currently we have mostly a sequence of individual decisions (one editor writes, one editor patrols, one editor(admin) blocks, and so on. We need more "collective" tools. (Lots of work that-a-way, I'll add no more now) Nabla (talk) 21:22, 30 November 2017 (UTC)
  •   Support User Risk Engineer, (talk) 21:22, 30 November 2017 (UTC)
  •   Support Braveheidi (talk) 07:11, 1 December 2017 (UTC)
  •   Support Krinkle (talk) 19:31, 1 December 2017 (UTC)
  •   Support If it's determining whether an edit constitutes vandalism or not, then really anyone could review it and the old tools could work just fine. But most of the edits that require reviewing (at least in my topic area) are good-faith edits that are more or less subtly misinformed, incompetent or biased, and there is only a small number of editors whose judgement I would trust to spot these flaws. Who has reviewed the edit matters a lot. Uanfala (talk) 01:47, 2 December 2017 (UTC)
  •   Support ديفيد عادل وهبة خليل 2 (talk) 14:22, 2 December 2017 (UTC)
  •   Support Emir of Wikipedia (talk) 16:04, 2 December 2017 (UTC)
  •   Support Joshualouie711 (talk) 02:17, 3 December 2017 (UTC)
  •   Support -- seth (talk) 11:09, 3 December 2017 (UTC)
  •   Oppose Plays into the hands of article owners, making it easier for a person to act as gatekeeper of an article, rejecting any change from an outsider with which he disagrees. Giraffedata (talk) 22:18, 3 December 2017 (UTC)
  •   Support Ciao • Bestoernesto 02:51, 4 December 2017 (UTC)
  •   Support This could also be useful for AI. Doc James (talk · contribs · email) 02:23, 5 December 2017 (UTC)
  •   Support Great idea: perhaps aletter R (or blue thumb up emoji resp. red thumb down) with a number  Klaas `Z4␟` V:  21:39, 6 December 2017 (UTC)
  •   Support Ahm masum (talk) 08:45, 7 December 2017 (UTC)
  •   Neutral Don't like the thumbs-down option; we have enough negative feedback channels that scare new editors already. But I'd like to edit an article without feeling that I'm tacitly approving all the past edits unseen. Is "So-and-so thought this edit useful" then just going to be a milder version of thanking? Would making the thanks record visible on the history page be similar? HLHJ (talk) 06:28, 8 December 2017 (UTC)
  • 15:34, 8 December 2017 (UTC)
  •   Support I like upvoting things! RandomDSdevel (talk) 01:46, 9 December 2017 (UTC)
  •   Oppose, please do not create one more edit patrolling/reviewing system, develop existing ones instead. I think this is feasible with some customised configuration of FlaggedRevisions — NickK (talk) 16:23, 11 December 2017 (UTC)