spam issues
Categories: site news, snipe
6 Comments »
Well, AoMM got rocked yesterday at one point by roughly 100 pieces of comment spam a minute. Akismet didn’t let one though but did flag a few false positives. If you had a comment moderated recently, please try again. Thank you. Comment spam is the most annoying part of blogging.
6 Responses to “spam issues”
Leave a Reply
so true
I guess that explains the ‘Exceeded alotted CPU time’ messages I was getting. A spam filter running *that* hard *must* have been eating a lot of time.
An easy way to make spam harder without resorting to the dreaded CAPTCHA is to make “invisible” fields in forms (via CSS, of course), and give them “attractive” names like “subject”. You could also have the names of all fields randomized, making it even harder.
Another method is to use encrypted javascript to load the form, which is practically invisible to the end-user, but a spammer will need to get a parser to use it (not only will it require work, it will also make the spammer’s program a lot slower).
I’ll try to find a guide i read a few hours ago and post the link here if i find it.
Kodukuu, once a spammer knows what variables do he have to send on the encrypted javascript form, the netbot program will be as fast as it could be.
The solution is a combination of the randomized fields with the encrypted JS generated from the server side. But that’s not so easy in WordPress.
Yeah i meant that the JS encryption would work together with the random fields. And yeah, it isn’t easy. Then again, is dealing with spammers ever been easy?
Once it becomes harder on the spammer than it was to you, you win.
Well, if think in positive, spams show popularity :)