[pogue]

How are they going to be adding uBlock Origin to Chromium going forward if manifest v2 gets completely deprecated/removed entirely?

[gruez]

AFAIK some of the other chromium forks (brave and/or edge?) were committed to backporting manifest v2 (or more specifically the webRequestBlocking API) for future chromium versions.

[bjord]

this is not correct. neither brave nor edge has committed to that.

as of yet, there's no (publicly stated) contingency plan if the upstream mv2 code is excised, but I could be mistaken.

[rpdillon]

Brave has integrated uBO directly into their core logic. Visit brave://settings/extensions/v2 and you can download it, even with no MV2 support. I'm not aware of any other browser adopting this approach.

[bjord]

firefox 149+ actually bundles brave's adblock-rust as well, it just doesn't really use it. waterfox does enable it and use it, though they're still testing (https://github.com/BrowserWorks/waterfox/issues/4182).

all of that being said, I was answering the question about mv2 broadly, not ad blocking.

[eipi10_hn]

They said until they can't afford to maintain it.

[rpdillon]

The exact misimpression I was trying to counter.

[feverzsj]

Nothing. It will be a huge burden for them to maintain all the removed code. Their only choice is to integrate brave's adblocker.

[pogue]

This seems to be the only way forward from what I can figure. Helium's main selling point is that it's essentially degoogled chromium + a few miscellaneous patches & full uBlock. But once Google completely strips all that out of Chromium project, that won't be a tenable option.

I'm not sure what Opera/Vivaldi/et al. use for their native adblocking, but Brave's rust adblocker makes the most sense to me. Really it's uBlock's filtering lists that keep the whole thing working anyway.