this post was submitted on 24 Oct 2024
489 points (99.4% liked)
Technology
59612 readers
3492 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I remember when Bluetooth started demanding location permissions. You'll never convince me that it's functionally required or provides any benefit other than furthering efforts to spy on the user.
When it started being rolled out, I avoided any app or hardware that made that demand. Sadly, that's no longer an option if I want any Bluetooth at all.
It's not like Bluetooth started demanding location permissions, the conceptual model of the permission was revised: having access Bluetooth means an app could determine your location via a form of lateration.
In earlier versions of smartphone operating systems, this was not transparent to users lacking the technical background, so Bluetooth also requiring location access is actually an attempt at making users aware of that. I'm not an iOS developer, so I can't comment on iPhones, but on Android versions prior to 11, having access to Bluetooth meant an app would be able to determine your location.
Today, you can require the permission
ACCESS_FINE_LOCATION, which expresses that your app might use Bluetooth to obtain location information on Android. Also, if you're just scanning for nearby devices to connect your app to, but don't want users to be confused why your smart fridge app needs to know your precise location, you can declare a permission flag (neverForLocation) and Android will strip beacon information from the scan results, better asserting your intentions.So, overall: no, there is nothing nefarious going on, it was always possible to determine your location via Bluetooth, and the update to the permission model was an honest improvement that actually benefits you as user.
Now, there are still plenty of shady apps around, and apps that are poorly written - don't use those.
I knew that someone would try to convince me. You won't convince me.
... Though your argument is pretty compelling.
I don't think he wanted to convince you, he just explained the backgroundon how you can track locations with bluetooth.
I believe it's only required during the pairing process, but as the other observer pointed out, I don't know much about it. If you're able to circumvent the process, more power to you!