フラグ付きの改訂

This page is a translated version of the page Flagged Revisions and the translation is 59% complete.

FlaggedRevs (Flagged Revisions) is an extension of MediaWiki that allows one to flag versions of articles and thus give additional information about quality. This comes with the possibility of changing what an 未登録利用者 sees by default. The technical description can be found at mw:Extension:FlaggedRevs.

The actual usage and configuration of the extension varies a lot; usually, the feature enters into effect on a page only after it's "reviewed" (flagged) at least once, so it takes a committed community (in terms of active editors and guidelines) to actually enable it on a large wiki. For instance, the German Wikipedia uses the feature on 99.99 % articles considering it the default process; while the English Wikipedia uses it on less than 0.05 % articles with a non-standard configuration, for some special cases. More information on this spectrum follows.

クラシックなフラグ付き改訂: ドイツ語版ウィキペディアの例

Here we will describe how the concept is used in the test on the German Wikipedia and what it is good for. First of all, there are two types of flags: Sighted and Quality. These come with two new user groups: An editor is able to flag versions as sighted, a reviewer is able to flag as quality.

Sighted means that an article has been looked at and does not contain vandalism. Quality means that a real content check has been done. Because the first check is not a big thing, any admin can give editor rights and there is an automatic process for giving this right. Currently, if you have edited for two months and did 200 edits in the main namespace, then you can get the editor right. The reviewer right for quality flag can be given only by bureaucrats and it is not in active use.

What do flagged revisions accomplish?
  1. Flagged revisions give the reader an indication of the quality of the article.
  2. They assure a basic article quality (someone with basic trust has written this or checked it), if the last sighted version is shown to the reader.
  3. If only the last sighted revision is shown to the reader, they may make vandalism less attractive, although it is disputed whether vandalism decreased due to the adoption of flagged revisions.
  4. Generally, they provide a powerful tool for the control of new edits and patrolling the recent changes becomes more efficient:
    新しい編集は1度だけ破壊行為がないかチェックする必要があります。
    連続した複数の編集をチェックできます。
    If an article was vandalized and subsequently edited by a trusted user, vandalism was often hidden. This is no longer possible.
    編集が忘れられることはありません。
    More people are able to find edits that were not sighted yet.
    Combined with categories, this becomes really powerful, since wikiprojects/portals have the possibility to oversee their whole area for new edits.
  5. They provide a useful system of revision labeling in general, increasing the information readers and contributors can derive from the history and about the article.

Edits can wait to be reviewed for a considerable amount of time, up to a month and a half as of 24 January 2016, and 15 days on average (see de:Special:ValidationStatistics). Edits awaiting review can be seen at de:Special:OldReviewedPages.

変更の保留: 英語版ウィキペディアの例

Classic Flagged Revisions were perennially rejected on the English Wikipedia. In 2009–2010, this new proposal emerged as an acceptable compromise for trial, which ended up being adopted on a permanent basis. The principle of pending changes (initially denominated flagged protection) is to allow administrators to enable flagged revisions on selected pages, when they meet criteria specified by the protection policy, typically an excess of vandalism or other policy-violating edits.

An important aspect of the feature is that edits by all autoconfirmed users (accounts older than four days and with at least ten edits), and not only reviewers, are automatically reviewed when the previous revision had already been accepted. Since edits by autoconfirmed users who are not reviewers to pages under pending changes with still unreviewed changes are rare, this means that almost always, autoconfirmed users can edit pages under pending changes without restriction. Thus, this is less restrictive than semi-protection. Additionally, there is an option to turn off this automatic reviewing of autoconfirmed non-reviewers, suggested for use on pages heavily targeted by sockpuppets which on occasion require full protection, however the use of this option has not gained consensus.

As of September 5, 2023, 3,880 of the 7,972,029 eligible pages (Article and Wikipedia namespaces) are using pending changes on enwiki (see en:Special:ValidationStatistics). Edits awaiting review are located at en:Special:PendingChanges, which has most of the time about half a dozen edits, none older than a few hours.

フラグ付き改訂のその他のフォーム

