My argument is that a spammer is more likely to spend that extra CPU time versus a legitimate visitor - if the option were there. I'm not gong to sit around for a few seconds waiting for my comment to post. Comments are pretty much bullshit anyway (on most sites), so I generally won't post them and contribute to the garbage pile. But If I did, I certainly wouldn't be around waiting as if I was on some 20 year old dial-up connection.
The plugin I use doesn't max out the cpu for several seconds. It just trys to use javascript to prove that someone at a keyboard physically typed out a comment. It's completely invisible to the commenter.
Which, I might add, is significantly less inconvenient that typing in a captcha.
The stopping of spam has more to do with the spamming scripts not having javascript interpreters and not being able to do any calculations at all rather than the artificial time penalty. The most beneficial implementation of PoW is with a lightning fast calculation that won't even be noticed by the human visitor.
Agreed. That's how wp-hashcash works. If/when the spammers get around to integrating a javascript engine, we'll have to see what happens. So far, I've not had a single spam comment get through.
And this too can break accessibility for some people. Not all browsers have javascript (a text-only browser like Lynx comes to mind). I'm not a fan of using Javascript for something that isn't likely to benefit the viewer and isn't optional. I do like the server-side evaluation of the content however.
That's where akismet comes in as a secondary filter. When clients that don't have js enabled comment, it just goes into my moderation queue and I approve them. no problem there.
Previous Topic
Index
