User:Cenarium/Flagged revisions/New

User groups

1. IP

   Delay before sighing: 18 hours

2. User

   Delay before sighing: 12 hours

3. Autoconfirmed user (automatic, non-removable)

   Delay before sighing: edit: 6 hours, move: indefinite

4. Established user (automatic, removable, assignable by moderators)

   Delay before sighing: edit: 5 minutes, move: 8 hours

5. Surveyor (assignable by administrators)

   Delay before sighing: immediate

   Can sight/un-sight versions

   Access to special pages related to sighted versions

6. Rollbacker (assignable by administrators)

   Rollback

7. Moderator (assignable by administrators)

   Confirm/Un-confirm versions

   Assign established user rights (cannot remove rights)

   Mark a page as stable, as high risk (cannot remove status)

   Bypass certain filters

8. Administrator

   Bypass filters

   Assign above rights 4,5,6,7

   Enable/Disable sighted revisions for an article

   Enable/Disable confirmed revisions for an article

Automatic sighting

• By default, if a surveyor edits an article and the latest version is sighted, the new version will be automatically sighted immediately after the edit.

• For non surveyors, we may use automatic sighting after delay:

• By default, if a non-surveyor edits an article and the latest version is sighted, the new version will be automatically sighted $1 after the edit. Where the delay $1 may depend on the group of the user and the page, and may also be subject to modification by a filter (for example Wikipedia:Abuse filter).

Article status

An article could be 'marked' by a moderator as stable, high risk, etc. And depending on the status of the article, the behavior of automatic and normal sighting would be changed.

• A 'stable' article is an article that is very unlikely to be redirected (especially merged), moved, or nominated for deletion, and where such actions would disrupt or damage Wikipedia. Edits to a stable page could be filtered such that, when a user who is not a moderator moves, redirects or requests deletion of the page (it could be detected with the use of a deletion template or category), then the edit is not automatically sighted and sighting it requires moderator rights.
• An article could be marked as "requiring attention" if it has been recently and persistently subject to vandalism or violations of our policies. Pages requiring attention with edits non manually sighted would be listed to a special page.

Another use of confirmed revisions

In order for a moderator to confirm a revision, the mod must not have edited the article between the latest confirmed revision and the revision to confirm. Administrators could bypass this by removing confirmed revisions from the article, however, especially in disputes, this would be a blatant abuse of sysop rights. This would add an additional security for high risk pages, like system messages and the main page: an edit there needs to be confirmed by another admin before being effective. It would require that confirmed revisions be enabled there by default, and that admins cannot change that.