Comment on Firefox will have a built-in ‘fake reviews detector’ — Amazon is in trouble

• neshura@bookwormstory.social ⁨1⁩ ⁨year⁩ ago

  Compromise: Develop it as a Plugin and then install it by default. That way people who don’t want the feature can easily remove it completely. That approach would likely also reduce the number of Firefox forks whose sole purpose is to remove the new features some consider bloat.

  source

  • redcalcium@lemmy.institute ⁨1⁩ ⁨year⁩ ago

    That’s actually what Firefox usually did for these kind of features. They’re usually delayed as system add-ons.

    source
  • Lepsea@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    Or make it so that people have a choice to add some of the features when installing the browser. Debloating is not fun

    source

    • Kusimulkku@lemm.ee ⁨1⁩ ⁨year⁩ ago

      Sometimes it feels like debloating is a hobby to people with little to show for it

      source

      • Aceticon@lemmy.world ⁨1⁩ ⁨year⁩ ago

        Well, the purpose of debloating is to end up with less stuff than you started with ;)

        source

        • -> View More Comments
    • ByGourou@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      Most people don’t want a 45th prompt when they just want to install firefox to check facebook and their mail

      source
    • neshura@bookwormstory.social ⁨1⁩ ⁨year⁩ ago

      True, also wouldn’t be too much work. Just some additional dialogues on first start up asking you which plugins you’d like installed

      source
  • tweeks@feddit.nl ⁨1⁩ ⁨year⁩ ago

    Good solution, perhaps two simple options at browser install: Default / Custom. That way you don’t have to uninstall all the stuff at the end.

    source

    • BaardFigur@lemmy.world ⁨1⁩ ⁨year⁩ ago

      But how should they handle a version update where a given addon is added. A popup?

      source

      • Gestrid@lemmy.ca ⁨1⁩ ⁨year⁩ ago

        Probably handle it similarly to how Chrome handles an extension asking for new permissions. It disables the add-on and gives the user a small non-intrusive notification on the options menu. Opening the notification notified the user about the change in permissions and asks them if they want to re-enable the add-on or remove it from Chrome.

        source
• Engywuck@lemm.ee ⁨1⁩ ⁨year⁩ ago

  Now, let’s talk about adblockers… Oh, wait, Google would get upset if FF had an inbuild adblocker…

  source

  • Honytawk@lemmy.zip ⁨1⁩ ⁨year⁩ ago

    If Google stopped sponsoring, Mozilla would go down and Google would get slammed with anti-monopoly lawsuits from the EU.

    So Mozilla can do whatever they want and Google won’t stop sending them money. Since that is a lot more profitable in the long run.

    source

    • Engywuck@lemm.ee ⁨1⁩ ⁨year⁩ ago

      Mozilla can do whatever they want and Google won’t stop sending them money.

      So… What are they waiting for? Are they going to rely on gorhill for ever?

      source

      • jtk@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

        You want Mozilla choosing what gets blocked?

        source

        • -> View More Comments
  • netchami@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    Use LibreWolf. It’s Firefox with pre-installed uBlock Origin and pre-configured privacy settings. It also doesn’t have any of the Firefox bloat like Pocket

    source

    • Engywuck@lemm.ee ⁨1⁩ ⁨year⁩ ago

      No way I’m giving market share to gecko and, thus, to Mozilla. I just point how how hypocrite they are.

      source
  • jtk@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

    Blockers need to be an extension, keeps everyone honest.

    source
• mitrosus@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

  …you would have to install plugins and make it your own.

  Reminds me of gnome.

  source