I’m convinced the person that put it together has never touched a faster-paced mouse+keyboard game in their life, because clicking all the correct squares too fast also causes the test to fail
Just use a click delay program between press and input, maybe with a physical on/off switch on a dedicated keyboard next to the mouse together with other necessary keys (like the one button switch between EN and SE layouts or the Memory Cache Dump Key)
But you’re right, the UX sucks, and there are other ways to detect and limit bots that don’t impact legitimate users as much - but Google needs to train their AI, and developers need to cargo cult stuff.
I’m convinced the person that put it together has never touched a faster-paced mouse+keyboard game in their life, because clicking all the correct squares too fast also causes the test to fail
Nah, you’re a robot man. We caught you.
I’m Kilroy.
just as what the wise Mahatma Gandhi, when faced with similar allegations, would say before summarily nuking all opposition: “GG EZ”
These things feel like they are made by microsoft. You click somewhere, wait 3-10 seconds and then you can click again.
Just use a click delay program between press and input, maybe with a physical on/off switch on a dedicated keyboard next to the mouse together with other necessary keys (like the one button switch between EN and SE layouts or the Memory Cache Dump Key)
That’s what a bot would say /s
But you’re right, the UX sucks, and there are other ways to detect and limit bots that don’t impact legitimate users as much - but Google needs to train their AI, and developers need to cargo cult stuff.
A bot trying to solve the captcha would be very fast so it makes sense that they block fast solvers.
A bot would be exactly as fast as possible, while staying below the detection threshold.