I think it's almost always an error to frame technology discussions in terms of "privacy" rather than "consent." The word "privacy" is just too ambiguous, and muddies the distinction between a system's security model and what a user has reasonably consented to.
-
Show this thread
-
This leads developers into the trap of applying the wrong solution–either dumping a security problem on the user by forcing them to make an impossible consent decision, or erroneously treating a consent decision as something that can be implicitly addressed in the security model.
1 reply 0 retweets 5 likesShow this thread -
We should really just avoid the word "privacy," and instead clearly differentiate concerns between what security guarantees a model should reasonably provide, and what UX is appropriate to obtain genuinely informed consent for data used or actions take on the user's behalf.
3 replies 2 retweets 10 likesShow this thread -
Replying to @justinschuh
That sounds reasonable if you can convince users to agree that those are the concerns and get them to use that new language. However, as long as users (real users, not just forum posters) have "privacy" as a concern, we shouldn't distance ourselves from their concern w/ newspeak.
1 reply 0 retweets 0 likes
Also, when we use the more vague language like "privacy" and try to address concerns with that broad term, I think it motivates us to solve more of their concerns. More precise language that lets us break "privacy" down into smaller nuanced points encourages us to disregard some.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.