Manual talk:Combating vandalism

Just out of curiosity, how are they changing their IP so damn fast? So tiring.

http://highfedelity.com/index.php5?title=Special:Ipblocklist

Darrellx 21:43, 19 September 2011 (UTC)
 * Oops, I havent checked this page in a long time. They use proxies. I suggest you do this. Set up Confirm Edit to show the captcha for every anonymous edit. Seeing what that bot is doing on your site, I can safely assume its some advertising bot and not a human, so the captcha will put a stop to that. A real human can use the captcha, they just have to or they can create a username and not have to enter it every time. If its a malicious human doing intentional vandalism, he'll still get around the captcha. The only option then is to disable editing and report the IP addresses if you can (not successful for proxies as there are so many), or install Flagged revisions. I'm still learning what that one is about but it has some nice features. --Choshi 02:40, 29 December 2017 (UTC)

Creating a bot to revert spam
I'm trying to help the root site at the wiki farm at wiki-site.com, seeing as the admin there seems to have abandoned the main site. What I've been doing for some months is replace the spam pages with a redirect to creating their own wiki on the farm. This has worked well.

But recently a rash of advertising spam has over run the root site and I'm struggling to keep up - and the server is struggling as well as I have to change IP's every three to five edits. They appear to be bots that ignore instructions completely. The only real way this can be combated by me right now is with a bot of my own that reverts these spammers on sight. But I have no idea how to do this.

Can anyone help? TLPG HOME YACK 01:34, 16 May 2012 (UTC)
 * Well, you can use Extension:ConfirmEdit and Extension:AbuseFilter to try to hinder them.--Jasper Deng (talk) 02:10, 16 May 2012 (UTC)


 * No I can't because I'm not an admin, or even a sysop. There's no one with those powers dealing with this. TLPG HOME YACK 04:18, 16 May 2012 (UTC)
 * Ugh, you'll have to contact your wiki's operator in order to get a bot. I'm sure it'll irk your wiki's operator(s) if you ran a bot without their permission.--Jasper Deng (talk) 04:39, 16 May 2012 (UTC)
 * I doubt he'd even know, given that he's abandoned the site and is uncontactable. TLPG HOME YACK 05:26, 16 May 2012 (UTC)
 * There's very little you can do without some form of administrative access.--Jasper Deng (talk) 19:24, 16 May 2012 (UTC)
 * Surely there must be some sort of bot that anyone could run? TLPG HOME YACK 07:59, 17 May 2012 (UTC)
 * I'd browse around this site for information on how to write one, because I personally don't know of any freely distributed bot that does this.--Jasper Deng (talk) 16:58, 17 May 2012 (UTC)

removing spam contents
I would have expected that when I block the user, and identify it as spam that it doens't offer a way to remove associated content at the same time. And again when I go to the block of contributions. A simple way to delete it all without going to each page would make it a lot easier.
 * Extension:Nuke can do mass page deletions.Jasper Deng (talk) 17:08, 23 August 2012 (UTC)

removing spam accounts and spam contents
Recently some KDE wikis got flooded by a possible botnet, so we needed to mass delete accounts and their spam pages. Thanks to another friendly KDE member i got an updated removeSpamAccountsAndPost.php, which can be put into maintenance: This can be invoked the usual way, like. Now, to mass delete he also gave me a simple bash script: It waits for username input, if found, takes the necessary steps and waits for the next name. So it is just a matter of dropping the names into the console. In certain cases you need to adjust the call to the php script, like providing the wiki name var.

Hope that helps someone else as well. --Neverendingo (talk) 19:12, 24 July 2013 (UTC)

Banning images
How do I (1) prevent users from uploading specific images and (2) after they have uploaded images, delete all those images, if they are new versions of already-existing images? E.g., suppose a user uploads new versions of a bunch of different currently-existing images, updating them to the goatse picture. What's the quickest way to revert-and-delete that on multiple images, and keep them from uploading those images again? Will it be necessary to write a new extension to implement this? I don't want to rely on Extension:BlockandNuke because it seems like overkill to completely delete their non-image edits. Thanks. Leucosticte (talk) 07:54, 6 March 2014 (UTC)
 * For specific images, I would try protecting the non-existing image page. That might prevent them from creating that page and maybe also from uploading the image...
 * For overwriting of existing images, there is the "reupload" user right, which you can take away or grant user groups as needed. --87.123.20.110 23:36, 7 April 2016 (UTC)

Extension: Wikimedia blocks?
We know that Wikimedia stewards block a huge number of vandal IP ranges. Other wiki sites could potentially benefit from it as well. An extension is possible which checks IP at every action in a way similar to Extension:GlobalBlocking but, unlike that existing extension, it must check the IP against the database of Wikimedia (via API or some intermediary caching service). Did anybody work on something alike? Incnis Mrsi (talk) 11:52, 23 July 2018 (UTC)