[zephyreon]

Could definitely be writing on the wall that MV2 support will be deprecated in the future but imo not necessarily a bad thing if it’s not actively developed anyways. Maintaining both MV2 & MV3 support isn’t easily sustainable long term when you factor in the need to prioritize other features.

That said, if this is writing on the wall I’d hope they’ll listen to the community this time and allow the engine to be extended / make it such that a block all ads feature always exists. I’m cautiously optimistic given Mozilla’s track record just over the past year-ish. They have released some great new features that help bring Firefox closer to feature parity with other browsers.

I am a Firefox hopeful and recently switched back to using it as my daily driver when Arc went belly up (but mainly for uBlock Origin support).

[charleslmunger]

>Maintaining both MV2 & MV3 support isn’t easily sustainable long term when you factor in the need to prioritize other features.

There is no feature Firefox provides that is more differentiating than ublock origin. As long as pages load and security issues are patched it is the reason to choose Firefox as a browser. What would they prioritize over it?

[lxgr]

And there's nothing in MV2 that uBlock Origin needs that doesn't exist in MV3 on Firefox, unlike Chrome. This issue is completely overblown.

[curt15]

Are you disputing uBlock Origin's list of MV3-incompatible capabilities [1]?

[1] https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...

[andrewaylett]

That list contains issues with the APIs that Chrome exposes via MV3. Firefox still supports APIs that Chrome removed.

[lxgr]

Not really, but this FAQ, like almost all articles published on MV3, conflates MV3 the specification with Chrome's MV3 implementation. (FWIW, I'm almost certain that this is either due to sloppy/imprecise writing or intentional, with the authors not wanting to confuse users already appropriately riled up by equally imprecise reporting on MV3. They definitely know the difference.)

In any case, for better or worse, when people say MV3, they now usually mean "Chrome's MV3 implementation", which obviously never applies to Firefox.

[ragall]

That's utter bullshit. The author of uBlock Origin has posted a long list of capabilities that declarativeNetRequest does not support.

[tyushk]

Unlike Chrome, Firefox did not remove the older API.

[ragall]

What's this supposed to mean ? OP was saying that MV3 is feature-equivalent to MV2 and would like to see MV2 support removed from Firefox just as it was from Chrome. I replied pointing out that's utterly false.

[lxgr]

MV2 and MV3 are feature equivalent on Firefox when it comes to request blocking.

[zephyreon]

I’d like to see more investment in their new profile manager. It feels pretty barebones at the moment. Arc had the ability to link profiles to “spaces” and you could easily switch between them without opening a new window. It was very nice to so easily swap between personal, work, & side business.

[collabs]

The multi user containers are also very nice.

[gawa]

And to go one step further, for achieving a profile-per-firefox-window workflow, I suggest to have a look at the underrated extension Sticky Window Containers [0]

While far from being perfect, I find it good enough for keeping things separated, especially when using a desktop/workspace workflow. For example, in workspace/desktop 2 I have a Firefox window opened with the first tab set to "container A", so hitting ctrl-t there opens new tabs with the same container "A", so I'm logged-in for all projects A. In another Firefox window in workspace 3 I work with "business project B" tabs (where I'm logged into different atlassian, github, cloud, gmail, ...)

Then with a Window Manager like i3wm or Sway I set keybinds to jump directly to the window (and workspace), using the mark feature [1]

It's also possible to open websites directly in specific containers so it's flexible. For example on my desktop 8 I have all my AI webchats in "wherever my company pay for it" tabs: `firefox --new-window 'ext+container:name=loggedInPersonnal&url=https://chat.mistral.ai' 'ext+container:name=loggedInBusinessA&url=https://chatgpt.com' 'ext+container:name=loggedInBusinessB&url=https://gemini.google.com' 'ext+container:name=loggedInBusinessB&url=https://claude.ai'`

It's also the only way I found to keep opened multiple chat apps (Teams, Slack, Discord, ...). The alternative electron apps are as resource-hungry, and in my experience never handled multiple accounts well (especially Teams).

[O] https://addons.mozilla.org/en-US/firefox/addon/sticky-window...

[1] https://i3wm.org/docs/userguide.html#vim_like_marks

[tosti]

Why does everything have to be "actively developed"? Sometimes a program is just done. Better not touch it. I actually do downgrade packages when "actively developing" causes regressions. Not curl or anything sensitive like that, but local programs definately yes.

In case of the extension manifest, that's probably layered on top of the JS engine which does get attention and scrutiny. It's not like an API needs to be updated. If you'd always do that, nothing would ever be interoperable and we'd likely have a hard time trying to communicate.

[Dylan16807]

> Maintaining both MV2 & MV3 support isn’t easily sustainable long term when you factor in the need to prioritize other features.

The feature that better adblockers need is one callback that's similar to one that's still in V3. It's not difficult to keep if it's your own codebase.

[striking]

Try Zen! Firefox fork with Arc-like UX.

[pjjpo]

Zen is great and still mostly Firefox. I use standard Firefox on Android and everything syncs without hassle. The experience is so much better that personally cannot imagine using Chromium anymore. Of course I do wonder if the entire Firefox ecosystem is sustainable long-term funding wise.