- From: Alexander Riccio via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Jan 2022 23:21:43 +0000
- To: public-web-bluetooth-log@w3.org
Hmm. I'm seeing another issue that makes the serial # blacklisting more of a problem. Basically, I'd like to tie a specific device-via-bluetooth to a specific instance of that device in my database. If users only have a *single* aranet4, this can work ok. But if they have multiple, how do I know programmatically which bluetooth device they've connected to? As their calibrations may be drifting differently (they probably will), this is a data-integrity problem. I just went ahead and looked into the `id` `BluetoothDevice` field, and I'm seeing that the way that it's implemented in google chrome is not at all repeatable. It's generated at runtime with a `crypto::RandBytes(bytes);` call! This is not repeatable or reliable. So how else can I make use of WebBluetooth? Honestly, it's looking more and more like I'll be spinning up a react native app. -- GitHub Notification of comment by ariccio Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/24#issuecomment-1007007949 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 January 2022 23:21:44 UTC