3 ms·

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 s

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 5mo ago
No browser supports Bluetooth.
- LoganDark 5mo ago
  Chrome does...
  - drusepth 5mo ago
    Interestingly, only on desktop/Android and not iOS it seems.
    - LoganDark 5mo ago
      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.)
  - halapro 5mo ago
    That's news to me https://developer.mozilla.org/en-US/docs/Web/API/Web_Bluetooth_API https://developer.mozilla.org/en-US/docs/Web/API/Web_Bluetoo... Websites cannot use Bluetooth anywhere. The QR codes shown in the blog post are not passkey QR codes, which is likely what's confusing you.
- nerdsniper 5mo ago
  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.
  - halapro 5mo ago
    That's passkey QR codes generated by the browser, it has nothing to do with random QR codes offered by websites.