3 ms·
This is just one more reason to use a secure operating system such as GrapheneOS which has implemented a sensors toggle for all apps: https://grapheneos.org/fe
by poisonoushydra 5y ago
This is just one more reason to use a secure operating system such as GrapheneOS which has implemented a sensors toggle for all apps:
https://grapheneos.org/features https://grapheneos.org/features
"Sensors permission toggle: disallow access to all other sensors not covered by existing Android permissions (Camera, Microphone, Body Sensors, Activity Recognition) including an accelerometer, gyroscope, compass, barometer, thermometer and any other sensors present on a given device. To avoid breaking compatibility with Android apps, the added permission is enabled by default."
- afavour 5y agoOn the other hand, the nature of Apple’s BDFL ownership means that they could very easily add a permission prompt in an iOS release, allowing them to default to disabled, then tell app developers to update their code or go to hell. They’ve done it before with other APIs. In fact they’ve already done this on the web: the DeviceMotion API is behind a permission prompt. I’m surprised the same isn’t the case for apps.
- derekjdanserl 5y agoIf Apple did that, giant app developers would whine about it. Google was basically responsible for locking down the DeviceMotion API.
- e_proxus 5y agoGiant app developers do complain about it (see the ad tracking debacle). That hasn’t stopped Apple in the past.
- afavour 5y agoIIRC Apple locked down the Contacts API precisely because giant app developers were abusing it. And look at the recent ad tracking stuff that Facebook hates: I don’t think Apple is all that afraid of angering developers, big or small.
- _rdvw 5y agoMy https://divestos.org https://divestos.org offers per-app sensors permission toggle and a global sensors/camera/mic toggle to many more devices.