Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Wikipedia:Flagged protection and patrolled revisions

From Wikipedia, the free encyclopedia
This page is currently inactive and is retained forhistorical reference.
Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as thevillage pump.
Shortcut
Pending changes
Interface:Pages with pending edits ·Pages under pending changes ·Pending changes log ·
Documentation:Main talk ·Reviewing guideline ·Reviewing talk ·Protection policy ·Testing ·Statistics
Summary information for editors
  1. Current status - Pending changes (level 1) was re-enabled on December 1st, 2012 by community consensus according to the2012 RFC.
  2. Logged in users – Logged in users (or users choosing to view pending changes) will see all edits as usual (unless the relevant setting has been changed in theirpreferences). All edits will still be added to the wiki and inappropriate edits must still be reverted or fixed as usual.
  3. Logged out users – Until checked for obvious vandalism or superseded by appropriate editing, edits by new and unregistered users to "pending changes protected" pages will not be seen by users who are not logged in until approved. Edits byautoconfirmed users are approved automatically at level 1 when the prior revision is approved.
  4. Policy – See thepending changes usage policy and theguideline on reviewing
  5. Reviewer rightsBecome a reviewer!.
  6. Support and testing – Test page:Wikipedia:Pending changes/Testing. Bugs: Report them atWT:PC. For more information visit theIRC channel:#wikipedia-en-pcconnect
  7. Provide feedback and suggestion – Feedback page:Wikipedia talk:Pending changes. Your feedback and suggestions are appreciated.
The two month trial of flagged protection, renamed to pending changes, ended in 2010, and was reactivated in 2012 on a permanent basis. SeeWikipedia:Pending changes. Patrolled revisions was not implemented.

This page describes two new features approved for trial, based on the concept offlagged revisions. The first feature isflagged protection, since renamed topending changes, which uses flagging as an optional alternative tosemi protection andfull protection. When a page is protected in this way by an administrator, the latest flagged revision is shown to readers by default. The second feature ispatrolled revisions, which uses flagging passively to coordinate the monitoring of articles, but has no effect on the version viewed by readers.

Background

[edit]

The "Flagged Revisions" feature was initially developed for the German Wikipedia (de.wikipedia.org) so thatwikis could review contributions by users before allowing their publication. In 2007 and 2008, flagged revisions have been proposed to better handle several issues faced by the English Wikipedia (en.wikipedia.org), such asvandalism and violations of ourpolicy on living people. Aggressive use of the feature was rejected by the English Wikipedia community, essentially for too drastically reducing the ability of anyone to edit Wikipedia. In late 2008 and beginning 2009, more specific implementations were discussed in order to reach a compromise, and finally the joint proposal for flagged protection and patrolled revisions reached consensus for a trial on the English Wikipedia.

Description

[edit]

Those features are principally aimed to address the lack of flexibility of our current protection mechanisms and the relative inefficiency of our basic monitoring tools such asrecent changes andwatchlists. Flagged protection allows more granularity than the classic page protection system: while the latter prevents any editing, flagged protection allows editing but requires review before changes by new or unregistered users are displayed on the version viewed by readers. Like classic page protection, it can be enabled only by administrators, for a fixed period of time or indefinitely. Patrolled revisions provide a way to review edits similar to Flagged Revisions but without affecting the version viewed by readers, thus it is a passive way to monitor articles much more efficient than recent changes and watchlists which tend to become ineffectual with the huge volume of editing and articles on the English Wikipedia. While recent changes and watchlists display bare edits with no possibility of organization of the reviewing at the individual or community level, patrolled revisions allow users to review changes made to an article since the latest patrolled revision, and patrol new revisions when appropriate; and thus allow to coordinate and optimize the reviewing efforts.

Pending changes (flagged protection)

[edit]
Main page:Wikipedia:Pending changes
This feature was formerly known as "Flagged protection"

Pending changes introduces new protection levels which can be used as an alternative to regular semi-protection and full-protection. In terms of policy, the conditions for using pending changes protection at level 1 are the same as for using semi-protection, as determined by theprotection policy, and the condition for using level 2 are the same as for using full-protection. Disputes should still be handled by full protection[1]. Classic protection can and should still be used, for example in cases of exceptionally high levels of vandalism, where using flagged protection would be counter-productive. The full spectrum of protection levels are shown in the following table:

