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

Double-check "unwanted" recognition #140

Open
jyasskin opened this issue Apr 7, 2022 · 1 comment
Open

Double-check "unwanted" recognition #140

jyasskin opened this issue Apr 7, 2022 · 1 comment
Labels
backburner consider closing At least one person thinks this issue is resolved

Comments

@jyasskin
Copy link
Collaborator

jyasskin commented Apr 7, 2022

In patcg/patwg-charter#6 (comment), @alextcone is worried that our use of "unwanted" in https://w3ctag.github.io/privacy-principles/#hl-recognition-cross-context is likely to be too load-bearing for their use:

The adjective “unwanted” is going to end up carrying more water than you might expect or…want. Determining and subsequently demonstrating whether something is wanted or not is less than straightforward and, as it relates to digital advertising, explosive and in flux. I suggest removing “unwanted” or at least not using a euphemism for consent, which this group is not scoped to design for in any sort of holistic, consistent across all data processing manner. User controls are certainly important to consider as we advance designs for individual purpose limited APIs. For example, I think @benjaminsavage’s example that IPA shouldn’t work if user agent storage or device storage is cleared might be something we choose to standardize. But we can do that without adding ambiguity to the charter.

@benjaminsavage did add "unwanted" to our "same-site recognition" section, where we didn't use it, but we've been leaning on the concept of user "wants" in a couple places, so I wanted to flag that a concern has been raised about it.

@jyasskin jyasskin added this to the post-fpwd milestone Apr 7, 2022
@benjaminsavage
Copy link

Thanks for flagging jyasskin. I think there is another reason to be cautious about phrasing that means into what a user supposedly "wants". This relates to a point that @darobin made in his presentation yesterday, which is that we cannot lean too much into individualistic approaches. Many people do not have the time and expertise to acquire enough depth of context to make determinations about what they might really want (should they possess all the relevant information and context and expertise). Instead, he recommended a collective approach.

In the case of same-site recognition across storage clears, rather than trying to ask individuals what they each "want" here, a sensible default (not recognisable across storage clears) might be the best collective approach.

@darobin darobin removed this from the post-fpwd milestone Jun 27, 2022
@darobin darobin added the agenda+ Add to the next call's agenda. label Jun 27, 2022
@torgo torgo added backburner consider closing At least one person thinks this issue is resolved and removed agenda+ Add to the next call's agenda. labels Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backburner consider closing At least one person thinks this issue is resolved
Projects
None yet
Development

No branches or pull requests

4 participants