Only two days after my lazyweb request for a way to combat comment-spam, Jay Allen posts this solution to the problem.
Jay's approach is exactly what I was looking for - he doesn't attack the problem based on how the spammer reaches your blog (IP blocking, hidden fields on the comment-form, etc), but rather he blocks based on the URL that the spammer is attempting to leave in your comment-system. His solution is also integrated in MT in that you won't need to edit the MT source and can add blocked URL's using MT's configuration interface. Very cool indeed.
There are a few minor downsides though:
<MTEntryCommentCount>
will still show the total number of comments - including the comment-spams&#xx;
characters. However, since Google will most likely be as confused by this as Jay's anti-spam solution, linking like that won't help spammers increase their Google ranking. Without that payoff, it's unlikely they will do this.Despite these minor shortcomings, I still think Jay's solution is the best one I've encountered so far, and hope it will keep this weblog spam-free for the foreseeable future. Thanks Jay!
My blog is Domino based ,so I don't know about cross implementation, but I will soon do something very similar to the above.
In the comment I will compare any text, whether it is in a URL or not, to a list in a configurable document containing all manner of words and phrases that would make my mother blush.
I was originally going to just siphon them off to a different view (not display them as a live comment), but I like the idea of publishing them to a personal rss feed with a link to delete them from there.
Very cool. Thanks
To Spam or Anti-Spam, that is the question...
If there's one type of spam that gets on my nerves more than any other, it is spam that promotes anti-spam tools. Sure, anyone that reads this spam is clearly in need of some protection, but by doing this, the anti-spammer becomes a spammer. And if som...