Re: [w3ctag/design-reviews] HTTP State Tokens (#297)

Oops, never replied about my concerns about first-party tracking from https://github.com/w3ctag/design-reviews/issues/297#issuecomment-434996368

My concern was that today, if a user visits example.com and it sets a cookie or uses any other storage API, there's something that the page does *actively* to store data.  So it's detectable that the page is doing *some* form of data storage (which could be used for tracking) in a way that not all pages do -- and in a way that something like a browser extension could indicate to a user who's interested in knowing about that and monitoring which pages do some form of tracking or data storage.

If instead the page gets a token automatically, then such UI would essentially flag *every* page on the web as doing tracking, and would become completely useless.  (It's not clear that it would be all that useful today, but that's another debate...)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/297#issuecomment-442339681