July 21, 2005
|
Trackback spam
|
644 hit(s)
In my blog I've started seeing a variation on comment spam -- trackback spam, wherein a trackback is left whose purpose is, of course, to embed a URL into the blog. This is an interesting twist because it's not quite as easy to defend against trackback spam as it is against comment spam.
To review: for comment spam, the most popular defense (aside from simply disabling comments) is to add some sort of feature requiring human intervention before the comment is saved. Most people use a CAPTCHA control. In my case, I present an arithmetic problem that is easy for humans but not so easy for automated comment-spam bots.
For trackbacks, though, you can't do this -- trackbacks more-or-less by definition are posted by machine, so you can't require human intervention. (At least, not in my casual thinking about it.) So my defense for now is to disable comments; I just updated the blog code so that if comments are disabled, so are trackbacks. Not a particularly effective defense, really, but since all the trackback spam was hitting one particular entry, maybe it will fend off at least one spammer.
In addition, for the time being the volume of trackbacks I get is small, and I am alerted whenever one is posted, so it's easy for me to simply delete the bad trackbacks manually. So that's a secondary line of defense (and a very effective one, too!), assuming I am not inundated with trackback spam.
I'd be interested to hear whether others have seen this problem and what they are doing about it.