Strict Standards: Non-static method CSS_Switcher::usage() should not be called statically, assuming $this from incompatible context in /home/bigblog/public_html/hipporiver/plugins/pi.css_switcher.php on line 29

Warning: Cannot modify header information - headers already sent by (output started at /home/bigblog/public_html/hipporiver/plugins/pi.css_switcher.php:29) in /home/bigblog/public_html/hipporiver/core/core.functions.php on line 707
the Big Blog Company | Smitting the spammers with blacklists
“Who yer callin' a sparrow, you schmuck?!”
The bird on the back.
April 20 2005
Wednesday
Smitting the spammers with blacklists
Perry de Havilland • Blogs & Blogging • Administrative 
Trackback to this post [0]

This blog ‘only’ gets a few trackback spams per week but we are well aware that some folks have been getting hammered pretty hard by those parasitic vermin.  The site Samizdata.net, of which I am chief editor, is a high volume site and thus attracts the spammers rather more regularly (as in about 2,600 trackback spams in the last 48 hours alone).  Let me pass on a trick that makes using the various forms of Blacklist designed to keep the spammers at bay work more effectively.

If you get a couple trackbacks with ‘payload’ URLs of (say) ‘goatsex.poxyspammer.com’ and ‘texasholdem.bandwidththief.com’, you can of course enter those URLs into your blacklist and all future incidences of trackbacks with those URLs in them will be blocked.  Alas, the vile spammers are rather too smart to make that effective, because next time their spambots are sent out to dump their garbage on your blog, the URL may look like: ‘goat-sex.poxyspammer.com’ and ‘texas-holdem.bandwidththief.com’ and next time ‘goatsex.peabrainspammer.ru’ and ‘texasholden.commoncriminal.pl’.  So…

When adding to your blacklist, rather than adding the entire offending URL, add the data thusly (using the examples above):

goatsex
goat-sex
poxyspammer
texasholdem
texas-holdem
bandwidththief
peabrainspammer
commoncriminal

That way just partial matches will trip over the blacklist and minor alterations to the payload URL will not let it avoid detection.

Spam is intolerable, so do not just delete it, fight back and defend your private property (i.e. your blog)!  If you do not have anti-spam defences in place, you really must install them… the tools are available but you need to spend the time to learn how to use them effectively.

Page 1 of 1 pages