Sure, and that's part of why they switched to that model a few years ago. You can toggle off permissions for apps using the legacy permission model and they get provided with empty / zero data but that has awful usability. Users will forget they did it and will hit issues.
-
-
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.
1 reply 0 retweets 1 like -
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 -
Replying to @CopperheadOS @RichFelker and
Setting up a bunch of traps for users and pushing complexity onto them is not proper privacy / security design. Silently blocking things in the background with users being able to see it's happening is completely broken. It's broken whether it's domain-based ad-blocking or this.
1 reply 0 retweets 0 likes -
iOS also has a couple of these traps. Location services are needed to access photos that contain location services. Not immediately intuitive, but the OS is kicking around.
2 replies 0 retweets 0 likes
Seems iOS should just prompt & present a version of the image with EXIF stripped when app lacks location priv.
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.