XpdSpammers

• 20050225
• • Correct (and write tests for) tomcat filter so it doesn't chain other filters on a spam hit (there by still letting spam in!)
  • https://xpdeveloper.com/cgi-bin/cvsweb.cgi/xpdantispam/

• 20050224
• • rolled back to JSPWiki 2.0.52
  • Tomcat level filter added with a collection of spam words
  • Updated it after being spammed (spammer listed on http://chongqed.org/) so I'll consider using that source of words

• 20050218
• • All IP address bans have been removed
  • We can now bar various words from being posted.
  • Going to look at linking the spammers sites to http://chongqed.org/

I have used SnipSnap for over a year and found it to be very good - some really nice macros for code formatting etc. --DanPollitt

A policy that only requires people to sign in when they do writes that contain an IP address or a DNS name might work. -- DafyddRees

OliBye has now run SnipSnap on another site for a while. It's clever, too clever, so many gadgets.

Bah. I visit too occasionally to be an effective WikiGnome?, and this morning I'm quite disheartened to find dozens of pages spammed. Hoping it's possible to write a script to reverse the changes from the spammer's IP address automatically...

On the UseMod-variant Wikis I maintain, I found that a policy of disallowing edits which add external links (h-t-t-p-variety links) blocks 100% of WikiSpam?. This may be a radical step for some Wikis, reasonable for others. It doesn't require annoying registration. (Requiring people to register to post links would be reasonable.)

-- LaurentBossavit JSPWiki doesn't have this (I thought it did). Alpha JSPWiki versions have a JSPWiki:SpamFilter which we're now using. I still think simply not allowing any external links is a nice simple idea though. -- OliBye