| ▲ | skissane 3 hours ago |
| The big problem with these permission dialogs, is their lack of technical detail about what the app is actually trying to do which triggers them. How do I know whether to say "Allow" or "Disallow" when it gives me no idea what either option actually means in concrete? |
|
| ▲ | joshuat 2 hours ago | parent | next [-] |
| This also happened on iOS when they began to prompt users before apps could access the clipboard. I built an app that would handle the inbound redirect automatically if you had a relevant URL in your clipboard - did this for years with many users happy with the feature. Then it started prompting users before allowing them to paste, and then the claims of privacy violations began to come in. If instead I were able to specify what was happening in the prompt rather than iOS giving users an ambiguous statement, or even provide a detection pattern, it wouldn't have been nearly as bad. I feel like this really harms security and privacy awareness by flooding the field with unimportant prompts/warnings to the degree that a real issue is similarly ignored because it is assumed to just be noise. |
| |
| ▲ | dd8601fn an hour ago | parent | next [-] | | > If instead I were able to specify what was happening in the prompt rather than iOS giving users an ambiguous statement No. They’re correct, there. The app developer should not get to provide the message text for a prompt like that. A secondary note somewhere in less than ten words, maybe, where it explicitly warns that the statement may be false. | | | |
| ▲ | ryandrake 2 hours ago | parent | prev | next [-] | | I think the visibility of these dialogs serves as a warning to the user--but they should do a better job directing the user's attention to where the threat is. If the user is getting annoyed at all these pop-ups, he should direct this annoyance at the developer who is (in all likelihood) asking for access to more of the user's computer than he needs. The fact that there are so many popups should mean apps are reaching for access to your system way beyond what they should be. It shouldn't mean Apple needs to get rid of the pop-ups. | | |
| ▲ | mook an hour ago | parent | next [-] | | I get the pop-up semi-frequently from Chrome. I don't think complaining to Google has ever helped with anything; but then it's not like complaining to Apple has a better track record. Yes, I don't know why the OS isn't tracking the pop-up by bundle id or anything. It's not like I changed my mind the last dozen times… | | | |
| ▲ | johncassil an hour ago | parent | prev [-] | | Regardless, apple should definitely not send popups unless an app is being engaged with. |
| |
| ▲ | internet2000 30 minutes ago | parent | prev [-] | | Counterpoint: do not read my clipboard without any action on my side, dude! |
|
|
| ▲ | OptionOfT 2 hours ago | parent | prev [-] |
| Well, usually the answer is no, and then when something breaks the app will tell me. Which reminds me. Why does the CVS app need access to Bluetooth? |
| |
