Comment by aaronmdjones

Comment by aaronmdjones a day ago

This isn't Google's doing but Mozilla's. Firefox's strict tracking protection blocks third-party cookies. The site you're trying to visit isn't hosting reCAPTCHA itself; reCAPTCHA was loaded from a third-party origin (Google); so the cookie that Google sets saying you passed the CAPTCHA is blocked by Firefox.

You can add an exception in Firefox's settings to allow third-party cookies for CAPTCHAs. Google's reCAPTCHA cookie is set by "recaptcha.net", and CloudFlare's CAPTCHA has exactly the same problem, whose domain is "challenges.cloudflare.com".

If the cookies aren't set and passed back, then they can't know that you've solved it, so you get another one.

mindslight 20 hours ago

You're blaming Mozilla because they fixed a security vulnerability, and then saying that the workaround is to reenable the vulnerability so that Google can continue surveilling.

Reply View 0 replies

BolexNOLA 21 hours ago

Yet for some inexplicable reason all the other bot detection methods I encounter online don’t struggle at all with me and don’t stick me in infinite loops. Cloudflare for instance simply does not bug out with rare exceptions for me.

Maybe my experience is atypical but it seems to me this is a reCAPTCHA problem, not a Mozilla one. It’s Google’s problem. I imagine they can solve this but simply don’t want to.

Maybe I’m wrong but again, i encounter more issues with their “anti bot” methods than any other by a massive margin.

Reply View 0 replies