|
|
|
|
|
by nodamage
1433 days ago
|
|
> More restrictive and more transparent handling of permissions. Maybe this mechanism was caused by Uber bundling some sort of library that led to permissions leak. Perhaps the OS could expose that permission being triggered. I don't think you've thought this all the way through. Once a user grants me permission to send them push notifications because they want to know when their ride shows up, you can't really stop me from pushing them ads through the same channel. |
|
> Once a user grants me permission to send them push notifications because they want to know when their ride shows up, you can't really stop me from pushing them ads through the same channel.
Wait, can't an improvement upon the OS be to make it more granular so that Uber is forced to establish separate permissions channels for rides (vital) vs. ads (not-so-vital), and that every time a notification of a certain type appears, the user is given the option to mute that channel entirely?