2 ms·
I don't like the no JS approach, it kills an important part of the potential in the web, including polyfills for things like srcset. Instead, I'm using Policem
by pmlnr 11y ago
I don't like the no JS approach, it kills an important part of the potential in the web, including polyfills for things like srcset.
Instead, I'm using Policeman ( https://addons.mozilla.org/en-US/firefox/addon/policeman/; https://addons.mozilla.org/en-US/firefox/addon/policeman/; similar to uMatrix https://github.com/gorhill/uMatrix/releases https://github.com/gorhill/uMatrix/releases, but the first is easier to use for me ) which blocks 3rd party anything by default.
If they serve their own JS from their own servers, let it be. Others (Facebook connect, GAnalytics an Twitter seems to be _everywhere_): walk away.
This obviously renders most of the sites to bare HTML due to the excessive and unneeded use of CDNs, and is a massive pain to use for the first weeks, but after a while the whitelist gets you to a friendly web level.
uBlock also runs in the background, just in case things leak through, or I quickly want to check something and I need to turn Policeman off.
- 0xffff2 11y agoFYI, the first link is broken because the semicolon was included as part of the hyperlink. Should have been https://addons.mozilla.org/en-US/firefox/addon/policeman/ https://addons.mozilla.org/en-US/firefox/addon/policeman/
- nkrisc 11y agoIf you use a modern browser you probably don't need the polyfills anyway, so why are you concerned about blocking them? While not necessarily related to privacy, I've found sites where blocking self-served JS creates a better browsing experience because it gets rid of annoying effects and things like scrolljacking.