I’m okay with older apps losing functionality. The OS can provide some warnings too, to help users understand why the app isn’t working if the app is too old to understand. Breaking some older apps is better than leaking everything always.
-
-
You're describing what they implemented: newer apps use runtime permissions (disabled by default, need to be requested) with proper exceptions. Older apps have toggles enabling empty / fake data and the permissions review mode has users review / toggle before they can run.
2 replies 0 retweets 0 likes -
Great, I’m describing what they did. Why wasn’t it in 2 or 3? Or 4.2 which had it, but hid it so users wouldn’t accidentally get control of their information?
1 reply 0 retweets 0 likes -
Had that discussion a few times in this thread.
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS @TheDaveCA and
Being able to toggle off permissions even for legacy apps not supporting a runtime permission model is a feature that's present. However, it has awful usability. Users will toggle off permissions and forget about it. They won't realize why the apps aren't doing what they want.
1 reply 0 retweets 0 likes -
You keep saying this. Who cares? Failing safe is the only remotely reasonable behavior here. App not working is no problem. App hideously violating user's privacy is.
1 reply 0 retweets 1 like -
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.
3 replies 0 retweets 0 likes -
You've never presented one plausible example of a behavior a user actually wants breaking when gaping privacy holes are fixed.
1 reply 0 retweets 0 likes -
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?
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker and
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. :\
2 replies 0 retweets 0 likes
I use (near-)current Android in the form of LOS.
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.