this post was submitted on 22 Aug 2024
175 points (82.5% liked)

Firefox

17937 readers
37 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] slazer2au@lemmy.world 174 points 3 months ago (4 children)

Mozilla is the maker of the famous Firefox browser which has been using its own web engine called “Gecko” since forever, and hence, is not affected at all by these moves from Google.

You answered your own question. It doesn't effect FF.

But, I do agree they should use the downgrade in functionality of V3 as a point for advertising FF.

[–] Quacksalber@sh.itjust.works 63 points 3 months ago (2 children)

What good would advertising "Still supporting Manifest V2" do for your average user? They also wouldn't want to openly advertise that "Your ad block still works with us".

[–] tb_@lemmy.world 17 points 3 months ago

Most sane take in this whole thread.

Some of y'all get a little conspiratorial.

[–] gedaliyah@lemmy.world 2 points 3 months ago

That is literally the premise of the article

[–] eruchitanda@lemmy.world 45 points 3 months ago (1 children)

Don't they get like 90% of their money from Google?

[–] slazer2au@lemmy.world 29 points 3 months ago (1 children)
[–] TriflingToad@lemmy.world 15 points 3 months ago (1 children)

that's also probably a factor in why they don't say anything, big moneypants might say something

[–] sugar_in_your_tea@sh.itjust.works 2 points 2 months ago (1 children)

No, big moneypants is getting sued for monopoly practices, which means Mozilla's search revenue may dry up. I'm guessing they don't want to ruin their chances with a competitor should they need to find another search partner.

[–] TriflingToad@lemmy.world 1 points 2 months ago

sure, that's also probably a factor in why they don't say anything, new big moneypants might say something

[–] RobotToaster@mander.xyz 9 points 3 months ago (3 children)

Didn't they remove XUL extensions to make their extension interface compatible with inferior chrome web extensions?

[–] Fisch@discuss.tchncs.de 16 points 3 months ago

I just did a quick online search and it seems like the reason for removing that was that it was way too much work to maintain and stopped them from implementing performance improvements for Firefox. Apparently it was also a lot of work for extension developers, since they had to update their extensions constantly.

That's just what I read tho, I wasn't there when XUL extensions where still a thing.

[–] mindbleach@sh.itjust.works 3 points 3 months ago

Yes, after twenty years of refusing to stabilize any part of that interface.

Chrome is absolutely the villain in this context. But Mozilla has been fucking itself over since the single-digit version numbers.

[–] pupbiru@aussie.zone 1 points 3 months ago

i wouldn’t say inferior… mozilla extensions were more performant and flexible, web extensions (ie the initial chrome format - now a standard that most browsers use) are easier to develop, and thus there were a lot more of them

[–] thingsiplay@beehaw.org 71 points 3 months ago (3 children)

Mozilla is silent about Firefox in general, not just about Manifest v2 and v3. I assume there is nothing new to report. Mozilla already stated somewhere they will support V2 and the extensions will work as before. But I don't understand why Mozilla does not use this moment from marketing standpoint to market the Firefox Extension Manifest V2 the hell out of it.

[–] sunzu2@thebrainbin.org 26 points 3 months ago (2 children)

Why piss off the guy who pays your bills bro

[–] ReversalHatchery@beehaw.org 8 points 3 months ago (1 children)

Don't they need to pay the bills if they don't want to get in antitrust investigations?

[–] 50MYT@aussie.zone 4 points 3 months ago

Google lawyers would make the calculation on how much, if, when, what etc monthly on this.

Mozilla's actions would factor into the calculation, but are definitely not the deciding factor.

[–] possiblylinux127@lemmy.zip 4 points 3 months ago

Because they are an organizational mess.

[–] jet@hackertalks.com 4 points 3 months ago

mozilla the organization has acted extremely reluctant, almost embarrassed, to talk about the browser.

[–] hemko@lemmy.dbzer0.com 42 points 3 months ago (3 children)

Because it doesn't make sense for all Firefox marketing material to be how shit chrome is. Save that bullshit for American president elections

[–] banazir@lemmy.ml 44 points 3 months ago (3 children)

It will be exciting to see Kamala and Trump debate whether Gecko or Blink should be the industry leader.

[–] hemko@lemmy.dbzer0.com 17 points 3 months ago (4 children)

Kinda off topic, but I find it weird that Kamala is usually referred by first name, and trump by surname.

[–] iAmTheTot@sh.itjust.works 21 points 3 months ago

It's a "brand recognition" kind of thing.

[–] Malgas@beehaw.org 8 points 3 months ago

I think it's because that's the more distinctive part of her name. "President Harris" sounds kind of generic, like the fictional president from an action movie.

It may start to constitute a pattern that the same was true of Hillary Clinton, though in that case it was likely that just saying "Clinton" might cause confusion with Bill.

Also Bernie Sanders is mostly referred to by his first name, so…

[–] scorp@lemmy.ml 6 points 3 months ago

Trump™ Kamala™

[–] possiblylinux127@lemmy.zip 1 points 3 months ago

They should get married. Then it would be Kamala Trump

[–] kbal@fedia.io 5 points 3 months ago

Harris can't deny the popularity of Blink. Trump is a die-hard EdgeHTML advocate.

[–] Midnitte@beehaw.org 5 points 3 months ago

Would it... though?

[–] Trilobite@lemm.ee 6 points 3 months ago (1 children)

Not saying anything bad about chrome is probably in the contract they have with Google which is most of their income

[–] hemko@lemmy.dbzer0.com 5 points 3 months ago (1 children)

