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.

▲

halapro 5 hours ago | parent [-]

No browser supports Bluetooth.

▲

nerdsniper 4 hours ago | parent | next [-]

These passkey QR codes don't need to use Web Bluetooth API, because they utilize the WebAuthn API. The website itself isn't given access to the bluetooth, the task is handed off to the browser, which as a native application, can access bluetooth and abstracts the bluetooth away.

▲

LoganDark 5 hours ago | parent | prev [-]

Chrome does...

▲

drusepth 5 hours ago | parent [-]

Interestingly, only on desktop/Android and not iOS it seems.

	▲	LoganDark 4 hours ago \| parent [-]
		Chrome on iOS uses WebKit, so that makes sense. (*I think in the EU, iOS Chrome can use Blink, but I am not sure if it actually does.)