3 ms·
I use RequestPolicy. It gives fairly fine-grained control over which third party sites are loaded, and from which origin. It's the best of both worlds for me.
by GrinningFool 11y ago
I use RequestPolicy. It gives fairly fine-grained control over which third party sites are loaded, and from which origin.
It's the best of both worlds for me. I'll see the ads I don't object to (those not served from an ad network), greatly reduced cross-site tracking, and the risk of exposure to malicious ad content is much reduced.
Occasionally you run into a poorly coded site that fails to render because facebook or twitter didn't return what it expected, but for the most part it's a good compromise between extremes of wide open and noscript.
- distances 11y agoI used to use RequestPolicy too. Then I found uMatrix, which simply has a much better representation for this, and allows finer control (cookie/image/css/plugin/script/XHR/frame). I suggest you to try it out. As for the setup, I made it accept all first-party content, and images+css from third parties, and block everything else by default. Then you play the "guess the source" game for a couple of scripts that you as RequestPolicy user are already familiar with :)
- GrinningFool 11y agoThanks, I'll take a look