- cross-posted to:
- firefox
- cross-posted to:
- firefox
deleted by creator
Yeah, I don’t get why the rest of the comments here are shooting against both. Firefox is 100% doing the right thing here.
The reality is more nuanced than this. Wrote up my thoughts on my blog: A layered approach to content blocking.
Strictly speaking about content filtering:
declarativeNetRequest
is honestly a good thing for like 80% of websites. But there’s that 20% that’ll need privileged extensions. Content blocking should use a layered approach that lets users selectively enable a more privileged layer. Chromium will instead be axing the APIs required for that privileged layer; Firefox’s permission system is too coarse to support a layered approach.
Use Librewolf and Tor 😉
deleted by creator
@tristan fortunately I stopped using both
@Shishimaru, what do you use instead?
(The article notes that Firefox is going to continue to support a wide ranger of ad-blocking, while Chrome is not.)
He went back to Internet Explorer
I thought the answer was going to be Falkon, but it ended up being an ad response…
@tristan Brave
Sorry to hear that
deleted by creator
@BowerickWowbagger Brave
So basically, Chrome…