460
Chrome’s next weapon in the War on Ad Blockers: Slower extension updates (arstechnica.com)
submitted 2 years ago by to c/technology@lemmy.world
103 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[+] -7 points 2 years ago* (8 children)

It wouldn't surprise me if they removed features to make popular extensions work. Time will tell. I'm still salty about Jetpack.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 4 points 2 years ago* (7 children)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] -4 points 2 years ago (6 children)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 3 points 2 years ago*

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 years ago (4 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 2 years ago (3 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 2 years ago (2 children)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 years ago* (last edited 2 years ago)

    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.)

  • permalink
  • fedilink
  • source
  • parent