Nah I doubt, it would be a huge lawsuit if google was found to pay competitors for staying quiet about their flaws

[–] Trilobite@lemm.ee 4 points 3 months ago

Sure they could sue but that's a lose lose situation even if they won Google would not give them money anymore and they need that to stay in Business

[–] possiblylinux127@lemmy.zip 4 points 3 months ago

Hold up

American presidents are hating on Chrome? What did I miss?

[–] KarnaSubarna@lemmy.ml 28 points 3 months ago* (last edited 3 months ago) (12 children)

... because Mozilla already clarified their position on this last year.

TL;DR

No, Mozilla is NOT ditching manifest v2.

Well what’s happening with MV2 you ask? Great question – in case you missed it, Google announced late last year their plans to resume their MV2 deprecation schedule. Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future. And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed.

Source: https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/

load more comments (12 replies)
[–] d0ntpan1c@lemmy.blahaj.zone 21 points 3 months ago* (last edited 3 months ago) (1 children)

Manifest v3 extensions work in Firefox, too. Its just the new thing. Its way easier to build cross-browser extensions with, too. V3 is actually a good thing overall, as its led to a lot of extensions being available for Firefox when the devs might have just targeted chrome. Way more feature parity between browsers with v3.

Chrome dropping support for v2 doesn't merit a response from Firefox because nothing changes for Firefox users and they're not going to drop support. Any one who actually cares (and they should) will move to Firefox on their own, so why waste advertising money on that? Eventually Firefox and any other browsers who want to allow stuff like ublock will probably have a way to do the same tasks in v3 (and the Firefox Dev team has said as much in blog posts for ages), then it'll just be a feature that doesn't work in chrome. V3 just simply doesn't have the API that ublock uses in v2.

There have been discussions for years in the w3c standards group about this whole shitshow and this is one the chrome team have basically refused to budge on despite all the other browser teams. Its honestlu a mirscle they delayed it as long as they have. This was originally supposed to happen at the start of 2023.

Chrome is kinda like a country with a overrule veto vote at the UN when it comes to w3c working groups since they can just do whatever they want anyway, and nothing will change until they no longer have that power. That said, browser feature parity is at an all time high recently and its because all the browser teams are working together better than ever. There are just these hard limits chrome chooses to stick to.

[–] orcrist@lemm.ee 4 points 3 months ago

What you said makes sense from a technical standpoint but not from a practical standpoint. If I'm losing good adblock on Chrome, but good ad block still works on Firefox, it would be easy for Mozilla to put up some blog posts or tweets or whatever to point out that they are a great option, because they're adblock isn't going anywhere.

This is an obvious concern for many users, Mozilla has the capability to issue a press release or anything at all, and they've chosen not to do so. Therefore, people are reasonably questioning why they've chosen not to do so. Free marketing but they're throwing it away, and their best defense for doing nothing is essentially what you wrote, which is essentially to dodge the precise issue at hand.

[–] KingThrillgore@lemmy.ml 20 points 3 months ago

"We really can't rock the boat on this Google money "

[–] smpl@discuss.tchncs.de 14 points 3 months ago

One of the most controversial changes of Chrome’s MV3 approach is the removal of blocking WebRequest, which provides a level of power and flexibility that is critical to enabling advanced privacy and content blocking features. Unfortunately, that power has also been used to harm users in a variety of ways. Chrome’s solution in MV3 was to define a more narrowly scoped API (declarativeNetRequest) as a replacement. However, this will limit the capabilities of certain types of privacy extensions without adequate replacement.

Mozilla will maintain support for blocking WebRequest in MV3. To maximize compatibility with other browsers, we will also ship support for declarativeNetRequest. We will continue to work with content blockers and other key consumers of this API to identify current and future alternatives where appropriate. Content blocking is one of the most important use cases for extensions, and we are committed to ensuring that Firefox users have access to the best privacy tools available.

https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-firefox-recap-next-steps/

[–] Trainguyrom@reddthat.com 11 points 3 months ago (1 children)

Biggest thing I learned from that article is that over 1/3 of users use an adblocker. I did not know adblockers had become so prevalent amongst normies

[–] rasmus@lemmy.world 9 points 3 months ago (1 children)

Have you visited a website without it, its 10:1 ratio of ads to content

[–] Trainguyrom@reddthat.com 9 points 3 months ago

Oh yeah I would never browse the internet unprotected by an adblocker, but knowing that normies are feeling this way now too? That's something else entirely

[–] ZeroHora@lemmy.ml 9 points 3 months ago (2 children)

Mozilla should spent money to advertise(Is this right? I don't know verbs fuck) a flaw in Chrome? It's not like the public cares about it.

[–] ReversalHatchery@beehaw.org 4 points 3 months ago

No, not a flaw in chrome, it has always had flaws even regarding what security oriented extensions like uBO could do.
Not a flaw in chrome, but that the tools they depended on still work over here.

[–] possiblylinux127@lemmy.zip 1 points 3 months ago

The do get most of there funding from Google

[–] masterofn001@lemmy.ca 5 points 3 months ago

There are thousands of user configurable flags/settings in about:config

An option for Manifest V3 has been there for quite a while. It wasn't enabled by default.

In FF Nightly for Android it is enabled by default along with V2.

[–] j4yt33@feddit.org 4 points 3 months ago

Why would it not be?

[–] Matriks404@lemmy.world 3 points 3 months ago

Well of course they are, after all they are slowly becoming one of these malicious companies it tried to fight with.

load more comments
view more: next ›