News for hackers. Stuff that matters.
Re:CAPTCHAs decrease conversion rates by gcr on Friday March 25, 2011 @01:09PM (#2369316)
Here's an idea: Force registrants to submit a computationally expensive token along with their registration form. Perhaps it's computed with javascript. Users usually spend more than 15 seconds on the form anyways, and spammers will hate to peg their hardware like that.

Any thoughts?

Re:CAPTCHAs decrease conversion rates by jeremyw on Friday March 25, 2011 @02:20PM (#2369637)
Fun, a number of blog plugins have picked up the hashcash ideas, e.g. http://wordpress.org/extend/plugins/wp-hashcash/.

Add 100ms-of-2011-avg-cpu computation and tie it to the submit button (avoiding any complications interleaving with user activity). So that deals with first-order dumbbots and makes life a little harder for Javscript-executing (but still volume-based) folks. Marry to a bayesian system to handle the third-order mechanical turk-style miscreants.

Re:CAPTCHAs decrease conversion rates by gcr on Friday March 25, 2011 @02:44PM (#2369753)
I see! Interesting. Thanks for sharing this.

For curious people, Wikipedia also has related information: http://en.wikipedia.org/wiki/Proof-of-work_system

Re:CAPTCHAs decrease conversion rates by cowpewter on Friday March 25, 2011 @01:35PM (#2369444)
Javascript is single-threaded. You'll block the UI, and your real users will spend 15 seconds staring at the <insert your OS's wait cursor here>
Re:CAPTCHAs decrease conversion rates by gcr on Friday March 25, 2011 @02:02PM (#2369575)
There are ways around that. Web workers for browsers that support them and continuation-passing style for those that don't.