466
Chrome’s next weapon in the War on Ad Blockers: Slower extension updates
(arstechnica.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Dec 2023
466 points (100.0% liked)
Technology
59554 readers
3603 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
I'm confident that Mozilla will follow suite sooner or later to make it easier for extension developers to make extensions for both browsers. Mozilla did that when manifest v1 came along, removed a bunch of functionality from Jetpack, and aligned with Google.
They implement Manifest v3 already for compatibility, but without the user-hostile restrictions.
It wouldn't surprise me if they removed features to make popular extensions work. Time will tell. I'm still salty about Jetpack.
What do you suppose Firefox's goal or motive would be in removing features for the end user? Isn't their purpose to compete with Chrome and be better?
I can only guess that there is a monetary incentive. They get 400 million a year from Google. Why would you compete if you get that kind of money for being the underdog?
you're definitely right and it's obvious that Mozilla can't make Firefox as private as they advertise it because of their monetary interests (thus google is default, there are paid promotions in the home page, a lot of privacy features aren't enabled by default).
But at least they make a decent work implementing them and because it's free software then other projects like Tor or Librewolf can enable all the privacy features, remove the trackers and release a damn good browser.
It would stand to reason that if they were as bad as Chrome, that people would just stick with Chrome and they would miss out on profit entirely, I would think. If monetary incentive is a reason, purposely hamstringing themselves seems counter-intuitive toward that goal.
The thing is, firefox is the only other browser out there that doesn't use the same browser engine. They know it too. They have absolutely no incentive to change, unless some other browser engine and a corresponding browser were to pop up that competed with them. If a group decided "we're going to make a browser that is really private and doesn't do what Mozilla does", and they got a footing, only then would Mozilla consider competing, but only to be better than that other browser, not Chrome.
For Mozilla to want to be better than Chrome, Google would have to do some incredibly dumb shit, Mozilla would need an enormous cash injection from another party, or the current stewards of Mozilla would need to be replaced with people who actually care. IMO, those are all unlikely.
In this specific context we are talking about Manifest V3 artificially limiting the number of rules in an extension. That's it, it's artificial, there is no reason for it to exist other than Google purposely degrading the capability. What does Mozilla have to gain by also degrading themselves?
Compatibility. You want to have enough users to be considered for being paid off, but not too little that you can be ignored. It's similar to the linux gaming move: on linux you can't just add a windows compatible interface to the kernel, so you have to translate it. Game developers thus focus on windows and ignore linux since there build process is completely different. As a browser, you sure as hell can introduce a common interface --> extension devs write their extension once and it run on firefox too. Users who care enough can thus switch without much hassle.
It's a numbers game.
It will still be compatible, Firefox just doesn't need to add a limiter, meaning the same extension will run better on Firefox than Chrome in the end. That's how I see this all unfolding at least. (I'm a javascript developer, I audit all the extension code I run generally, my perspective is purely technical and not political on the matter.)
Why would a nonprofit org do that?
Money. Google is their biggest source of income.