However, Google still get referrers every time you visit a site using googleapis provided jquery and that is a lot of sites these days.
If they're not tracking through googleapis (I can't find any such statement) then they shouldn't mind if we strip the referrer and just appear to be making a direct request to http://ajax.googleapis.com/ajax...
You've got to ask the question, why do you think Google provide these scripts hosted on a high quality CDN for free?
I find it incredible the amount of detail put into Ghostery. However I see such a big tracking operation being allowed to continue without our ability to even strip the referrer sent to Google. Ideally there would be a simple way to serve these standard jquery files up locally and not connect to Google at all.
Please see https://developers.google.com/speed/l... for information about what googleapis.com is used for. Webmasters choose to use Google hosted libraries because it makes their pages load faster, and offloads traffic from their networks. Since googleapis.com is a cookieless domain, frequently-used libraries (such as jQuery) can be cached locally. Note that Google sets a one-year expiration and specifies Cache-Control: public with a max-age of 365 days. Yes, they'll collect some referrers, but they've done everything they can to not have this "phone home" every time.
Google is a publicly-traded corporation, and has agreed to oversight of their privacy practices by the U.S. Federal Trade Commission for the next 20 years. At this point, they are probably among the most trustworthy companies out there.
It is true that webmasters choose to use googleapis to reduce their bandwidth and supposedly improve load times for users (although that claim is dubious as it'll only improve the very first load of a site).
I could go into further detail but it's not relevant to the problem and the sites you link to do nothing to reassure, where's the guarantee of privacy you're getting from them?
The Chromium team implementing a webkit wide fix that will only be utilised by a small number of sites doesn't change my opinion much either. Another red herring is cookies, they are not the risk, take a look at your unique browser fingerprint http://ip-check.info/
Every time, yes, every time you load a non-Google page which references googleapis as the place to grab jquery; it'll let them know your IP, the exact URL you're on and your browser fingerprint; couple that with their multitude of other services you may be using and this can easily add up to who you are, where you are, what you're doing and when. If referrers are disabled or jquery was referenced from a different location then Google lose one hook they have to track user behaviour, it simply doesn't need to happen.
I'm not looking for Ghostery to block googleapis.com, that'd break functionality across the web and they're hosting standard files which literally could be anywhere but if they're not interested in tracking through providing this service (although I can't see another reason they'd give away use of a really expensive CDN)... then they'd not be bothered by a handful of privacy concious users not giving them a bunch of tracking data.
Google give away excellent services for "free", these all come with the caveat that they'll track what you do and use this data to sell targeted advertising (at least for now).
Normally if one doesn't like a company they can simply not use their products but this isn't currently possible with Google; they're burrowing their way into so many places you really struggle to avoid them, even if you never load a Google page they're building a profile on you and I wish I could escape...
Given the scale and efficiency with which Ghostery is stopping other tracking devices, it seems absurd that you wouldn't want it to stop the biggest collector of personal data that exists.
Responsiveness has a huge psychological effect. IBM did studies where they found people's minds start to wander in as little as a quarter second. Since a webmaster doesn't know whether page elements will be cached, it's reasonable to hope for best, but plan for the worst. The claim isn't dubious; everything from DNS lookup to actual delivery is likely to be much faster when using a CDN. Taking jQuery as an example, there are several choices:
You want a guarantee? The guarantee is that Google has been caught with their fingers in the cookie jar more than once; consequently, they're now being subjected to closer scrutiny than anyone else.
The Chromium example merely points out that Google has been doing more than anyone else to do something to address your issue. Still, responsibility rests with the webmasters.
You could run a local proxy that intercepts googleapis.com requests and offers substitute content. This is easy for http, a little trickier for https.
Google operates the CDN because they need it for their own purposes. The marginal cost of hosting third-party libraries is small relative to the goodwill it generates. They can consider it a promotional expense.
I get that you're a Google hater and a conspiracy theorist. But they're hardly the biggest collector of personal data that exists. That honor probably belongs to Facebook at this point. However, I can assure you that if you're in the U.S., and you get your Internet access via AT&T or Comcast, you've already lost (unless you're running all your traffic through a secure tunnel).
I don't see a massive difference between what I did and linking to the same text but if it bothers you then I'll just link (rather than trying to hold this discussion on a closed topic).
If they're not tracking through googleapis (I can't find any such statement) then they shouldn't mind if we strip the referrer and just appear to be making a direct request to http://ajax.googleapis.com/ajax...
You've got to ask the question, why do you think Google provide these scripts hosted on a high quality CDN for free?
I find it incredible the amount of detail put into Ghostery. However I see such a big tracking operation being allowed to continue without our ability to even strip the referrer sent to Google. Ideally there would be a simple way to serve these standard jquery files up locally and not connect to Google at all.
Google is a publicly-traded corporation, and has agreed to oversight of their privacy practices by the U.S. Federal Trade Commission for the next 20 years. At this point, they are probably among the most trustworthy companies out there.
I should add that Google Chrome 17 implemented a proposal to allow pages to disable sending referrer information. http://code.google.com/p/chromium/iss...
Firefox considered it: https://bugzilla.mozilla.org/show_bug...
I could go into further detail but it's not relevant to the problem and the sites you link to do nothing to reassure, where's the guarantee of privacy you're getting from them?
The Chromium team implementing a webkit wide fix that will only be utilised by a small number of sites doesn't change my opinion much either. Another red herring is cookies, they are not the risk, take a look at your unique browser fingerprint http://ip-check.info/
Every time, yes, every time you load a non-Google page which references googleapis as the place to grab jquery; it'll let them know your IP, the exact URL you're on and your browser fingerprint; couple that with their multitude of other services you may be using and this can easily add up to who you are, where you are, what you're doing and when. If referrers are disabled or jquery was referenced from a different location then Google lose one hook they have to track user behaviour, it simply doesn't need to happen.
I'm not looking for Ghostery to block googleapis.com, that'd break functionality across the web and they're hosting standard files which literally could be anywhere but if they're not interested in tracking through providing this service (although I can't see another reason they'd give away use of a really expensive CDN)... then they'd not be bothered by a handful of privacy concious users not giving them a bunch of tracking data.
Google give away excellent services for "free", these all come with the caveat that they'll track what you do and use this data to sell targeted advertising (at least for now).
Normally if one doesn't like a company they can simply not use their products but this isn't currently possible with Google; they're burrowing their way into so many places you really struggle to avoid them, even if you never load a Google page they're building a profile on you and I wish I could escape...
Given the scale and efficiency with which Ghostery is stopping other tracking devices, it seems absurd that you wouldn't want it to stop the biggest collector of personal data that exists.
You want a guarantee? The guarantee is that Google has been caught with their fingers in the cookie jar more than once; consequently, they're now being subjected to closer scrutiny than anyone else.
The Chromium example merely points out that Google has been doing more than anyone else to do something to address your issue. Still, responsibility rests with the webmasters.
A better example of browser fingerprinting is https://panopticlick.eff.org/
What you're looking for is something like a URN.
You could run a local proxy that intercepts googleapis.com requests and offers substitute content. This is easy for http, a little trickier for https.
Google operates the CDN because they need it for their own purposes. The marginal cost of hosting third-party libraries is small relative to the goodwill it generates. They can consider it a promotional expense.
I get that you're a Google hater and a conspiracy theorist. But they're hardly the biggest collector of personal data that exists. That honor probably belongs to Facebook at this point. However, I can assure you that if you're in the U.S., and you get your Internet access via AT&T or Comcast, you've already lost (unless you're running all your traffic through a secure tunnel).
https://getsatisfaction.com/ghostery/...