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

▲

gruez 2 hours ago | parent | next [-]

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 2 hours ago \| parent [-]
		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.

▲

feverzsj 2 hours ago | parent | prev [-]

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 2 hours ago \| parent [-]
		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.