Last modified: 2011-04-14 15:12:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 11880 - Captchas for new editors/anons making large edits
Captchas for new editors/anons making large edits
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ConfirmEdit (CAPTCHA extension) (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-11-05 22:15 UTC by Robert Rohde
Modified: 2011-04-14 15:12 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Robert Rohde 2007-11-05 22:15:09 UTC
Often when a new editor makes an edit that substantially changes the size of a page (e.g. by blanking sections or dumping copies of other text into the page), it is an act of vandalism.  I would like to suggest that the same captcha system that triggers when such a user adds a new external link, also be used when a new user makes large edits.

Obviously not all large edits are vandalism, but enough are that putting a roadbump to slow such edits seems reasonable.  Perhaps a triggering threshold like 2000 characters would catch most of the bad edits without burdening normal activity.
Comment 1 Aaron Schulz 2007-11-05 22:25:35 UTC
Well, it might as well check for the amount of characters changed rather than just the length difference. That would cache replacing good text with garbage.

Note You need to log in before you can comment on or make changes to this bug.