How difficult would it be to fork and mantain a chromium version that still supports Manifest V2? (sh.itjust.works)

submitted 4 months ago* (last edited 4 months ago) by tomatoely@sh.itjust.works to c/opensource@lemmy.ml

23 comments fedilink hide all child comments

As Google tries to hinder ad-block extensions with their new platform Manifest V3, it seems to me Chrome or any Chromium derivatives are no longer a viable way to browse the web safely. So it got me wondering, how much big of a task would it be to still suport Manifest V2 on newer releases of Chromium? Maybe implement some legacy option for backwards compatibility with older extensions. I think it would be a great alternative to have, but I haven't seen anyone coming up with something similar.

you are viewing a single comment's thread
view the rest of the comments

[-] Shamot@jlai.lu 34 points 4 months ago

I think that using gecko based browsers like Firefox is the best thing to do in the short term. But having no competition is a bad thing. So supporting new web engines, like Ladybird, is important too: https://github.com/LadybirdBrowser/ladybird