The spammers have just found my ikiwiki. I have my main pages locked but allow open changes to my discussion pages and in the last few days one page in particular has been overwritten by spam about nine times, each edit was from a different IP address. (sorry for the funny formatting, I upgraded to the latest version and haven't tracked down what changed yet)

I'll probably lock down my discussion pages to require a login of some sort and hopefully that will slow them down. Is anyone else seeing problems on their wiki?

As far as techniques for reducing spam I've found the MoinMoin technique of refusing to allow page saves with known spam URLs combined with a group maintained list of URLs to be fairly effective.

Cheers, AdamShand

I have yet to hear of any spammer using openid.. --Joey

Mh.. well. I know this problem, too. I leave the Discussion sites open for no registrations, so that visitors can easily write a comment to this specific blog entry without the need for registration. (This would be the same behaviour, as many blogging engines are using). Maybe it is possible to wrote a plugin that would scan the text which is submitted via spamassassin or something similar. (Using this combined with known spam URLs would maybe reduce the load of the server if there are many webpages which are getting editted by someone). If you like this idea Joey I might be interested to write such a plugin after my exams this and the next month. :) -- ?Winnie

You might look at the Wikipedia page on "Spam_in_blogs" for more ideas. In particular, would it be possible to force a subset of the pages (by regex, but you'd choose the regex to match those pages which are publicly writable) to use rel="nofollow" in all links.

I just wanted to leave a link here to the require CAPTCHA to edit plugin patch. Unfortunately that plugin currently interacts badly with the openid plugin. -- Will

Ikiwiki now has a checkcontent hook that plugins can use to see content that is being entered and check it for spam/whatever.

There is a blogspam plugin that uses the service to check for common spam signatures. --Joey


I am sorry to say that neither those solutions are sufficient for a site that allows anonymous comments. blogspam lets thousands of commits through here, as i described in commandline comment moderation. Now, maybe I didn't configure blogspam correctly, I am not sure. I just enabled the plugin and set blogspam_pagespec: postcomment(blog/*) or */discussion. I have also imported the blocklist from this wiki's ikiwiki.setup, generated from spam fighting. I have had to add around 10 IPs to that list already.

It seems to me a list of blocked URLs or blocked IPs as mentionned above would be an interesting solution. blogspam is great, but the API doesn't seem to support reporting IPs or bad content back, which seems to be a major problem in working around false negatives. I'm tempted to just remove the done tag above, because this is clearly not fixed for me here... --anarcat