This is the sort of thing that the W3C committee and open-source web-companies should be researching/solving instead of "HTTPS" and "SSL pinning", "new HTML5 ta

This is the sort of thing that the W3C committee and open-source web-companies should be researching/solving instead of "HTTPS" and "SSL pinning", "new HTML5 tags", "web notification", "location apis", and "DNS over HTTPS" type of stuff (although they are important on some level). We shouldn't have to rely on JS in order to do these sorts of website analytics. It could arguably be part of the browser stack and within the users' realm of control. Instead we now have disable GA or all JS in order to not be tracked. GA is a huge privacy issue, and I have no idea why no one is looking at this more closely than some of the other things I see as trivial. Google controls most of the web's search. It controls a huge chunk of the browser market. And a huge chunk of the websites out there use GA if not google-ads. Between Google and Facebook, we are constantly being tracked and monitored for maximum benefit/profit. Case in point: Even without GA, I recently browsed a blog that had a Disqus comments section embedded on it. The embedded Disqus script did a post to "https://accounts.google.com/o/oauth2/iframe" https://accounts.google.com/o/oauth2/iframe" that had a referral header telling google exactly the page I was at, and it included a few other potentially-tracking tokens. Bad? You decide. But this is not what we should be allowing the players on the web to do, and we shouldn't feel like conspiracy-theorists for being bothered by it.