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

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

25 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

[-] jet@hackertalks.com -5 points 2 months ago

Because of incentives it's not impossible for the Mozilla foundation to drop support for manifest V2 eventually. If Google's paying 90% of their bills, it's not unreasonable to assume they also have a say in the direction of the browser

[-] Chewy7324@discuss.tchncs.de 14 points 2 months ago

I've never seen any reason to believe Google has any say in the direction of Firefox. Google pays to be the default search engine, not more, not less.

This same argument could be brought up about Safari. All other browsers are based on Chromium anyway, so they are directly developed by Google themselves.

this post was submitted on 16 Aug 2024

73 points (95.1% liked)

Open Source

31181 readers

233 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Posts must be relevant to the open source ideology
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago

MODERATORS

Cloak@lemmy.ml

kevincox@lemmy.ml

CrypticCoffee@lemmy.ml

Lettuceeatlettuce@lemmy.ml