Skip to content
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

Duty of Honesty #401

Open
chrisn opened this issue Feb 2, 2024 · 6 comments
Open

Duty of Honesty #401

chrisn opened this issue Feb 2, 2024 · 6 comments

Comments

@chrisn
Copy link
Collaborator

chrisn commented Feb 2, 2024

In Section 1.4, Honesty is currently qualified with "as long as they can understand it" (i.e., the user). I suggest that honesty should apply regardless: how is the UA to know what the user understands? I would also suggest that "try to give its user information" is a bit too weak, maybe "should give"?

@jyasskin
Copy link
Collaborator

Note that "as long as they understand it" qualifies the given information, not the UA's honesty. I do think the "as long as they understand it" is an important part of the concept we're trying to get across here, but like many parts of this document, perhaps it could be worded better.

Specifically, the UA has access to lots of information that might improve the user's autonomy if the user understood it, but it's not a good idea to just dump that information on all users. Think about the details of the current TLS connection: the UA needs to pick and choose from all the available information in order to show the user things they're likely to understand and be able to act on.

@darobin
Copy link
Member

darobin commented Feb 28, 2024

@chrisn Do you feel that addresses your point?

@chrisn
Copy link
Collaborator Author

chrisn commented Mar 11, 2024

Sorry for the delay....

I think #403 is a good change, and I get the subtleties that @jyasskin describes. But to me, these fall more under "transparency" than "honesty". Transparency is well covered in 2.11, but the text here indicates that "honesty goes well beyond that of transparency" but without clearly explaining the distinction (aside from an example of not hiding behind complex legal notices). I don't have a good suggestion, as it's not clear to me what is the distinction you're looking to make.

My original comment was based on the observation that by saying "as long as they can understand", we're in effect leaving it to discretion for each UA to make its own design choice on the level of transparency/honesty to provide. But maybe that's the best we can do here.

@darobin
Copy link
Member

darobin commented Mar 11, 2024

No worries, we're all busy.

Basically, transparency is how the Vogons do it: "It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard." Honesty is taking credible steps to make sure that the person has the information they need and understands it.

If that's not getting across, we're doing it wrong. Maybe we should actually cite H2G2?

@jyasskin
Copy link
Collaborator

FWIW, while "transparency" gets used that way by folks who want to get lots of people's data, the point of that bit of the Hitchhiker's Guide is that it's not really transparency. We could try to defend and reclaim the word, instead of fleeing to another word ("honesty") that'll get mis-defined and corrupted in the same way.

@darobin
Copy link
Member

darobin commented May 8, 2024

We will process this when we split out a UA document, post-Statement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants