[rmrfrmrf]

I want to know what privacy concerns you have regarding static CDNs that you don't implicitly give up by accessing the Internet.

[nly]

Tracking via 3rd party cookies and E-Tags, plus HTTP Referers as codeonfire said. There's also just the obvious risk of compromise, resulting in millions of sites running malicious code.

[dictum]

Not sending Referer headers to Google.

(Yes, it becomes a problem when you use private browsing, since the cache is cleared when you end the session.)

[codeonfire]

This is what it's all about. These cdn sites exist not out of good will, but because they give tracking information.

[rmrfrmrf]

You have to do that at the end-user level if your goal is truly shielding yourself from Google. Wagging your finger at a few of the devs on a news website isn't going to change the millions of websites using client AND server-side Google Analytics, not to mention ads.

[dictum]

I do. Your comment,

> I want to know what privacy concerns you have regarding static CDNs that you don't implicitly give up by accessing the Internet.

implies that the privacy concerns for 3rd party JS library CDNs are null. They are only null if you don't already block or misdirect their other tracking methods.