Brutkey

Marcin Wichary
@mwichary@mastodon.online

A classic rule for these: show them after I invoked an action that lets me connect the permission to the intent, or explain the reason. Other dialogs like these are usually much better at this (for example: asking for permission to a Documents folder when I try to save a file). I am not sure why this one is so awful.

MattStudies
@mgaudet@discuss.systems

@mwichary@mastodon.online I think you put your finger on why it's so awful in your first post: 1) It's a deeply ambiguous permission that's very hard even for an expert to build a mental risk model around (compare to the Documents example). 2) The connection between your action and the dialog is very obscured. 3) It's very unclear what happens if you say no! Can you change your mind later? if so, where?

I love the idea of programs having to ask for consent, but the practical form of it can be deeply exhausting.