3 ms·
Okay, you win HN, I created an account because the anti-captcha crowd is missing the point. There's a current bug in Recaptcha. IPs that successfully solve to
by Vanit 12y ago
Okay, you win HN, I created an account because the anti-captcha crowd is missing the point.
There's a current bug in Recaptcha.
IPs that successfully solve too many captchas get given progressively more difficult challenges, which is fine, but currently Recaptcha is using the IP of the web servers, not the client. This means that the difficulty ramps up for all users quite quickly. It seems the iframe Recaptcha is permanently affected, if you use AJAX its fine after the first reload (I wrote a simple JS hack that makes it reload the first time, see www.mPoll.me)
Only noticed it because I was previously proxying Recaptcha through the server and it run its successful solutions up too high, so when the new bug came in it was immediately obvious what had happened when the first challenge is "wthdyjikhgfyijv" and on reload its "fluffy bunny 18".
On my website I'm currently overwriting the Recaptcha callbacks to allow multiple captchas, just put in a simple check to reload it the first time:
var reloaded = false;
function reloadCaptcha(challenge) {
$(':input[name=recaptcha_response_field]').val('');
$('img.recaptcha').attr('src', '//www.google.com/recaptcha/api/image?c='+challenge);
$(':input.recaptcha').val(challenge);
if(!reloaded)
{
reloaded = true;
Recaptcha.reload();
}
}
Recaptcha.finish_reload = function(challenge,b,c){
reloadCaptcha(challenge);
}
Recaptcha.challenge_callback = function(){
reloadCaptcha(RecaptchaState.challenge);
}
Recaptcha.create(recaptchaKey);