Page MenuHomePhabricator

User right to autopatrol mw-undo reverts
Open, LowestPublicFeature

Description

Rollbacks (mw-rollback) are always automatically marked as patrolled. (AFAIK) Even if the user in question isn't autopatrolled.

Two suggestions (which don't rule each other out):

  • When performing an undo action, check if the performer has rollback (global or local shouldn't matter) and if so, mark the undo action as patrolled.
  • Create a new user right that autopatrols reverts only.

Event Timeline

https://meta.wikimedia.org/wiki/Wikimedia_Forum#Why_does_global_rollback_include_autopatrol%3F

For the first suggestion, there might be a concern that an undo can contain new content. If this is the case, you could:

  1. Check if the performer has rollback rights and if so
  2. Check if the submitted wikitext matches the preloaded wikitext and if so
  3. Mark the edit as patrolled

Can I comment that this is one user generating this discussion, and at this time it is an unsupported issue. The rights as currently set have been in place for 12 years, and were what would have been considered a consensus at that time. There is no demonstrated issue or community reports of this required change.

DannyS712 changed the task status from Open to Stalled.Jun 30 2020, 11:45 AM
DannyS712 added a subscriber: DannyS712.

Stalling pending evidence that this is desired by the community

I don't see any consensus, so the change cannot be done.

I don't see any consensus, so the change cannot be done.

This is just a feature request for the MediaWiki software. Not a site request.

AlexisJazz changed the task status from Open to Stalled.EditedJul 7 2020, 5:07 PM

Setting the status back to stalled as that is the status that DannyS712 has assigned. Note that @94rain and North8000 replied in the thread on meta and appear to be in favor of this idea. Also, there is no need for consensus to implement this as a feature. Consensus would only be required to add the new right to any user group. It is true though that developer time is slightly more likely to be freed for a feature for which there is already consensus to enable it somewhere. This is a chicken-and-egg problem though, it would be difficult to garner support for using a feature that doesn't exist yet.

Jony changed the subtype of this task from "Task" to "Feature Request".Jul 7 2020, 5:56 PM

As @AlexisJazz said this is a feature request. Now MediaWiki software developer have to think about it.

Aklapper changed the task status from Stalled to Open.Oct 6 2020, 12:20 PM
Aklapper triaged this task as Lowest priority.

Treating this as a software development request, hence removing tag and resetting status.