Providing empty data means the apps stop providing the functionality users expect, and the apps can't check to see that the permission is gone to request it from the user. It's a major usability issue. It works for power users, it doesn't work for regular people.
-
-
The user cares. Their apps are broken and they can't figure out why. Not having empathy for users and designing privacy / security features in ways that aren't friendly to them and usable by them is not the way to go.
-
You've never presented one plausible example of a behavior a user actually wants breaking when gaping privacy holes are fixed.
-
We've had years of experience of providing support for an OS taking a much more aggressive approach to privacy and security features. Our users also make much more use of the standard privacy/security features. Are you seriously denying that people regularly hit issues with it?
-
None of you are at all familiar with how it works and don't even seem to have experience *using* a current Android phone, let alone experience working with non-technical people or even just non-programmers / non-cryptographers using this kind of software. :\
-
It's really silly trying to explain to us how it works or what the pitfalls are when we have a lot of experience with it. Could go on long rants about everything that's wrong with it and what they should be doing but it's not at all what people without experience keep claiming.
-
If you want to talk about garbage privacy how about both Android and iOS granting apps access to sensors without needing any permissions. Can do coarse 100-200Hz audio recording (ML -> detect speech), track movement (ML -> match to routes to find location), etc. with 0 perms.
-
Being able to explicitly grant apps access to get phone state information and SMS/MMS/RCS data has nothing on that. At least that's something you have to very explicitly consent to doing and you can change your mind for future data.
-
Not sure what's hard to understand about the major usability issues of silently blocking stuff with no UI presented when it's happening. It's the #1 support issue that we have to deal with: using silent ad-blocking, disabling root CAs, disabling permissions / apps.
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.