Apparently, Android now requires browsers to have the "Nearby devices" permission just to access a website on your own LAN.
I miss when computers just let you... you know, compute.
Apparently, Android now requires browsers to have the "Nearby devices" permission just to access a website on your own LAN.
I miss when computers just let you... you know, compute.
@fribbledom I found out yesterday that [UPDATE: on Android,] out of DuckDuckGo, Firefox and Chrome, only the latter will even let you open a local .html file. (None of them have a File->Open dialog, but at least Chrome accepts share-intents)
Like: A browser, not made to open an html file. Come on ...
@Chaos_99 @fribbledom whaat? I open local html files on Firefox all the time - is this on mobile or something?
@fribbledom Back then, apps could scan your whole LAN and you wouldn’t notice. How is it not better with that permission control? I’d say most apps definitely don’t need to connect to my local network.
@lx @fribbledom Agreed, if LG are brazen enough to scan your network for devices to use for marketing/id purposes the flashlight app with in app purchases definitely would be too.
I think the one that also grinds my gears is when an app needs access to my location to use Bluetooth. Good faith presumption is that it's because 'location' permissions are too broadly categorised which snatches up bluetooth use cases, but it'd be great if we had a more granular option.
@BenjaminNelan @fribbledom True, but AFAIK that has changed in Android 12 with "Nearby Devices" that is now no longer a location permission.
Because of BLE beacons and such you could determine someone’s location by scanning Bluetooth devices, so it makes sense to raise awareness.
Hmm... It is no better because it is the *wrong* permission to require?
The right approach would have been a new permission called "access LAN".
Like, why do I need to allow location access to find nearby devices? I don't need to know my GPS location, I just need to listen to BLE or Wifi.
@aaribaud @lx @fribbledom Both of those are used to infer your approximate location.
@aaribaud The point was not the kind of permission requested but the fact that one was requested at all instead of "just let you compute". Many people don’t even know what a "LAN" is and don’t care if it’s WiFi or Bluetooth, so "Nearby Devices" seems reasonable.
@fribbledom The part that bothers me is the category error: "nearby devices" bundles your own LAN in with other people's Bluetooth. The threat it's addressing is real, but the name teaches users to tap Allow without thinking — which is exactly the habit the permission was supposed to break.
@fribbledom same for macos: I can access the wider internet but not the local network at work unless I switch that on. Which is utterly bizarre as our "local" network does not use local network addresses but the university's public block.
@fribbledom desktop browsers too, I think.
@fribbledom I honestly have no idea what I'm going to do when my current phone needs replacing.
@fribbledom But that is _exactly_ what the "Nearby devices" permission means: Talking to computers on the non-public internet. The web platform is about to follow the same pattern as established by the app platforms, unfortunately.
This annoyance is - by the way - brought to you by Meta and https://localmess.github.io/
@fribbledom
Graphene OS works the way you want and lets you set granular permissions per app.