News for hackers. Stuff that matters.
Re:Mozilla blog: Begin your MV3 migration by implementing ne... by gingerlime on Tuesday November 01, 2022 @03:16AM (#33418013)
I’m no expert, but I think the main moat that Chrome has here is its web store where users find extensions and developers submit their extensions. There’s a review process which whilst far from perfect is labor intensive and still helps catch rogue extensions. Hard to open-source this part of Chrome.
Re:Mozilla blog: Begin your MV3 migration by implementing ne... by cglong on Tuesday November 01, 2022 @03:22AM (#33418042)
There's an OSS fork of Chromium for Android called Kiwi that enables installing extensions from the Chrome Web Store.
Re:Mozilla blog: Begin your MV3 migration by implementing ne... by ToruiDev on Tuesday November 01, 2022 @03:46AM (#33418170)
Which still relies on the Chrome Web store.

Which will stop accepting MV2 Extensions after the move to MV3

Therefore leaving you without a store again

Re:Mozilla blog: Begin your MV3 migration by implementing ne... by marwis on Tuesday November 01, 2022 @04:08AM (#33418300)
You also can't use Google services with unofficial build. That includes Sync, Translate and bunch of other stuff.
Re:Mozilla blog: Begin your MV3 migration by implementing ne... by zarzavat on Tuesday November 01, 2022 @04:55AM (#33418601)
That’s a feature for me. I don’t want to have to sign into my browser or have it phoning home constantly. It’s a privacy risk.