4 ms·
I'm really confused. I'm reading the spec[0], which seems to explicitly state that it's not possible (modulo some possible vulnerabilities with mitigations tha
by kelnos 6y ago
I'm really confused. I'm reading the spec[0], which seems to explicitly state that it's not possible (modulo some possible vulnerabilities with mitigations that they later list) to track a user across the web using these tokens. Yet many of the comments I read here are talking about this being a way for websites to track users?
This spec document also doesn't really list use cases for this. Why would I want this? The linked article seems to suggest it's so Google can reduce ad fraud, which of course I don't give a damn about, and don't want my user agent doing anything that helps advertisers, ever.
Hopefully Firefox does not implement this, and hopefully if they don't, websites don't somehow penalize browsers that don't support it.
[0] https://github.com/WICG/trust-token-api#overview https://github.com/WICG/trust-token-api#overview
- jsnell 6y agoI don’t even think this is for Google’s benefit. They don’t need these tokens, since the vast majority of their ad revenue is first party. But do you know what happens the moment Chrome disables third party cookie support? People will start complaining that it’s an anti competitive move against businesses with a stronger need third party cookies.
- KenanSulayman 6y agoGoogle does not need any cookies for Google properties because Google Chrome sends an `x-client-data` header to them.
- jefftk 6y agoThe x-clint-data header is for experiments, not personalization: Additionally, a subset of low entropy variations are included in network requests sent to Google. The combined state of these variations is non-identifying, since it is based on a 13-bit low entropy value (see above). These are transmitted using the "X-Client-Data" HTTP header, which contains a list of active variations. On Android, this header may include a limited set of external server-side experiments, which may affect the Chrome installation. This header is used to evaluate the effect on Google servers - for example, a networking change may affect YouTube video load speed or an Omnibox ranking update may result in more helpful Google Search results. https://www.google.com/chrome/privacy/whitepaper.html#variations https://www.google.com/chrome/privacy/whitepaper.html#variat... (Disclosure: I work for Google, speaking only for myself)
- ocdtrekkie 6y agoHowever Google claims it is used, it's a fingerprinting strategy that only a company with Google's level of monopoly in controlling both the biggest browser and the biggest several websites can employ.
- jefftk 6y agoFor it to be a fingerprinting strategy it would need to be used for fingerprinting, and that page has Google publicly claiming that it is not. I'm not a lawyer, but I would expect if Google were not telling the truth here it would go very poorly for them.
- ocdtrekkie 6y agoBut Google has been not telling the truth on all sorts of things, and Google is under investigation by the federal government, 49 US states, the European Union, and several other entities for misconduct and illegal activity with regards to both monopolization and privacy violations. The idea that it'd go very badly if Google were to lie may be true: And Google is currently going through exactly that. To ask us to "trust your word" while you're actually actively being accused of a lot of misconduct by a lot of very reputable sources is... kinda hard to buy into? We gave Google the benefit of the doubt for far, far too long, and it screwed us. We're done trusting you.
- jefftk 6y agoWhat I'm claiming is not specific to Google. In general, large companies very rarely take a strategy of publicly saying "we don't do X" and then trying to secretly do X. It doesn't work out well for them, because they aren't the kind of entity that can pull off that kind of deception. Documents get subpoenaed, auditors look at things, whistleblowers release things, things get leaked. You're referencing anti-trust and privacy investigations, but those don't seem to be about lies?
- ocdtrekkie 6y ago
- nwellnhof 6y agoTrust tokens are only one of several separate proposals to remove third-party cookies. The so-called Privacy Sandbox will also include other technologies. Tracking cookies are planned to be replaced with Turtledove and FLoC. The latter is about running machine learning algorithms in your browser to infer your interests. https://www.chromium.org/Home/chromium-privacy/privacy-sandbox https://www.chromium.org/Home/chromium-privacy/privacy-sandb...
- nxpnsv 6y ago> machine learning algorithms in your browser nope...
- eis 6y ago> The latter is about running machine learning algorithms in your browser to infer your interests. Oh nice, sounds like my information will now not only be sent to someone else, I even will be doing the computation for them to increase their margins and pay with reduced battery life. Awesome!