3 ms·
> serving jquery for free in exchange for tracking your users persistently via Google Analytics jQuery on their CDN has nothing to do with Google Analytics, an
by magicalist 12y ago
> serving jquery for free in exchange for tracking your users persistently via Google Analytics
jQuery on their CDN has nothing to do with Google Analytics, and it's served without a cookie and with long cache expire times, so it's not a very good tracking target.
> building a browser to slowly but surely make it harder to opt out of Google's SSL-based tracking
I have no idea what you're referring to here, but it doesn't sound like it makes much sense.
- justcommenting 12y ago> jQuery on their CDN has nothing to do with Google Analytics most production servers i encounter that serve google's copies of jQuery also serve GA. i know this because i have to manually allow those requests using RequestPolicy. yes, they're technically different products. but that wasn't my point. > I have no idea what you're referring to here check out: https://sites.google.com/a/chromium.org/dev/Home/chromium-security/client-identification-mechanisms#TOC-Lower-level-protocol-identifiers https://sites.google.com/a/chromium.org/dev/Home/chromium-se...
- magicalist 12y ago> most production servers i encounter that serve google's copies of jQuery also serve GA. i know this because i have to manually allow those requests using RequestPolicy. yes, they're technically different products. but that wasn't my point. so...when you said "in exchange for" you meant that some sites also use Google Analytics? > check out: https://sites.google.com/a/chromium.org/dev/Home/chromium-security/client-identification-mechanisms#TOC-Lower-level-protocol-identifiers https://sites.google.com/a/chromium.org/dev/Home/chromium-se... That's not a page of "Google's SSL-based tracking" methods. That's an attempt to enumerate ways browsers leak information.