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.
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.
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.
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.
In the same sense that a blockchain can be forked by using software that only accepts certain types of block, is it possible to fork the WWW in a similar manner? e.g. with changes that neuter the ad-mongers.
For example coming up with a way to get rid of these god awful cookies. Maybe ad-monger sites could be allowed in the same way an insecure connection is allowed behind a series of warnings?
20 comments
[ 2.5 ms ] story [ 31.8 ms ] threadAn odd pairing
as of yet, there's no (publicly stated) contingency plan if the upstream mv2 code is excised, but I could be mistaken.
all of that being said, I was answering the question about mv2 broadly, not ad blocking.
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.
For example coming up with a way to get rid of these god awful cookies. Maybe ad-monger sites could be allowed in the same way an insecure connection is allowed behind a series of warnings?
[0]: https://github.com/imputnet/helium/issues/1532
[1]: https://github.com/imputnet/helium/issues/1850