Countervandalism development

What software needs to be developed for better countervandalism operations? Extension:BlockandNuke cleans up your database, but maybe you want to keep those revisions around in the edit history.

Borrow Wikipedia's abusefilters
Use Extension:AbuseFilter to get Wikipedia's list; then add them to one's own abusefilters.

Lockdown that can be activated by special page
A bureaucrat or other trusted user should be able to put the wiki on lockdown if a wave of vandalism hits; the site owner shouldn't have to do it. Extension:PanicButton or something. Maybe it'll use an Extension:Lockdown hook.

Field that records when a user went rogue
Revert everything the user did after that timestamp.

RevertBatch extension
The next extension will be RevertBatch. It will have much the same UI as Extension:BlockBatch, except that it will also let you revert a bunch of people, in two steps:
 * 1) Revert all page moves of those users. Go through the page move log, and for each page, move it to the location it was at before any users on that list moved it. Thus, it will be necessary to start with the most recent page moves and work backward. If the user rights have been properly locked down, e.g. with page moves throttled to, say, a few per day for non-autoconfirmed users, then page move vandalism shouldn't be a big deal.
 * 2) Revert all edits of those users, back to the most recent edit by a user other than those users. (If there is no such user, delete the page, perhaps; although this could also be done by DeleteBatch. Usually if there's been page move vandalism, there will be new, undesirable redirects.)

Mass delete new file versions added by bad users
Delete all the new file versions added by these users, which in most cases will be goatse or the like. (Is there already an extension to do this?) Here, an exception can be made to the usual rule that it's better to keep around information, because images can be much more disturbing to stumble upon than text. In most cases, adjusting the user rights for 'reupload' is a good preventive measure, but sometimes it's too late.

Blacklist certain images
Let's create an image blacklist, based on. Then we can blacklist goatse and the like. At least there should be a way to blacklist images from having multiple duplicate copies uploaded.

Blacklist open proxies
There are already a lot of such blacklists (see, e.g., http://www.stopforumspam.com/downloads/); they need to be imported into the wiki somehow. Maybe an extension can be written to convert the list into a PHP file creating a big $wgProxyList array that can be require_once'd by LocalSettings.php. More likely, a database table should be used; maybe a script could be written to automatically block those IPs.

Improve documentation

 * We could use some more examples of good abuse filters to use.
 * Some suggested user rights settings could be helpful. E.g., pretty much every wiki that's open to the world will at the very least want to restrict 'reupload' if there are a lot of images that could be vandalized. Also, page moving by newbies should usually be at least throttled, if not prohibited.