You could implement your own captcha. This is hard if the captcha is on
sites popular enough to be brought to the attention of very smart
programmers who specialize in compromising captchas. This is easy if
you don't have to worry about those programmers.
Or you *might* be able to use Recaptcha in a privacy-friendly way by
serving everything yourself to the client, so that no HTTP request is
made by the client directly to Google and no plausibly identifying info
is otherwise propagated. That way, privacy-wise, Google gets little
more than timing and scale info. I'm not sure that this is permitted,
technologically or contractually. Serving it yourself is also more
expensive to maintain, and, in absence of guarantees from Google, there
is more risk that what works today will not work tomorrow.
Matthias Felleisen wrote at 12/11/2010 01:47 PM:
How difficult is it to implement one as a Planet lib that avoids tracking?
--
http://www.neilvandyke.org/
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