Other wikis may choose to use an amount of features somewhere between what the German Wikipedia and the English Wikipedia chose. For example, applying pending changes not by default on all articles, and not only on demonstrably problematic articles, but on a large subset of articles deemed particularly sensitive.

Flagged Revisions has also been suggested as a way to defer for review edits flagged as suspicious by the Abuse Filter , see w:Wikipedia:Deferred revisions.

Passive Flagged Revisions, working on the same principle but without affecting the version viewed by readers, has been suggested to improve patrolled edits, see w:en:Wikipedia:Patrolled revisions and w:en:Wikipedia:Deferred changes.

Setting $wgFlaggedRevsOverride = false; makes FlaggedRevs be just informative, doing "nothing" except adding review queues and banners/warnings: the latest version is always shown as on a "normal" wiki. Over 20 Wikimedia wikis use this configuration and many of them feel less urgency to go through the review backlog.

ウィキメディア・プロジェクト上のフラグ付き改訂

Flagged Revisions has been implemented on several wikis. The list below might not be up to date compared to the configuration file for all wikis.

  • ウィキペディア
  1. アルバニア語 – 2010年11月7日に有効化
  2. アラビア語 – 2009年8月6日に有効化
  3. アレマン語 – 2008年11月17日に有効化
  4. ボスニア語 – 2010年4月8日に有効化
  5. ベラルーシ語 – 2011年2月5日に有効化
  6. ベンガル語 – 2011年5月20日に有効化 (T30717)
  7. チェチェン語 – 2014年1月に有効化、(T58408)
  8. 漢文 – 2008年11月17日に有効化
  9. English – enabled Pending Changes once again 1 December, 2012
  10. エスペラント – 2008年11月18日に有効化
  11. ペルシア語 – 2014年5月22日に有効化 (T67452)
  12. フィンランド語 – 2011年11月30日に有効化
  13. ジョージア語 – 2011年4月11日に有効化 (T26976)
  14. ドイツ語 – 2008年5月6日に有効化
  15. ヒンディー語 – 2010年8月30日に有効化、2011年8月8日に再構成された (T26622T31911)
  16. ハンガリー語 – 2008年11月17日に有効化
  17. Indonesian – enabled 17 June 2010; reconfigured into Pending Changes on 15 July 2021 (T268317)
  18. インターリングア – 2009年3月19日に有効化
  19. 中央クルド語 – 2014年6月5日に有効化 (T67809)
  20. マケドニア語 – 2010年4月24日に有効化
  21. ポーランド語 – 2008年11月17日に有効化
  22. ロシア語 – 2008年8月8日に有効化
  23. トルコ語 – 2011年1月31日に有効化
  24. ウクライナ語 – 2011年に有効化
  25. ヴェネツィア語 – 2011年11月29日に有効化 (T30837)
  • ウィクショナリー
  1. ドイツ語 – 2008年11月24日に有効化
  2. アイスランド語 – 2009年3月19日に有効化
  3. ポーランド語 – 2009年12月7日に有効化
  4. ロシア語 – 2011年4月17日に有効化
  5. ウクライナ語 – 2008年11月24日に有効化
  • ウィキブックス
  1. 英語 – 2008年11月14日に有効化
  2. ポルトガル語 – 2011年11月29日に有効化
  • ウィキニュース
  1. 英語 – 2008年8月5日に有効化
  2. ペルシャ語 – 2010年10月25日に有効化
  3. フランス語
  4. ポルトガル語
  5. ロシア語
  6. スペイン語 – 2009年6月3日に有効化
  7. タミル語 – 2010年5月31日に有効化
  • ウィキクォート
  1. ドイツ語 – 2009年8月7日に有効化
  2. ロシア語 – 2008年11月19日に有効化
  • ウィキソース
  1. ロシア語 – 2008年11月19日に有効化
  2. ヘブライ語
  3. ポーランド語 – 2010年3月23日に有効化

For testing purposes, Flagged Revisions is also implemented on test2 wiki.

進行中のトライアル


None currently

