adblock-resources VS brave-core

You can find them here https://github.com/brave/adblock-resources/blob/master/filter_lists/list_catalog.json

Brave utilizes a lot of sources that are uBlock. For what it´s worth. So either test/make sure that Brave Shields is set to Aggressive and/or add any additional sources you have in uBlock that are missing in Brave and check if that works better for you.

For most people, the built-in Brave ad blocker set to "Aggressive" should work perfectly fine, as it uses the same default filter lists as uBlock Origin. It also works on Android and won't be subjected to the restrictions for extensions when Google remove support for Manifest V2 – as it isn't an extension.

Brave is essentially Chrome underneath, but with the privacy invading crap removed. It's Rust-based built-in ad blocker works on Android, as well as desktop and uses the same default filter lists as uBlock Origin. It's also possible add additional filter lists from brave://adblock.

Actually Brave has more filter lists on top of uBO as you can see here so if you want those maybe you can add them to uBO as well, but I'm not sure if they're compatible. But uBO on hard mode is definitely stronger protection than Brave with these lists

The Brave Shields content blocker also works really well on Android and uses the same lists as uBlock Origin (see HERE). In the next release, they're adding more procedural cosmetic filtering improvements to their content blocker (see HERE), which will allow even more advanced content blocking. This is already working in Brave Nightly.

Okay then I can also understand that the default.json is built into the AdBlocker, so to speak, and the regional.json is what you can choose from the list in the browser?

Unrelated but about Brave and interesting to me: I recently found myself having a large upstream project that I need to maintain some custom patches for, and there's a need for deeper customizations and I worry that my rudimentary system of applying .patch files will turn into an unmaintainable nightmare of merge conflicts after every rebase. I was thinking about possible solutions, and it occurred to me that Brave being Chromium-based must have this same challenge but an order of magnitude more difficult, so I looked for their code to see how they solved this issue.

It's pretty interesting! They do basically the same thing for core Chromium, applying a (big) set of patches[1].

Incidentally, I'd be interested to hear any ideas/approaches to this problem. I'm guessing if there was something clearly better, Brave would be doing it, but it seems like there should be a better way even if I can't think of one.

[1] https://github.com/brave/brave-core/tree/master/patches

https://github.com/brave/brave-core/pull/13737

(Incidentally, that PR number is not quite elite. :)

I disagree that it's lip service Brave has a ton of engine level privacy patches https://github.com/brave/brave-core/tree/master/patches

To my understanding you can't match it with just js extensions.

Only firefox on the highest security mode comes close I think?

Or ungoogled chromium? (brave has most of their patches IIRC)

Are there other options that have this number of patches?

Chromium is not 100% Google's forever and always, though they do currently lead the way, and with the most used/backed fork.

https://github.com/brave/brave-core/pull/19476

They have much more changes than just compile flags. Here's the repo where they maintain their patch set: https://github.com/brave/brave-core/tree/master/patches

Brave Private Ads toggle controls just Push Notification ads at this time. So, if you are still seeing Push Notification ads, that would be incorrect. However, it's normal to still see New Tab Page image ads, and/or other ad formats. We are introducing a new UI that helps you better toggle on/off specific ad units, and removing the "Brave Private Ads" toggle that can be confusing: https://github.com/brave/brave-core/pull/18938

Yes, being fixed. Github at https://github.com/brave/brave-core/pull/18922