Similarly Android is a hedge against IOS and mobile search.
Would you be defending it if it was called "DoubleClick Browser"?
Google wants to secure the status quo with their own browser. What is the status quo? Massive spying, surveillance and tracking.
This is why Safari and Firefox implemented strict measures against third-party cookies which Chrome watered down until it was practically useless or didn't implement at all.
If Chrome is such an open and independent project, what do you think are the chances of a PR being approved that removed DoubleClick from the tracking header whitelist?
> Chrome was always a trojan horse to co-opt web standards for their own purposes
That wasn't the case. Google was concerned about Microsoft's ability to lock them out, and the lack of high quality browsers on non-Windows platforms.
https://chromium.googlesource.com/chromium/src/+/e51dcb0c148...
[1] https://9to5google.com/2020/02/06/google-chrome-x-client-dat...
See this post I made when X-Client-Header was introduced.
> But they claim [1] this X-Client-Data header is used for experimenting with Chrome, not for tracking.
They claim a lot of things. Sometimes they even modify their claims years after they first made them. Even if they were making 100% innocent claims now, they are not guaranteeing[2] they won't change how they use the data in the future.
> But you're claiming they're using it for tracking, so you're claiming they're lying...
Not at all - as I point out in [1], Google is saying they are tracking people with that header, but the claim is obfuscated by some blatant doublespeak and the hope that you only consider the X-Client-Header (or any other field with >0 bits of fingerprintable entropy) in isolation. That is never true, <i>which Google also admits</i> when e.g. they casually mention they can deduce a HTTP request's country of origin.
Asking if the X-Client-Data is "used for tracking" is the wrong question. They are tracking people using the combined set of all of the tiny pieces of data they are able to exfiltrate from you. Any specific piece of data isn't important; if that header was missing or corrupt, it's just a small amount of noise added to the already noisy correlations they do to fingerprint you to infer whatever they are interested in about your pattern-of-life.
No they don't. Nothing in your comment sounds anything like Google claiming to be tracking people. And as mentioned elsewhere in this thread, they explicitly claim to not be tracking individuals.
>> "The information included in this header reflects the variations, or new feature trials, in which an installation of Chrome is currently enrolled. [...] it is not used to identify or track individual users."
I believe this statement is true. They are not using the X-Client-Data HTTP Header to track "individual users". As they state in their "Privacy Whitepaper"[3], a "low entropy variation" is
>> randomized based on a number from 0 to 7999 (13 bits) that's randomly generated by each Chrome installation on the first run.
This per-installation 13 bit id number is sent in HTTP requests to certain Google domains:
>> [...] a subset of low entropy variations are included in network requests sent to Google. [...] These are transmitted using the "X-Client-Data" HTTP header. [...] This header is used to evaluate the effect [of the variation (presumably?)] on Google servers [...]
Google is explicitly saying they are tracking the new 13 bit id number. This particular id number is somewhat low granularity, due to the limited bit length, which - as Google correctly claims in their statement to the press - is too small to "identify or track individual users". Regardless, they are still claiming they track a 13 bit identifier tied to "each Chrome installation".
I never said the X-Client-Data header was enough to track individuals. An IP address doesn't uniquely identify individuals either. Google's use of language is hoping you stop there. The header is too small to be identifying, so it doesn't matter! This framing is only true if you limit your questioning to considering the "low entropy variation" number in isolation. If that was the only number Google was able to track, it indeed wouldn't be concerning. However, that number is probably transported to Google over the internet in an IP Protocol packet, meaning they are at a minimum also receiving either a 32 bit (IPv4) or 128 bit (IPv6) identifier in the Source Address field of each packet's IP Protocol header.
Google doesn't need to use the X-Client-Data header to "identify or track individual users". They can simply use it to disambiguate different Chrome installs that share the same public IP address. This usage of the number isn't identifying users; it's only identifying the different Chrome installs e.g. behind a typical household stateful NAT router. Both the X-Client-Data header and the IP address are both not unique personally identifying IDs. However, the tuple {X-Client-Data, IPv4 Address} is probably unique for most people. In the rare instance where it isn't unique, one of the related tuples like {X-Client-Data, IPv4 Address, User-Agent} will be.
The doublespeak is pretending the header "will not contain any personally identifiable information" when the stated purpose of header is to create a new tracking identifier that accomplishes the same thing as a personally identifying identifier when you combine it with the other data that Google already tracks (such as the 24 bits of "anonymized" IP address (they zero the LSB) that they store with each GA record.
[3] https://www.google.com/chrome/privacy/whitepaper.html#variat...
> when the stated purpose of header is to create a new tracking identifier that accomplishes the same thing as a personally identifying identifier when you combine it with the other data that Google already tracks
This is not stated anywhere except by you. The stated purpose of the identifier is to track analytics around chrome experiments, and only that.
The tuple (IPv4 Address, User-Agent) is already unique for almost all, so why go to all the effort?
Google are totally lying here.
If you never go to doubleclick yourself, chrome won't ever send data to it. It's not like a sneaky background thing. It's extra data attached to requests you were already making.
To a first approximation, _nobody_ "goes to doubleclick themselves".
At the same time, back in 2016 a study at Princeton found almost 50% of all sites on the web had Doubleclick on them (this is separate to the 70% of sites running Google Analytics - and I'd bet there's approximately zero sites that serve doubleclick ads/trackers but not google analytics ones, so there's even less way to spin this as being a necessary way for google to "understand experiments" by whitelisting the doubleclick domain...).
I never "go to doubleclick". My browser "sneakily in the background goes to double click" while I browse about half the sites on the internet.
"It's extra data attached to requests you were already making." is technically true, and gaslighting at it's most brazen.
If you asked your mom how many times she made a went to doubleclick today, what would she say? What would the actual answer be if we wanted to use the tortured terminology of "requests she was already making to doubleclick" from your apologia about your employer up there?
You took me to task for calling you a stooge and that being "against HN policy" elsewhere in this discussion...(Well, I said "stooge", you accused me of saying "shill", but whatever.) I guess I apologise for using the term "stooge" for someone who's told us they work at google and are telling lies about how Chrome is sending unexpected tracking data to Doubleclick. But it seems very much the right term.
How about instead I say that your statement "If you never go to doubleclick yourself, chrome won't ever send data to it." is a brazen lie, wrapped up in a weasel-wordy disingenuous interpretation of what 99.99% of people would clearly understand "go to doubleclick yourself" to mean?
I'll leave this argument now, with a quote for you and all googlers:
"It is difficult to get a man to understand something, when his salary depends upon his not understanding it!" -- Upton Sinclair
(Source for my 50% number: https://www.technologyreview.com/2016/05/18/160139/largest-s... )
> At the same time, back in 2016 a study at Princeton found almost 50% of all sites on the web had Doubleclick tracking on the
Means that many people are going to doubleclick, via it's ads existing on other sites. If the extent of your concern is that I said "going to" instead of "makes requests to", valid and I apologise for not being precise in my use of language.
However, the HN guidelines also ask that you respond to the strongest possible interpretation of what someone is saying. So please respond to what it is clear I meant, and not the straw man you feel compelled to attack.
And since that bit of rhetorical drama seems to at this point be the core of your concern, I don't know that theres anything of substance for me to address here, just more personal attacks.
> My browser "sneakily in the background goes to double click" while I browse about half the sites on the internet.
To be clear, this is false. Your browser isn't doing anything sneaky here. Perhaps you can argue that individual websites are being sneaky by including 3p advertising. That's a valid concern. But a browser "loading the HTML of the page you direct it to" isn't being sneaky or nefarious.
We all know the answer. Zero. Whatever your sneaky-browser-behaviour-depending employer wants you to say in public, her answer will be zero. Same as 99.99% of the world.
I think the behavior on display is pretty sneaky, undermines privacy and users aren't really informed about Google doing "research" on them.
But the question here is what part of this is sneaky? Is including a weird tracking header sneaky? Perhaps. Is making requests to doubleclick sneaky? In the context of those requests being made as part of a page load? Not on the part of Google, which is my point.
The original complaint was that the header was being sent
> That Google need to send "experimental headers" to a hardcoded domain for an advertising company they bought a decade or so back - because of course the results of web browser experiments should go to an advertising company
And the reason why is simple: that's the domain people are already making requests to.
"The X-Client-Data header is used to help Chrome test new features before rolling them out to all users. The information included in this header reflects the variations, or new feature trials, in which an installation of Chrome is currently enrolled. This information helps us measure server-side metrics for large groups of installations; it is not used to identify or track individual users."
Okay, so they're saying it is not currently being used to track individual users.
This means they can:
- Track individual users in the future.
- Track devices at any time, for differentiation of individual profiles.
- Track installs at any time.
- Derive information about the individual using this data (for example how often they update their browser, how often they use that device etc)
All of those things are extremely valuable from a data standpoint.
Unless Google explicitly stated that it was not being used to track, differentiate or profile users or devices and will not be used for that purpose in the future, it's extremely suspicious.
Most ad networks collect bulk information from browsers to fingerprint devices and users. Google has a step up on the competitor networks because they own the browser.
Do not forget Google was sued just this month for tracking users while they were using incognito mode.
If you want to say you think they're tracking people because of reasons X/Y/Z, or that what they're doing looks suspicious, that's a lot better of an argument. But to claim they are with no evidence of it actually happening is really pushing it.
Every single word of that statement was carefully crafted and constructed. Knowing that, why is it so ambiguous?
> Every single word of that statement was carefully crafted and constructed.
I also don't believe this to be true (their statement seemed plain and clear enough to my eyes), but even if it were, it doesn't affect what I said above. You need actual evidence, not the mere possibility of mathematical loophole.
They may not even be explicitly lying, because the statement is so ambiguous. When you're reading PR/legal speak then every single word matters.
Sorry, but you're not going to.
> They may not even be explicitly lying, because the statement is so ambiguous. When you're reading PR/legal speak then every single word matters.
Then say it's ambiguous, instead of saying the opposite is true, is all I'm saying. You misinform people that way.
Google lost the benefit of doubt years ago. This is Google 2020 - all they do is "track users":
https://www.reuters.com/article/us-alphabet-google-privacy-l...
https://www.compliancejunction.com/google-loses-appeal-of-e5...
> I might as well claim you're a burglar because there's nothing to indicate you're not one.
Google have been caught burgling houses repeatedly, and have been found in your house with burglary tools claiming "we're just doing, ummm, _browser experiments!!!_" You saying there's "no evidence of it actually happening " isn't useful.
Now, Firefox and Safari will protect customers against tracking (measures against third-party cookies) while Chrome won't do anything -- because that's where the cash is.
IE was steadily loosing ground to Firefox years before Chrome came around. You want to claim that Google feared the half starved stepchild that was IE more than the add blocking enabled Firefox that was eating up market share left and right?
> Microsoft owned the desktop with Windows and could easily shut Google out.
How would building your own browser help with that? If Microsoft managed to build its walled garden (which it tried) it could have just shut Chrome out.
Chrome is already entering its planed end game: Adblock APIs are crippled and third party cookies get the boot while all Google properties get an additional x-client-data identifier to uniquely identify its user.
https://9to5google.com/2020/02/06/google-chrome-x-client-dat...
Like, the function you're referring to, `IsGoogleAssociatedDomainUrl`, seems to only be used to log some information about https. Or at least that's all I found from searching for it. So it's even less innocuous, the use appears to be "we'd like to know if our sites are broken under HTTPS", vs. just HTTPS being broken in general.
[I work at Google, but don't work anywhere near chrome, and I know basically nothing about it]
Edit: You were referring to a different spot (experiments), where what I originally said applies. Having more analytics is really useful when trying to diagnose problems.
That leaves... ad tracking. Chrome will send a tracking ID to DoubleClick with every request to that host. Doesn't this prove that Chrome is a trojan horse used for ads and tracking purposes?
[1] https://twitter.com/jonathansampson/status/11654932064417792...
Wait what? You don't think there's analytics that can be done about the browser itself? Let's say chrome ships a new experiment, that when enabled on certain devices uses 100% of the CPU until chrome is closed. Analytics sent on browser startup would provide insight into that.
If you're asking why they need both:
having analytics in the context of a given page is also useful. If you can see that different experiments in chrome cause different performance impacts when loading the same page, that's also useful data that you can't get from analytics sent on startup. Nor could you centralize the logging of that information, as it would essentially be sending your browser history to Google all in one request, which is even easier to track.
> Doesn't this prove that Chrome is a trojan horse used for ads and tracking purposes?
Bluntly, no.
Do you think this "feature" is adequately disclosed to customers downloading Google Chrome, that it includes a DoubleClick tracking backdoor that no other ad network or website receives.
> that it includes a DoubleClick tracking backdoor that no other ad network or website receives.
is false, yes, I think the disclosures are reasonable. Your standard of disclosure is that companies need to disclose things that they aren't actually doing. That's ridiculous.
There are literally billions of dollars on the line.
Does Safari or Firefox implement a similar tracking header? If it's so needed for experiments, why is Chrome literally the only browser sending this data to their advertising network (or any site)?
If Google were using it for tracking purposes, they'd never confirm that unless forced to. Hence the ambiguous PR statement.
There's nothing ambiguous about "is not used to identify or track individual users.". Any form of personalized ad tracking would require tracking individual users, by definition. So there's your answer. Your attempts to create weaseling where there isn't any, so that you can continue to exclaim about the potentials for tracking don't actually change the ambiguity of the statement.
> How do you know they're not using it for tracking
Well I mentioned upthread I work at Google, right? Let me ask a question:
Google has historically been notorious for not being able to keep things secret, especially controversial things. How is it that Google is managing to keep this major component of tracking, that has to touch multiple major products and involve various teams a secret?
There's plenty ambiguous about that statement. Firstly, it doesn't cover past or future. Room for weaseling there. Secondly, it specifically says "track individual users", rather than include devices or just say "tracking" generally. Could they be tracking multiple users with the data point of "rarely updates browser"? According to that statement, they didn't rule it out.
That statement explicitly does not say they are not using that information to track devices or Chrome installs.
In fact, it doesn't even say it isn't a factor in ad targeting algorithms.
Given it was written by Google's highly skilled PR team, and not a developer, I'm inclined to believe they wrote this ambiguously for a reason. Google does not have a good track record with the truth or community goodwill (they stabbed Firefox in the back).
It's an advertising company making billions of dollars specifically from the use of tracking data. You're asking me to trust that said advertising company isn't using a tracking ID for tracking purposes when said ID is sent directly to their advertising domains.
Do you mean like, categories into which it divides users (age, gender, interest), in which case a reasonable answer is https://adssettings.google.com/ or do you mean what request attributes it uses to make these determinations initially and tie them to particular users? In which case the answer is primarily cookies: https://policies.google.com/technologies/types?hl=en-US.
You're asking me to prove a negative, and you're starting from the assumption that Google must be lying.
> In fact, it doesn't even say it isn't a factor in ad targeting algorithms.
How can something be a factor in ad targeting without being used to target individuals?
Really weird question. Easy. The tracking ID sent to DoubleClick could be used to target groups of people, such as "people who rarely update their browser". Such heuristics can indicate age, tech knowledge, etc.
No other browser is doing this. Why does Google need to send such tracking information to DoubleClick? You cannot justify it without also explaining why Safari and Firefox don't need this.
Coupled with Google's other self-dealing behavior such as refusing to crackdown on egregious third-party cookies like Safari and Firefox, then this is starting to look very suspicious.
For me personally, the fact this data is even being sent is the smoking gun. Shifting the goalposts to "well we don't abuse it" is classic gaslighting. You don't need to send tracking information to an advertising network.
Why should I trust an advertising network with a hard-coded, impossible to disable, opaque tracking backdoor in the first place?
Google does not disclose it does this. Google provides no way to opt out. Google has not adequately explained why it needs to send it to DoubleClick, given Google Analytics. Google snuck this into the Chromium source code hoping nobody noticed.
The hash sent to the various google websites when you make requests to them is determined by chrome/chromium on the client side, at approximately installation time. So this would require the RNG thats sitting in a publicly auditable source repository to be flawed and abusable in such a way that chrome could bias the hash based on various system attributes that we're just going to assume for the sake of argument are correlated with various ad demographics.
> Shifting the goalposts to "well we don't abuse it" is classic gaslighting.
I never shifted the goalposts. You just did. Please don't accuse me of gaslighting you when you're the one changing your argument.
> Why should I trust an advertising network with a hard-coded, impossible to disable, opaque tracking backdoor in the first place?
If you don't want to personally, that's fine. But don't presume to get no criticism when you accuse any person or group of actively lying based on literally no evidence.
> No other browser is doing this. Why does Google need to send such tracking information to DoubleClick? You cannot justify it without also explaining why Safari and Firefox don't need this.
There's a difference between "want" and "think it's the best decision". I'm certain there are people at both Apple and Mozilla who would prefer to have more robust client side analytics. I have no doubt about that. But whether they think that's worth the perceived loss of privacy is another question. Right now, Firefox has a comparative advantage with certain types of privacy conscious users. Why throw that away? The increase in development speed may not be worth the loss of user trust. And that's okay, but using that to then imply that Google is lying about things, again based on no evidence.
Let me put it this way: I trust Google (obviously), and so I'm fine to take them at their word that they aren't using this for ad targeting.
Someone who didn't trust Google could reasonably say "I don't put much faith in Google's press release", but without any other evidence that there's actually any targeting happening, the most you could reasonably say is that they might be.
You're taking an even more extreme position that given the opportunity to do a nefarious thing, Google must be doing it. Despite other reasonable explanations existing. This is a weird position to take and I don't get it.
Accusing people of being shills is a violation of the HN guidelines, please don't.
> You do know the history of the name doubleclick, right?
I honestly have no clue what you're implying here.
> Now want to explain why a browser experiment or analytics domain whitelist includes an advertising surveillance domain?
So that it can pass analytics information to requests including to the advertising domain. Occam's razor and all.
It is possible to ask someone to, or disclose for someone, a conflict of interest, without breaking the HN guidelines. The comment did neither.
We're here for curious conversation. Please don't harangue.
FWIW, I don't think I did, at least not intentionally. I certainly disclosed mine, but it's not clear that that's intentionally inviting more questions.
That said, to your first question, no I don't work on chrome, or ads or anything related, and I don't proclaim to have any particular insider knowledge thereof (if anything, the opposite).
To your second question, while I'd prefer to be able to answer you, responding to that kind of question is the kind of thing that I believe could put me in hot water, whether my answer was a "yes" or "no". Ultimately while I think the risk of answering is small, so is the perceived value (I don't think a "yes" would change your opinion, and a "no" would just embolden you), and it's mostly moot anyway since, again, I'm not working off of any particular knowledge beyond Google's already public statements.
I'll add that I originally had a bit more in this response, but I removed it because I don't think it would be used as anything but an additional way to attack me and my character, which is unfortunate.
I never attacked your character, and I don't think you're a shill at all -- nor would I ever use any of your posts against you except in the spirit of genuine debate. Not everyone is a vengeful ideologue. Work anywhere you want.
For example, the extraordinarily popular extension Honey phones home about your purchases, shopping habits and other data without adequately disclosing that fact.
It's hard to see why Google would care when Chrome was always a trojan horse to co-opt web standards for their own purposes and to prevent measures taken against invasive tracking and data collection in the first place.
Tracking is built directly into Chrome's source. Chrome will send "X-Client-Data" headers with a low-entropy identifier on every request to DoubleClick, an advertising agency owned by Google. DoubleClick's hostname is explicitly whitelisted in Chrome source code.
Chrome was always meant for massive spying, and any "crackdowns" are only a reaction to media pressure.