about://config (ok, chrome://config) is gone Nothing Bluetooth is in chrome://flags Google search results are their usual, these days, jumble of largely usele

about://config (ok, chrome://config) is gone Nothing Bluetooth is in chrome://flags Google search results are their usual, these days, jumble of largely uselessness. In the context of a relatively quick search and results skimming, this result is dated 2015 but still seems to be pertinent. It is also the link that is cited in the OP's linked announcement. https://developers.google.com/web/updates/2015/07/interact-with-ble-devices-on-the-web https://developers.google.com/web/updates/2015/07/interact-w... In particular, where it says: https://developers.google.com/web/updates/2015/07/interact-with-ble-devices-on-the-web#dev_tips https://developers.google.com/web/updates/2015/07/interact-w... A "Bluetooth Internals" page is available in Chrome at chrome://bluetooth-internals so that you can inspect everything about nearby Bluetooth devices: status, services, characteristics, and descriptors. Checking the system I'm on, I'm not hooked up to any Bluetooth devices. I see the Status panel shown in the article, although it's not titled. Nothing else. There are two left-side tab-ish controls that let me switch between "Adapter" and "Devices". Devices shows the headset I was using the other week. It also has a button to "Scan". Nowhere, a browser-level control to turn this off. This is not acceptable. Google et al. are not going to stop. So, we are going to have to rewrite support for these stacks, and/or reconfigure how we run their apps and under what permissions, to cut them off. OS development (on "free" OS's, at least) is going to have to start assuming that applications the user actually wants and needs to run, can be and are at the same time at least partially hostile. Or, we just put up with this situation and being relegated to "cattle". I was just at a dairy farm the other week, and they now tag both ears -- so they don't even potentially have to take a step to identify the cow. This system uses Ubuntu 16.04, so supposedly control of this subsystem is more limited than on e.g. Windows 10. But there's no way I'm "relying" on that, all the more so going forward in time.