This is one of the most effective anti-vandal protection methods and has very little impact on legitimate users.
- 1 简介
- 2 安装
- 3 Configuration
- 4 Compatibility with other extensions
- 5 See also
- The user can see their edit and continue editing their own version of the page.
- How do the admins moderate?
- A new special page is provided (Special:Moderation). It's much like the RecentChanges, but has "Approve", "Reject", "Approve all" and "Reject all" buttons.
- Rejected edits go into the rejected archive.
- Approved edits are applied normally.
- Logs of "who approved what" are maintained. Only the moderators can see them.
- If edit conflict is detected and it can't be resolved automatically, the moderator has a merge button to apply the edit manually.
- Why is it good?
- New users are not discouraged by annoying captchas, phone number verifications, etc. They edit normally, like they would do in MediaWiki without moderation.
- Blocks become practically obsolete. And blocks are not good (consider the chance of hitting a legitimate user with a range block, or inability to allow good edits from a not-very-adequate user who sometimes has the urge to vandalize a page or two).
- Vandalism out of "wanting to be noticed" is discouraged. No one would sit for 5 hours looking for new and new proxies to make admin angry, if it's known that all those actions are not a problem.
- Vandalism methods like "vandalizing one page from two accounts to prevent one-click rollback" are no longer effective.
- Website can operate in anonymous networks like TOR or I2P.
Does MediaWiki have other counter-vandalism methods? In brief - not really.
MediaWiki was developed for Wikipedia. At any given time, Wikipedia has hundreds of volunteers willing to revert vandalism in real time. Almost every other wiki besides Wikipedia doesn't have that kind of advantage. The built-in counter-vandalism idea of MediaWiki is that vandalism takes more time than reverting it. Normally that's true, but this does a poor job at discouraging vandalism, and the admins still have to check for vandalism often, even if the reverting itself doesn't take much of their time.
There are three known methods of fighting vandalism:
- Make all edits hard. For example, Lurkmore.to imposes a strong captcha on all edits from new users, and it takes a lot of edits to finally be able to edit without the captcha. Therefore the vandal has to spend a lot of time to do a handful of edits.
- The obvious minus is that all legitimate users have to bypass the captcha as well, which could discourage minor edits like spelling fixes.
- Enforce user identification - for example, login via Facebook. If the social network verifies that all its users have a valid mobile phone number, then each vandalism attempt requires the vandal to go to the shop and buy a new SIM card. This method is extremely effective, though eliminates the anonymous editing and turns away the users who don't have an account in any supported social network.
- A strong minus of this method is the impact on users' privacy. In non-democratic countries editing a page on politics can result in government trying to identify and persecute the user. For example, Lurkmore.to was contacted by Russian "anti-extremist special force" with demands to disclose information about the authors of pages about Ramzan Kadyrov and Molotov cocktail.
- Mitigate the results of vandalism. For example, a user can create 100 pages with offensive titles, but they can all be deleted by two clicks in 扩展:大量删除. Moderation extension belongs to this category.
This extension is stable. It has been deployed in production on Russian Uncyclopedia (absurdopedia.net) since November 2014.
- newest version of MediaWiki
- MediaWiki 1.31 (LTS)
- MediaWiki 1.27 (legacy LTS)
What's the difference from FlaggedRevs or Approved Revs?
扩展:標記修訂 and Extension:Approved Revs hide the bad revisions only from readers. The vandal edits will still exist in history and RecentChanges, and all editors will stumble upon them when they try to edit the page which was vandalized. Therefore administrators have to revert vandalism quickly.
On the other hand, Moderation completely eliminates vandal edits: non-approved revisions are simply not created in page history, etc. This ensures that not only readers, but also other editors won't see the vandal edits in any of the pages.
In short, (1) FlaggedRevs is for quality control but doesn't help against persistent vandalism. (2) Moderation is specifically against vandalism and renders it completely ineffective.
|Do readers see vandalism?||No||No|
|Do editors see vandalism?||No||Yes|
|Does vandalism remain in page history?||No||Yes|
|Can quickly reject all edits by user?||Yes||No|
|Can other editors improve non‑approved edits? (not vandalism)||No||Yes|
- Check-out the sources with
git clone https://github.com/edwardspec/mediawiki-moderation.git文件，并将其放置在您
wfLoadExtension( 'Moderation' );
- 完成 – 在您的wiki上导航至Special:Version，以验证扩展已成功安装。
Parameters for LocalSettings.php
- If set to false, then new edits are applied as usual (not sent to moderation). Default: true.
- Time (in seconds) after which rejected edit could no longer be approved. Default: 2 weeks. Note: old rejected edits are NOT deleted (moderators can always look at them in Rejected folder even if this time has elapsed).
- if set to an array of namespace numbers (e.g.
$wgModerationOnlyInNamespaces = [ NS_MAIN, NS_FILE ];), moderation is only enabled in these namespaces (edits in other namespaces will bypass moderation). Default (empty array): moderation is enabled everywhere.
- If set to an array of namespace numbers (e.g.
$wgModerationIgnoredInNamespaces = [ NS_MAIN, NS_FILE ];), non-automoderated users can bypass moderation in these namespaces. Default (empty array): moderation can't be bypassed anywhere.
- If true, notification email will be sent to $wgModerationEmail each time an edit is queued for moderation. Default: false.
- If true, only notify about new pages (but not about edits in existing pages). Default: false.
See also: #Configuration options ONLY for pre-publish review (options not recommended for 95% of wikis).
|Right||What can the user do?||Who has this right? (by default)|
||Edits are applied as usual (not sent to moderation).||automoderated, sysop, bot|
||Page moves are applied as usual (not sent to moderation).||automoderated, sysop, bot|
||Can access Special:Moderation||moderator, sysop|
||Can see IPs of registered users on Special:Moderation.||checkuser|
Additional anti-vandalism tips
In order to prevent vandalism, the following additional measures should be applied:
- Please restrict the renaming of pages to a trusted group (not just "automoderated"), because it can be used for difficult-to-revert vandalism.
$wgGroupPermissions['automoderated']['skip-move-moderation'] = false; $wgGroupPermissions['sysop']['skip-move-moderation'] = true;
- Registering new accounts with offensive names is still a way for a vandal to show itself in the RecentChanges. A simple solution is to remove newusers log from RecentChanges:
$wgLogRestrictions["newusers"] = 'moderation';
Recommended use / good practices
The following good-practices are advised:
- Only vandalism should be Rejected. Not-so-good edits with good intentions (e.g. adding excessive plot details into the Wikipedia article about film) are better made Approved and then reverted as usual. This way the author is not offended and the text is saved in page history, viewable by anyone.
- Any user that is deemed legitimate (does N good edits) should be granted
$wgAutopromoteis NOT recommended, as it motivates the vandals to do many very-minor edits (e.g. adding interwiki). Better grant the flag manually for one good edit and not grant it for 30 useless-edits-made-for-count.
- Abstain from using blocks. Don't protect pages "just in case", except maybe for important templates.
- Allow the full rehabilitation of users with a bad history of editing. Their useful edits to the articles should be allowed, no matter how many times they were blocked. At the same time, trolling on talk pages should be rejected, so are the purposely-low-quality edits.
Non-recommended use: Moderation as pre-publish review extension
Moderation is an anti-vandalism tool first, but some wikis use it for quality control. For example, a wiki of scientific works might choose to:
- Not Approve any edits until they meet the strict quality standards of the industry.
- Not Reject any edits that are not yet good enough, so that the author could continue editing it as long as necessary.
Pros of this approach:
- New page appears as a fully reviewed, correctly formatted document with no typos, etc.
- Noone except the author and moderators would see the imperfect revisions.
- Other users can't improve the article until it is Approved. In fact, they won't even know that it exists.
- Pending changes don't have an "edit history". Moderation stores only 1 pending change for each Page/User pair. That's inconvenient if you are preparing your page for publication for weeks. User can even accidentally delete the necessary text in their pending revision, and it won't be recoverable.
Configuration options ONLY for pre-publish review
The following parameters are only needed when using Moderation for review. They are not recommended for 95% of wikis (when following the Best Practices, they are totally not needed).
- If true, Preview link is shown on Special:Moderation. Default: false.
Why not recommended? Answer: when following Best Practices, you would never Reject a good change just because it is formatted poorly. Whether this edit is good or not, you know from "diff" link. "Preview" link tells you "how is this page formatted", which shouldn't affect your decision.
- If true, moderators can modify the text of pending changes before Approving. Default: false.
Why not recommended? Answer: easy to mess up. Moderator can accidentally delete the text of pending edit (and it won't be recoverable). Furthermore, these changes are not attributed to moderator (after approval, it looks as if the original author made the edit this way), which is creepy.
Compatibility with other extensions
- Extension:Moderation should be enabled last in LocalSettings.php, because it aborts at least PageContentSave hook.
- Extension:Moderation fully supports Extension:CheckUser, meaning that if CheckUser extension is enabled, then any approved edit will have correct IP, user-agent and XFF saved in the checkuser tables.
- Extension:Moderation is fully compatible with Extension:VisualEditor and Extension:MobileFrontend. Theoretically it should also work with other API-based editors.
- Extension:Flow will work, but edits in Flow forums will bypass moderation.
- Moderation of Flow forums should be implemented in Extension:Flow itself. These forums use a non-text "content model", which is not supported by Moderation.
- (a) Upload extensions like Extension:MultiUpload and (b) uploads via API are only supported in MediaWiki 1.28+.
- This can't be implemented for MediaWiki 1.27, because it doesn't have UploadVerifyUpload hook.
- Extensions that modify several slots of Multi-Content Revisions (not just the main slot, as MediaWiki itself does) are currently unsupported, because MediaWiki doesn't provide the needed hook . Hopefully this will change in upcoming MediaWiki 1.33.
- Extension:ConfirmEdit - common CAPTCHA extension.
- 扩展:滥用过滤器 - common extension against spam bots and typical vandalism like blanking.
- Extension:Approved Revs - allows marking a revision as "approved", being the one displayed by default on a page.
- 扩展:標記修訂 - more advanced (and heavy) version of Extension:Approved Revs.