Technology

37712 readers

326 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

204

Google Chrome’s plan to limit ad blocking extensions kicks off next week (arstechnica.com)

submitted 5 months ago by [email protected] to c/[email protected]

45 comments fedilink hide all child comments

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

[–] [email protected] 71 points 5 months ago (1 children)

::Laughs in Firefox::

[–] [email protected] 10 points 5 months ago (5 children)

Who knows... Firefox might just follow suit. If devs have to write their extensions one for Chrome and once for Firefox, the Firefox one will probably be the first to die.

Anti Commercial-AI license

[–] [email protected] 48 points 5 months ago

That's not how it works. Firefox has full support for Manifest v3 extensions, but it does also support MV2 at the same time, and aims to keep MV2 support alive in the future.

[–] [email protected] 3 points 5 months ago (1 children)

Isn't that already how it works? Are there extensions trust work unchanged on both browsers? At the very least they'd have to maintain them on both addon stores.

[–] [email protected] 8 points 5 months ago

There's a common specification called WebExtension, which is used by all modern browsers. Firefox had their own API (XUL/XPCOM) before that, but they deprecated it in 2017. Safari also used to have its own system for extensions, but it's been deprecated since 2019. The Manifest API is a subset of WebExtension, which defines an extension.

[–] [email protected] 18 points 5 months ago (1 children)

Not if more people use FireFox...

Firefox also supports mobile extensions, unlike Chrome.

[–] [email protected] 6 points 5 months ago

Unfortunately, as much as I like and use firefox on both pc and mobile, chrome and chromium based browsers dominate the market. It doesn't help that they come pre-installed in both cases.

[–] [email protected] 31 points 5 months ago* (last edited 5 months ago)

From the article:

Firefox plans to support Manifest V3 because Chrome is the world's most popular browser, and it wants extensions to be cross-browser compatible, but it has no plans to turn off support for Manifest V2.

I doubt they'll ever choose to shut down V2, but Google is already forcing their hand a little by making them require supporting V3 to stay relevant

[–] [email protected] 13 points 5 months ago

Then there will be thousands, millions of people continuing development of FF extensions.