Flagged protection and patrolled revisions Flagged protection · Patrolled revisions · Poll · Implementation · Trial · Reviewing guideline · Reviewers

The following is a working draft of a proposed Wikipedia policy, guideline, or process. The proposal is definitely still in development and under discussion, and has not yet reached the process of gathering consensus for adoption. Thus references or links to this page should not describe it as "policy" nor yet even as a proposal.

This page in a nutshell: Flagged protection provides an alternative to page protection for articles, its use being limited by the protection policy.

Shortcut: WP:FLP

Flagged protection is a specific use of flagged revisions which provides an alternative to the current page protection feature: instead of disallowing editing for certain users, editing is allowed, but those edits must be flagged before being displayed to non-registered readers by default. Flagged protection is part, along with patrolled revisions, of a planned trial implementation on the English Wikipedia.

Contents 1 Overview 2 Description 3 Scope 4 Confirmation and validation 5 See also

[edit] Overview

One of the problems that this proposal is trying to solve is that about 3,000 articles are semi-protected. While 0.1% of English Wikipedia may not seem a huge fraction, semi-protected articles tend to be among the most-read ones, and many readers will also want to make legitimate contributions to them. Anonymous and new users can use the {{editsemiprotected}} template to suggest changes to the page, but it is tedious and daunting for newcomers to use. Thus, while it makes an article somewhat safer from vandalism, semi-protection locks out people who want to contribute in good faith to an article. Therefore, this system is designed to diminish the need for {{editsemiprotected}}, and to allow users to make changes directly to the article without knowing how to use the template.

Similarly, full protection permits only administrators to make consensus-based edits to articles. With full flagged protection, any user could make a change, which editors could then discuss; administrators would flag edits that reflect consensus rather than make them directly.

As noted above, this proposal does not suggest that the current page protection system should be removed, or even fully replaced. Due to the lack of experimental data on flagged protection and solid consensus, it is proposed that as of now the choice of using the traditional page protection or flagged protection is up to administrator's discretion provided that there is a need for page protection on WP:RFPP. Usage policy for flagged protection should be updated as consensus develops if flagged protection is adopted. This implementation is intended to reduce the need for protection on articles, thus making Wikipedia more open for anyone potentially to edit.

[edit] Description

There are three protection levels: semi flag protection, intermediary flag protection and full flag protection, and a usergroup Reviewer. On semi- or intermediately-flag protected pages, the latest confirmed revision is displayed to readers by default. Reviewers can confirm revisions on semi and intermediately flag protected pages. All autoconfirmed users are auto-confirmed on semi flag protected pages , that is, if the latest version of a page is confirmed, a new revision by an autoconfirmed user is automatically confirmed. On intermediately flag protected pages, reviewers are auto-confirmed but not autoconfirmed users who are not reviewers.

The table below resumes this:

Currently available protection levels	Anonymous / Non-Autoconfirmed	Autoconfirmed	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
Semi flagged protection	Can edit; a new edit is visible to registered users, but not to readers by default until confirmed by a 'reviewer'	Can edit; a new edit is visible immediately if the previous version is already confirmed; otherwise not visible to readers by default until confirmed by a 'reviewer'	Can edit; a new edit is visible immediately if the previous version is already confirmed or when the option "confirm this revision" is selected; otherwise left unconfirmed
Intermediary flagged protection	Can edit; a new edit is visible to registered users, but not to readers by default until confirmed by a 'reviewer'
Full flagged protection	Can edit; new edits are visible to registered users, but not to readers by default until validated by an 'administrator'

The process will work like this:

1. Article receives heavy vandalism from anons or users that have yet to be autoconfirmed
2. Someone requests flagged protection on WP:RFPP
3. Administrator activates flagged revisions on the article
4. Anon makes a legitimate edit to the article
5. An autoconfirmed user can decide to confirm or revert the revision made by the anon

In case of abuse, administrators can revoke the reviewer right.

The basic workings of flagged revision can be previewed here, except in this implementation, there is no need to set user rights to flag revisions.

[edit] Scope

The scope of flagged protection is limited by the protection policy. The conditions for semi flagged protection should be the same as to what the current semi-protection policy allows. If the article does not meet the requirements for semi-protection under the current semi-protection policy, then it should not be protected with flagged revisions either. Likewise, only pages that would otherwise be fully protected under the protection policy may be put under full flagged protection. Intermediary flagged protection can be used for articles meeting the requirements for full protection when it doesn't involve a content dispute, or when there is consensus for using it.

The expiry date or the absence of such (indefinite protection) should be considered the same way as for normal protection.

[edit] Confirmation and validation

It has been suggested that Reviewing guideline be merged into this page or section. (Discuss)

Confirming is generally based on the diff between the latest confirmed revision and the new revision. A new revision should be confirmed in general if it doesn't:

1. conflict with the Biographies of Living People policy
2. contain vandalism or patent nonsense
3. contain copyright violations
4. contain legal threats, personal attacks or libel.

Reviewers should take special consideration of the reason given for protection, and make sure to uphold it.

If a revision is not confirmed because of such concerns, the article should be edited^[who?], and unconstructive edits reverted, so that the latest version can be confirmed as soon as possible.

Edits should not generally be left unconfirmed on other grounds, such as containing Original Research, not being neutral, or not being adequately verified, except where this contradicts the policy on the biography of living persons, if the edit introduced many such problems, or the violations are egregious.

On a fully flag protected page, a revision may be validated if there is consensus to validate this revision, or if it is non-controversial compared to the latest validated version.

[edit] See also

• Wikipedia:Flagged protection and patrolled revisions/Implementation for the technical implementation of flagged protection