My comment in @TheRegister about the X-client-data header sent with every web browser request to selected (Google-owned websites), its role, the potential risks. Limited fingerprint-like ID. User control may be the issue. #GDPR #ePrivacyhttps://www.theregister.co.uk/2020/02/05/google_chrome_id_numbers/ …
-
-
DM ;-)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Why not simply tell everyone, rather than make snarky comments about people making commentary on what _could_ be done with the header. where's the "standards track, open" discussion of the feature that you boasted about yesterday?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Just to clarify, you *don't* think that it's egregious for Google to embed a unique identifier in Chrome that only gets sent in requests to its own sites? Why is it sent to doubleclick? How can one turn it off (rather than fire --reset-variation-state)? If it can't be, why not?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.