I use both to good effect. Similar goal, but not the same in practice.
UBO is a request-level filtering system. It blocks certain requests based on a set of patterns. It's incredibly simple, incredibly fast, and surprisingly effective, since most adds and trackers are served by 3rd party sources that can be recognized. This doesn't catch everything, though, and trackers can be sent alongside the core website content. PB provides content-level filtering that can catch some things that slip by UBO.
PB does things uBO doesn't bother with, but not because uBO only has request level filtering. E.g. uBO also employs content level filtering and methods such as scriptlet injection to neuter/stub specific tracker functionality.
Wonder when all analytics and ads will be first party (presumably years away since it’d ostensibly be so tough for the average small site). Enjoying it while it lasts I suppose.
Each offer something slightly different in various contexts. uBlock covers most use-cases, but not every site is completely clean.
In general, setting up NoScript per-site filters (like blocking XSS, webgl or LAN resources) is more practical in some ways, and offers deeper control of resources needed for core page functionality.
Often, websites only really require their host, a JavaScript CDN, and some media CDN/cloud URI. Modern sites often insert telemetry or malware/ad services, and will load much faster without that nonsense. =3
uBlock Origin is an excellent privacy tool. However, uBlock Origin is not a replacement for Privacy Badger (nor is Privacy Badger a replacement for uBlock Origin).
Thanks for linking this page. I am using multiple of these addons, but some years passed since I figured this setup, so it was time for reconsider the choices.
https://github.com/arkenfox/user.js/wiki/4.1-Extensions#-don...