ES version is available. Content is displayed in original English for accuracy.
Firefox 149 ships adblock-rust (Brave's Rust engine, MPL-2.0) completely disabled with no UI. It's controlled by two about:config prefs with no WebExtension API, so you can't touch them programmatically from a standard extension.
This extension gives it a UI: ETP toggle (via browser.privacy API, instant), filter list manager with clipboard helpers for the manual about:config steps, and 8 preset lists. You can also add your own if you so desire.

Discussion (33 Comments)Read Original on HackerNews
What concrete and practical differences are there between the two? I'm guessing because this exists, adblock-rust somehow is better than the built-in ETP? In what way?
I'm using ETP + uBlock Origin right now, and can't remember the last time I saw an ad, if I used this instead, what practical differences would I notice?
Note that there are (were?) also some small bugs in the waterfox integration (such as the configuration options sometimes disappearing).
(AdGuard does have an option to supplant uBlock in this stack btw, does “advanced” blocking https://adguard.com/kb/adguard-for-ios/web-extension/ which is nice but trust $mm-refusing uBlock dev gorhill forever)
¹ In this case, the developer – not the musician. I really liked the user interface of uMatrix.
I also test on FF and I don't care much for chromium. I was just curious why the author chose to do this.
More ideologically, Google and Chromium are awful for the internet as monopolistic tech.
The people who developed brave used brave to impersonate people and defraud their users out of money by asking for donations using other peoples names [1]. I don't trust them at all. Thus I don't use their browser.
And, unsurprisingly, this is part of a pattern of bad behavior, not a one off criminal act by otherwise trustworthy people, for some examples [2].
[1] https://web.archive.org/web/20181221180137/https://twitter.c... / https://news.ycombinator.com/item?id=18734999
[2] https://github.com/lobsters/lobsters-ansible/issues/45#issue... and https://lobste.rs/s/iopw1d/what_s_up_with_lobste_rs_blocking...
"https://easylist.to/easylist/easyprivacy.txt",
"https://secure.fanboy.co.nz/fanboy-cookiemonster.txt",
"https://raw.githubusercontent.com/uBlockOrigin/uAssets/refs/..."
These are the lists you say you do not want being used.
Please explain how these lists and the people who maintain them are compromised by someone with an obligation or association with the ad/tracking industry. This would be revelatory.