3 ms·
Here's a few: - performance gains from optimized machine code - CNAME adblocking, which is otherwise not possible on Chromium-based browsers - robustness aga
by antonok 5y ago
Here's a few:
- performance gains from optimized machine code
- CNAME adblocking, which is otherwise not possible on Chromium-based browsers
- robustness against potential changes from upstream (i.e. Manifest v3)
And, not exactly adblocking, but other privacy protections that are only possible with a deep level of control over browser APIs:
- advanced fingerprinting protections, including subtle randomized perturbations of canvas reads, fonts, user agent, etc.
- ephemeral storage sandboxing for third-party content
- throw16489 5y agoUblock Origin on Firefox has CNAME blocking. Also Firefox is not affected by manifest v3
- aaravchen 5y agoIronically, CNAME blocking is actually a (potential) privacy leak depending on your network configuration. It does a DNS look up (ignoring your system DNS settings) and checks what the CNAME record is pointing to against the block list. Assuming you have control of your DNS settings, you've (hopefully) configured your DNS to use Quad9 or something similar rather than Cloudflare (questionable) or Google (outright invasive). UBO ignores this choice. UBO also recently added a warning about this in their extended info on the option, and it's been featured on HN a few times.