Closed esgoodman closed 9 years ago
It manifests right now most obviously in the sign-in flow.
Per-item permissions slow people down. Convenience optimizers may not even look at them. Each separate permission gives privacy defenders and [privacy sensitives] more to worry about.
Facebook has been doing per-item permissions for more than a year, with reasonably good results. If they can make it work, so can we.
Here's an example of how FB does it.
@esgoodman: Could we offer a single name field instead of first name/last name? That would reduce the current # of permissions-related fields by a third.
+1 on a single name field if we can do it, because it takes care of some of the typical name problems. However, given the number of govt forms that require separate first and last name entry, we may not be able to get away with this. (Or we could just make it the RP's problem)
Closed by popular demand (or at least, silence) after the coworking meeting. We are agreed to keep going with the per-item permissions.
There is a predictable yet difficult to resolve tension between making consent meaningful and not getting in people's way. The more information we give people and the more we ask them to make decisions, the more we get between them and the job they want to get done.