却下された

  • ウィキペディア
  1. ペルシャ語 – 結果に至らず。2011年3月に閉鎖
  2. フランス語 – 2009年10月調査完了。
  • その他
  1. MediaWiki.org – enabled on 8 August 2009; disabled on 22 May 2014 with gerrit:134935 (announcement)
  2. ポルトガル語版ウィキソース2023年3月20日に無効化

Wikis that want to request custom implementation of the feature can use these Bugzilla requests as models for their own requests.

有効化

モラトリアムのお知らせ

As April 2017, there is a moratorium on the Flagged Revisions deployment to new wikis. (Dereckson @ T66726)

Flagged Revisions is extremely flexible; as such, it's complex to maintain (from a code point of view). The last new wikis added the extension in 2013 and 2014. In 2014 WMF tech first silently stopped enabling it without formal decision and then in 2017 by Dereckson's moratoira and RfC. Currently, WMF is trying to solve who should maintain it: Code stewardship review: FlaggedRevs – This extension has been deployed to prod around seven years ago and after a while, it became virtually without any maintainer, Technical debt in this code is unimaginable and in a matter of UX/UI it's non-standard and out-dated but any (of my) attempts to modernize it failed due to out-of-date and non-standard PHP code. (Ladsgroup, Jan 24 2018, phab:T185664) It is unlikely that new wikis will be enabled before this is solved OR the extension will be undeployed altogether.

有効化についての古いプロセス

The general process is the usual one for ウィキの設定変更の依頼 , but proposers should also:

(This is the process followed by a recent adopter like the Finnish Wikipedia.)

注: 上記のセクションは2014年に追加された。

英語版ウィキペディアのトライアル

The English Wikipedia trial of a light weight form of flagged revisions known as pending changes, which eventually resulted in its permanent implementation, required at least one contractor hired to tweak and test the configuration, as well as development work involving no less than 8 Wikimedia Foundation persons in a period of 7 months from September 2010 to March 2011, according to reports.

結果

ローカル

There is no policy yet for disabling or denying the extension, but it's highly advisable that any wiki adopting it monitors results closely (at least on Wikistats and Special:ValidationStatistics), to ensure the feature is actually helping to reach the intended goals. As an example, a wiki could establish, as local community guideline/goal, documented in the local project page on the feature/process, a minimum "level of service" or "key performance indicators", like

  • no more than X % total articles should be stale,
  • (if applied to a subset of articles, e.g. previously protected) total edits and active editors on flagged articles should increase by Y %,
  • average staleness of unreviewed edits shouldn't be above Z days and median time for review shouldn't be above W days.

Having such a shared understanding of the intended results will help a wiki reach a consensus on the opportunity to have/keep the feature enabled.

一般

General results of Flagged Revisions on various projects are not known: there are few studies.

However, on several wikis, Special:ValidationStatistics shows a clear failure, in that there are peaks where

  • the quota of total articles which have unreviewed edits is over 10 %, or sometimes even a majority of total articles,
  • unreviewed changes are as old as 1000 days or more on average (this metric disregards how fast reviewed changes were reviewed),
  • the time needed for unregistered users to have their edits approved is several days.

The more articles are using Flagged Revisions, the more severe the last two problems are; if only a handful pages are reviewed in the first place, average delays on those few pages are less significant for the wiki as a whole.

Where it's not actively used, the extension should probably be disabled. Regular cross-wiki reports on flagged revisions status have been proposed but not implemented yet. If you are or want to be a tool developer, this would be a nice thing to build and run on Tool Labs.

暫定レポート

  • FlaggedRevs Report December 2008 – report on FlaggedRevs usage across Wikimedia projects
  • Hungarian Wikipedia FlaggedRevs test, october 2019 – shows that showing latest revision by default (setting $wgFlaggedRevsOverride = false) increases the number IPs making edits by 100%, the number of edits made by IPs by 30%, and anonymous vandalism by 2-3 percentage points (which is a 10-30% relative increase, depending on how narrowly vandalism is defined) compared to showing approved revisions by default. No visible effect on registered users.

関連項目