You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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:
@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.
The text was updated successfully, but these errors were encountered: