How is this added permission not a good thing? Surely adding a local network only permission is a positive, you can allow apps internet permission and decline them access to your local services.
Comment on How is everyone dealing with Android 17's "Nearby Devices" change?
curbstickle@anarchist.nexus 13 hours ago
Haven’t been brought to 17 yet thankfully.
My long term solution is to not use android. My short term solution will likely be to use android even less, and be even more pissed at Google.
superglue@lemmy.dbzer0.com 8 hours ago
curbstickle@anarchist.nexus 8 hours ago
The permission structure sucks.
Its a silent drop (no errors are returned), webview breaks connected to WiFi even without a local resource being requested, it lives inside nearby_devices so giving permission there includes this (and gives a broader spectrum of access such as Bluetooth and WiFi).
Its just shuffling the problem around.
Also, fuck Google.
JetpackJackson@feddit.org 12 hours ago
Linux phone?
Colloidal@programming.dev 12 hours ago
Flip phone
BeatTakeshi@lemmy.world 9 hours ago
LostCarcosan@lemmy.today 2 hours ago
Bananaphone
femtek@lemmy.blahaj.zone 10 hours ago
Solution is to just enable the permission on apps that need it.
curbstickle@anarchist.nexus 10 hours ago
The solution is to avoid google going forward, for many reasons.
femtek@lemmy.blahaj.zone 9 hours ago
That’s why I use graphene but the permission is still there in base android.
pHr34kY@lemmy.world 4 hours ago
I’m actually using GrapheneOS.
curbstickle@anarchist.nexus 8 hours ago
The problem with graphene, unfortunately.
It doesn’t actually get away from google, at best its plugging holes in a (to me) sinking ship.
pHr34kY@lemmy.world 4 hours ago
It would be annoying to do that for everyone who uses my wifi.
I found that “Conversations” (XMPP) was blocking a connections even when the permission was enabled. I suspect Android no longer allows connections on port 5xxx on a local network. It works fine when the IP is external.