Re:EFF, AdBlock and Others Launch New “Do Not Track” Standard
by Programmatic on Monday August 03, 2015 @08:44PM
(#10000940)
I use RequestPolicy which is a plugin that allows you to control which third-party scripts are allowed to be loaded per domain. It is very lightly curated; they have a small set of default rules that allow sites to load "third party" sites that they control (e.g. their own CDN).
I have found that most sites work (including the one hosting the article being discussed) well enough to read, or even completely true to the author's intent (depends on if CSS is self-hosted or on a CDN that I haven't whitelisted). I even find that often it is actually more pleasant to have a basic experience when CSS doesn't load.
Sites that require me to allow a lot of third-party scripts and content to work force me to weigh the expected usefulness of the content vs the scumminess of the site. The creepier and more plentiful the third parties are, the more likely I am to press the X...
I very rarely have to allow Google and JQuery in my day to day browsing.
And that's why they work. You allowed things like Google's and Jquery's CDN. If they blocked third-party absolutely then tons of sites would break.
You cannot use a bunch of addons which whitelist/blacklist content and assume that is remotely ballpark the same as outright blocking third party scripts. Those lists are heavily curated to make sure that stuff doesn't break.