-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add UX considerations section #49
Comments
Do we have any security considerations, or is this just "There are no known security impacts of this feature." |
I don't know if we have gone through Mike's questionnaire. We should do that (maybe post the questions at the top, and we can all edit them and then put them in the spec?) We should also provide a link to the repo asking people to report any privacy/security issues/concerns here. |
There's obvious impacts, right? Poorly designed UX can lead to users exposing themselves to attackers. |
@annevk, absolutely. The same with presenting multiple permissions at once, which can lead to information overload. |
A few ideas: UAs should take care to present permission dialogs in such a way that users can understand the implications of a permission, etc. Permission fatigue is a thing, etc. Something about permission spam, etc. Security UX implications. Some stuff for inspiration: https://www.w3.org/Privacy/permissions-ws-2018/papers/martin-thomson.pdf is pretty decent as well. |
No description provided.
The text was updated successfully, but these errors were encountered: