Well, OperaGX adblocker is terrible, it has the basic Network filtering and you can’t really add cosmetics in the rules, same with Vivaldi, the most advanced features is the half-done
$rewrite support, but you can’t really do much with it.
Brave currently supports most uBlock features, still missing some but most can be workarounded with other features, it’s just compatibility with uBlock lists the reason why some rules don’t work 100% fine.
And yeah, I use tons of software not available for Linux, and I think the Windows experience is better overall, if we talk about Brave, seems like most bugs happen in Linux, but also, there seems to be this thinking of Linux users of Brave team magically fixing bugs, I have reported so many bugs because I use Nightly, but then I see some people complaining because a stable release contains a bug, and then I am like “why weren’t you using Nightly and reported it?” So, probably that’s the reason for the bugs, no testers.
Nightly to me it is pretty stable, Brave Nightly uses Beta Chromium release, not Canary, so the experience is mostly okay.
Anyway! the point is don’t get surprised if you find more bugs in Linux than Windows or MacOS (Most Brave devs seem to use Apple). I think it is a mistake to not use Windows, especially when you can get Windows for free and you can get WSL installed on it. When I say free, I am talking about legally free, using Microsoft known methods to activate Windows in new or old hardware and all that. But People like different things.
Talking about your lists, you can pretty much get rid of most of them.
I don’t think Adguard lists are necessary when you use uBlock lists, but even uBlock added Adguard as an option for it, also, uBlock has compatibility/alias to support Adguard features that don’t have the same syntax, so they might work in uBlock but not in Brave which barely has any aliases, the only Alias I think they got is for the
:has() and only
:-abp-has() is supported because Easylist tends to use from time to time.
Some lists can be avoided to, like the Adblock detection ones, either, Brave will already support that through uBlock, if not, for the lack of feature or something, you can just make a post reporting it here with the adblocking category, with your site and all that, and it will be fixed by FanboyNZ.
FanboyNZ is Ryanbr from Easylist and Fanboy lists, he works for Brave and will either modify Easylist/Fanboy lists or fix it with Brave own lists or talk to uBlock people, since I guess he has influence if it is a uBlock issue.
Saying all that, in my opinion I would remove most of those lists:
nocoin, because uBlock uses the
resource-abuse for it.
Adguard lists, because like I said, uBlock are great lists with tons of people behind them, and many of the rules might not even be compatible with Brave.
Anti-adblock ones because uBlock lists should take care of those as well, and if not, let FanboyNZ do the job.
Easylist and Fanboy because they are included in Brave, either by default or as Regional and even in the settings like Cookie one.
pgl yoyo Serverlist is also included in Brave.
The only ones that might be useful are the DandelionSprout ones.
But some like Hangouts one are so insignificant that it would be more work to update them than copy and paste them to the Custom Filter box, they don’t get updated often to worry about it though. So it is preference, if you want these rules, at least they aren’t something Brave already has out of the box.
But I can see some rules don’t work, I opened the Anti Google hangouts one and:
play.google.com#?#c-wiz > div > div > div:has(> c-wiz[jsshadow] > div):has-text(/^Hangouts/)
doesn’t work in Brave, since
:has-text is a Procedural Cosmetic.
and since the
:has-text() is inside the
:has(), then uBlock would use the rule with the Procedural Cosmetic :has(), and not the Chromium native one, which is the one Brave currently supports.
So be aware some rules will not work.
That’s why I usually create my rules so if I need a rule I create it and I never have problems with compatibility issues.
I usually make my own anti-adblock rules because it is usually the easier ones to deal with, either it is a cosmetic rule that needs to be removed or a script being blocked that needs a
For the cosmetic one… you can’t do much about them, unless you remove default lists and use them as custom lists, which would work great now that the lists respect
Brave can’t create exceptions for scriptlets or cosmetics.
But you can use
:style(display: block !important) to work around the cosmetics one, but it would only affect custom lists, not hard to remove default lists, just remove the folder that contains the txt with the list and deny write permissions to the folder and done.
Brave adblocker is so easily to ‘hack’ unlike an extension like uBlock or something, so I add features Brave still don’t support like disabling some lists or custom scriptlets and all that.
But as I can see, I only would use Dandelion ones and don’t use the others, unless you really know about some rule that doesn’t work and it is in Adguard or something, but then, you can just report it and it will probably get fixed by Easylist/Fanboy or uBlock.