31–40 of 467 posts
Why can't an AI scan the QR code? Just fire up an emulator if necessary
Bluetooth is generally used to prove that the two devices are co-located, which makes it more complex to do your proposed kind of deployment at-scale. Bespoke solutions could perhaps work around for some smaller number of devices, this QR code layer by itself isn't intended to stop 100% of workarounds.
The fact that mobile devices are now mandatory to prove "humanness" means that Google no longer trusts desktop/open platforms anymore.
Where is this specified? I don't see that in TFA.
But tactics like this will make that nearly impossible if every website starts requiring a QR code scan on a authorized smartphone.
Earlier quoted context omitted.
Bluetooth is generally used to prove that the two devices are co-located, which makes it more complex to do your proposed kind of deployment at-scale. Bespoke solutions could perhaps work around for some smaller number of devices, this QR code layer by itself isn't intended to stop 100% of workarounds.
No browser supports Bluetooth.
Google building harder walls against bots while simultaneously building AI agents that need to get through them is peak 2026.
Earlier quoted context omitted.
Yeah, I had the same question myself. I think that's what you would want to do to make it airtight (plus some amount of rate limiting or flagging for devices that are part of dedicated device farms). But even if not, there's still value in raising the barrier to entry. For example, you can buy 1000 reCaptcha solves for $1-2 from various captcha-solver services. And yet that $0.001-per-request fee does discourage mass…
... You... think... it would be a good thing. Don't you...