The proposal is located at Wikipedia:Flag protection and patrolled revisions. |
The three propositions aim to improve our monitoring of vandalism, BLP violations, and other recurrent problems using systems inspired by flagged revisions, patrolled edits and the abuse filter, without affecting editability as is currently the case for page protection, or as it would be for large-scale implementations of strict flagged revisions. It relies on a 'reviewer' usergroup that can be granted automatically, and manually added or removed by administrators, able to flag or patrol articles.
Main page: Wikipedia:Flagged protection/Proposed |
For articles meeting the requirements for protection (defined by the protection policy)[1], flag protection may be used instead of regular protection, that is, instead of entirely preventing editing by unregistered or new users, we allow it, but non-autoconfirmed edits are delayed until reviewed by a reviewer.[2] Classic protection can still be used temporarily in cases of exceptionally high levels of vandalism or unstoppable edit wars. The proposed additional protection levels are:
Summary tables:
Currently available protection levels | Anonymous / Non-Autoconfirmed | Autoconfirmed | Reviewer | Administrator |
---|---|---|---|---|
Semi Protection | Cannot edit | Can edit; edits are immediately visible | ||
Full Protection | Cannot edit | Can edit; edits are visible immediately |
Proposed additional protection levels | Anonymous / Non-Autoconfirmed | Autoconfirmed | Reviewer | Moderator / Administrator |
---|---|---|---|---|
Semi Flag Protection a | Can edit; a new edit is visible to registered users, but not to readers by default until reviewed by a 'reviewer' | Can edit; a new edit is visible immediately if the previous version is already reviewed; otherwise[5]not visible to readers by default until reviewed by a 'reviewer' | Can edit; a new edit is visible immediately if the previous version is already reviewed or when the option "review this revision" is selected[6]; otherwise left unreviewed[7] | |
Full Flag Protection b | Can edit; new edits are visible to registered users, but not to readers by default until validated by a 'moderator' [4] |
For all pages in mainspace, an enhanced system of patrolled revisions can be used. Reviewers can mark a revision patrolled, which has no effect but only to inform that this revision contains no vandalism and satisfy certain other requirements defined by a guideline.[9]
Reviewers have access to Special:UnPatrolledPages (pages that have never been patrolled) and Special:OldPatrolledPages (pages patrolled at least once with unpatrolled latest revision). Those special pages are filterable by category (especially interesting for Category:Living people). A new revision by a reviewer is automatically patrolled when the previous version is.
This system allows to improve the monitoring of pages for vandalism, blp violations, etc, by reducing the number of revisions to check and allow to compare the latest revisions with a previous 'good' version (acting like 'checkpoints').
This system would be entirely independent of flag protection, and would allow to double-check edits by autoconfirmed users to those pages.
Main page: Wikipedia:Deferred revisions |
For pages in mainspace, and possibly other namespaces such as Portal, Category, Template, Wikipedia, Help, File and User, we can use deferred revisions: edits that have been identified as suspect in some respect by an automated system (with customizable filters, like the abuse filter), are delayed until reviewed by a reviewer. Reviewers have access to Special:DeferredRevisions (listing all pages with a deferred revision that has not been canceled), and can cancel the deferral. Basic information on the filter triggered by the edit is given to the user whose edit has been deferred and to reviewers.
Edits are deferred when they match a certain filter, they can cover cases of obvious vandalism, spam, test edits and other potentially harmful edits. Each filter would require consensus to be turned on.
For patrolled revisions and flag protection, the extension FlaggedRevs would be the core of the implementation, but certain modifications, such as adding new special pages and allow deactivation of non-reviewer autoreview are needed.
For deferred revisions, the abuse filter may be the automated system charged to identify and defer suspect edits, but substantial modifications are required to make the collaboration between the two extensions efficient.
This variant of flag protection has been proposed as a trial, see Trial 17.