2 ms·
> I wouldn’t feel safe enabling it for any app Then don't enable it, no need to take away my ability to do so. Granular permissions are good (especially when t
by zb3 1y ago
> I wouldn’t feel safe enabling it for any app
Then don't enable it, no need to take away my ability to do so. Granular permissions are good (especially when the app can't reliably know they were refused), providing I have the ultimate control.
> it’s a damned if they do, damned if they don’t scenario for Google.
Did they consider my scenario above - where the app doesn't know it was not granted a permission?
- IshKebab 1y ago> especially when the app can't reliably know they were refused That's the problem. Android didn't do this even though it was obviously what is needed. Android apps can easily tell what permissions they have. I think Google prioritised UX over power and security here. They were presumably scared about people accidentally clicking the "Silently deny" button and then getting confused when the app didn't work. Big missed opportunity.
- nolist_policy 1y agoBut the new API allows exactly this, the user can just give the app an empty directory. And Google even pushes apps to use it.