Protection levels and their impact on various Wikipediauser groups[α]
FProtection levelNew or unregistered editorsConfirmedExtended confirmedTemplate editor[β]AdminInterface adminAppropriate for...
Editing
NoneNormal editingThe vast majority of pages.[γ]
Pending changesCan edit
Changes are only visible to logged-in users until reviewed by apending changes reviewer or administrator.[δ]
Can edit
Changes are visible to everyone if there aren't any unreviewed pending changes. Otherwise, they are only visible to logged-in users until reviewed by a pending changes reviewer or administrator.[δ]
Can edit
If there are any unreviewed pending changes, the administrators will be required to review them before they can edit the page.[δ]
Infrequently edited pages with high levels of vandalism,BLP violations, edit-warring, or other disruption from unregistered and new users.
 SemiCannot editNormal editingPages that have been persistently vandalized by anonymous and newly registered users. Some highly visible templates and modules.
Extended confirmedCannot editNormal editingContentious topics authorized byArbCom, pages where semi-protection has failed, orhigh-risk templates where template protection would be too restrictive.
 TemplateCannot editNormal editingHigh-risk or very-frequently used templates and modules.Some high-risk pages outside oftemplate space.
 FullCannot editCan edit[ε]Pages with persistent disruption from extended confirmed accounts.
 OfficeCan edit[ζ]Pages that the Foundation has determined to be exceptionally sensitive.
 Cascade[η]Can editParticularly visible pages, such as theMain Page, to prevent vandalism to pages that aretranscluded onto them.
 Interface[θ]Cannot editNormal editingScripts, stylesheets, and similar objects fundamental to operation of the site or that are in other editors'user spaces.
Creating pages
NoneCannot create[ι][κ]Can createThe vast majority of page titles.[γ]
 Create[λ]Cannot createAdjustable
It may be applied to neither, either, or both groups.
Can createPages that have been repeatedly and problematically re-created.
Moving pages
NoneCannot moveCan moveThe vast majority of pages.[γ]
 MoveCannot moveAdjustable
It may be applied to neither, either, or both groups.
Can movePages that have been the subject of move wars. Pages that are edit-protected are usually also move-protected at the same level.
Uploading files
NoneCannot upload[κ]Can uploadThe vast majority of file names.[γ]
 UploadCannot uploadAdjustable
It may be applied to neither, either, or both groups
Can uploadFiles that have been repeatedly uploaded after deletion
Advantages over the current system
  • Even though their edits are not visible immediately to readers, unregistered and new users can edit pages protected by pending changes, while they cannot edit semi-protected pages. So this allows constructive changes while disallowing vandalism and other unconstructive changes.
  • Semi-protection is insufficient in certain cases, especially for articles targeted by persistent vandals or sockpuppets, or subject to extreme BLP violations; these sometimes require full protection. The option to deactivate auto-reviewing for autoconfirmed users who are not reviewers (autoconfirmation) provides a protection level adapted to handle those cases.

Patrolled revisions

[edit]
Main page:Wikipedia:Patrolled revisions

The aim of patrolled revisions is to coordinate and improve the monitoring of all articles, especially biographies of living people. Reviewers can mark a revision patrolled, which has no effect but only to inform that this revision contains no vandalism, no blp violations, and satisfies certain other requirements defined by a guideline. In particular, this does not affect the revision viewed by unregistered users by default, it's still the latest one (unless the article is flag protected). A new revision by a reviewer is automatically patrolled when the previous version is.

Reviewers have access to a special page listing articles that have never been patrolled and a special page listing pages patrolled at least once with an unpatrolled latest revision. They allow respectively to detect never patrolled pages, that may not have been checked for vandalism, blp violations, etc, and monitor changes to patrolled pages, on which vandalism or blp violations may have been inserted since the latest patrol. Those special pages are filterable by category (for example,Category:Living people). It can also be filtered so that only elements on your watchlist appear, and mentions how many users are watching a page.

Currently, the number of edits to articles and in particular BLPs is so large that we don't have the power to check all of them, we have no way to even coordinate our efforts. This system allows us to monitor changes to articles, in particular BLPs, much more efficiently by comparing new edits to previously patrolled revisions. Even if only one edit of 10 is patrolled, it'll allow to bring potential vandalism and BLP violations to the attention of reviewers and so significantly reduce their general visibility.

