uBO can also do things that uMatrix can't (on Firefox at least) - like CNAME uncloaking[1]. This is where a resource is hosted/maintained on third-party servers

uBO can also do things that uMatrix can't (on Firefox at least) - like CNAME uncloaking[1]. This is where a resource is hosted/maintained on third-party servers, but is addressed using a first-party subdomain. As a completely hypothetical example, instead of loading content from homedepot.disqus.com, you load it from disqus.homedepot.com. The relationship between Home Depot and Disqus and the privacy implications are similar in both cases, but uMatrix would consider the former to be third-party content and the later to be first-party. uBO however will treat both as third-party content (when CNAME uncloaking is enabled). Enabling this in uBO really opened my eyes to how fuzzy the distinction between first-party and third-party is. Sites can have all types of business arrangements with different privacy implications, ranging from relatively harmless (hosting), to moderate (CDN), to invasive (ad tracking). uMatrix and other blockers have used the domain name as a proxy-variable to measure whether something should be trusted or not, but it is increasing becoming a poor metric. With CNAME uncloaking enabled, maintaining default deny, and allow only what is needed approach becomes quite a bit more work, as it ends up blocking a bunch of necessary content. But without you are allowing a fair bit of tracking you shouldn't. After a few months of trying to use uBO like uMatrix, I found that using the curated deny-lists was a more tractable approach than maintaining my own allow-list, and thus don't miss the uMatrix interface as much as I expected. [1] https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#uncloak-canonical-names https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#u...