I still don't know whether you're supposed to hit those and I also don't know if it's normal to get two challenges or if that just means I did the first one wrong.
It doesn't really matter, they don't expect you to get everything right on these. While most of the time you need to get mostly right (Google is using these to train their AI so often they are not sure themselves), they are also looking at other things, like how you move your mouse, and the cookies that they use to spy on people to determine the probability of you being a human. If you pass a certain threshold they let you through, and you can do it even if you miss a square.
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.
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)
I still don't know whether you're supposed to hit those and I also don't know if it's normal to get two challenges or if that just means I did the first one wrong.
It doesn't really matter, they don't expect you to get everything right on these. While most of the time you need to get mostly right (Google is using these to train their AI so often they are not sure themselves), they are also looking at other things, like how you move your mouse, and the cookies that they use to spy on people to determine the probability of you being a human. If you pass a certain threshold they let you through, and you can do it even if you miss a square.
Nah, you’re a robot man. We caught you.
I'm Kilroy.
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.
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)
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.