I posted a comment to the first Comment Spam post to see if it still works. It appears to have. I wanted to layout the rest of my comment spam strategy here.
I was also going to use Kitten’s Spaminator. When I opened the php file in Notepad, there were no line breaks. Until and unless someone tells me what I’m doing wrong, I won’t be using this method. Since I have WordPress v1.2.2, I need to edit the php directly instead of using the interface.
If HashCash isn’t satisfactory, I’m going to try periodically renaming the commenting php file. The problem is that anyone that uses WordPress has the same file name that handles comments. The bots know this name and edit it directly (or something like that). Changing the file name prevents the bot from finding the file. This all assumes that I can find the instructions to do it – a cursory search of the WP forums didn’t turn it up for me.
Next, I might try adding the code from this post that warns commenters if a forbidden word was used.
Then I might try a few things from Combat Comment Spam.
If none of that works or looks good, I’ll be going with CAPTCHA, Preview, and User Registration in that order. I don’t think it will come to that, though. This guy defeated CAPTCHA and you may be interested in reading about it. If you like capitalization and punctuation and much as me, you might not want to read this page – it has neither. Defeated or not, I don’t lose much by having as many defenses as are out there.
I plan to implement these one at a time until I get a manageable amount of spam or until the good folks at Spambayes come out with something for comment spam.
Thanks, everyone, for the comments on the first post.