Patrolled revisions would also allow checking of edits by autoconfirmed users who are not reviewers, to flagged protected pages, as those are generally automatically confirmed when the previous revision is, but would not be automatically patrolled. To avoid work duplication, patrolled revisions are automatically confirmed.

In addition, a special page displays articles withtagged edits that have not been patrolled.

Wikipedia users, page protections, and page edits
 Anonymous,NewAutoconfirmed,ConfirmedReviewerAdministrator
No protectioncan edit;
visible immediately
Patrolled revisionscan edit;
visible immediately;
cannot accept
can edit;
visible immediately;
can accept?
can edit;
visible immediately;
can accept
Pending-changes
level 1 protection
can edit;
visible after accept;
cannot accept
can edit;
visible immediately;
cannot accept
can edit;
visible immediately;
can accept
Pending-changes
level 2 protection
can edit;
visible after accept;
cannot accept
can edit;
visible immediately;
can accept
Semi-protectioncannot editcan edit;
visible immediately
Pending-changes level 2 with Semi-protectioncannot editcan edit;
visible after accept;
cannot accept
can edit;
visible immediately;
can accept
Full protectioncannot editcan edit;
visible immediately
Note: Under pending-changes protections, "visible immediately" assumes no previous pending changes remain to be accepted.

Trial

[edit]
Main pages:Wikipedia:Pending changes andWikipedia:Pending changes/Trial

Consensus has been reached for a two-month trial of flagged protection and patrolled revisions after series of discussions and afinal poll. A trial of flagged protection has been prepared by the Wikimedia Foundation and began on June 15, 2010. At the end of the trial, the Wikipedia community will decide whether to continue or discontinue using flagged protection, and whether to test alternative configurations of flagged revisions. A trial of patrolled revisions is not planned yet.

Implementation

[edit]
Main page:Wikipedia:Flagged protection and patrolled revisions/Implementation

TheWikimedia foundation has set up a team for the development and implementation of those features. The mediawiki extensionFlaggedRevs is the core of the technical implementation for flagged protection; testing was done athttp://flaggedrevs.labs.wikimedia.org/wiki/Main_Page. Patrolled revisions is planned to be developed independently of the FlaggedRevs extension and could not be made available for the upcoming trial.[2]

Notes

[edit]
  1. ^Initially a full flagged protection level, where flagging was restricted to administrators had been proposed but won't be implemented in the trial for simplicity.
  2. ^http://techblog.wikimedia.org/2010/01/flagged-revisions-your-questions-answered/
  1. ^Details about historical protection levels and user groups no longer in use are available atWikipedia:Protection policy § Retired protections.
  2. ^This table assumes that template editors are also extended confirmed, which isalmost always the case for non-bot accounts.
  3. ^abcdThis is the default protection level.
  4. ^abcHowever, if any editors (including unregistered editors) revert all unreviewed pending changes back to the latest accepted version, that revision is automatically accepted and pending changes reviewers and administrators aren't prompted or notified.
  5. ^Only noncontroversial changes or requested changes following an achieved consensus should be performed.
  6. ^Only with the approval from theWikimedia Foundation.
  7. ^Cascade protection extends to all pages that aretranscluded onto the protected page, unless the transcluded page is at the same protection level or higher. Cascade protection can only be applied to pages that are fully or office-protected because otherwise itcreates a workflow flaw.
  8. ^The interface protection level is automatically set by theMediaWiki software to a specific set of pages, such as pages in the MediaWiki namespace, system-wide CSS and JavaScript pages, and personal CSS and JavaScript pages of other users. It is not a protection level that an administrator can manually apply to any page, nor is it a protection level that can be modified on pages currently under interface protection. Because of this, administrators also cannotcascade-protect pages that are Interface-protected.
  9. ^This has been in effectfor unregistered users since 5 December 2005. The restriction wasextended to newly registered users on a six month trial basis starting on 14 September 2017. The extension became permanent on 18 April 2018.
  10. ^abUnder the default no protection, unregistered and newly registered users can still createtalk pages in all namespaces and draft articles in theDraft namespace. For these namespaces, it would therefore be possible for this protection to only apply to unregistered and newly registered users.
  11. ^This form of protection is often also called "salting".

See also

[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Flagged_protection_and_patrolled_revisions&oldid=1315446570"
Categories:

[8]ページ先頭

©2009-2025 Movatter.jp