The terms were just introduced on Wednesday.

AI Summary:

Overview:

  • Mozilla is updating its new Terms of Use for Firefox due to criticism over unclear language about user data.
  • Original terms seemed to give Mozilla broad ownership of user data, causing concern.
  • Updated terms emphasize limited scope of data interaction, stating Mozilla only needs rights necessary to operate Firefox.
  • Mozilla acknowledges confusion and aims to clarify their intent to make Firefox work without owning user content.
  • Company explains they don’t make blanket claims of “never selling data” due to evolving legal definitions and obligations.
  • Mozilla collects and shares some data with partners to keep Firefox commercially viable, but ensures data is anonymized or shared in aggregate.
  • woelkchen@lemmy.worldEnglish
    476·
    23 hours ago

    Friendship ended with Firefox,❎ Librewolf is my new best friend. ✅

    A big problem with such forks (same with packages made by Linux distributors) is that there is a delay between official FF release and the release of the corresponding update of the fork. 99% of the time this doesn’t matter much but when there is a severe security issue, the patch needs to be available ASAP.

    Past enshittifications of Firefox could be disabled by users. Users who know what to disable don’t need such forks then.

    I’m not yet clear what Mozilla even intends. Is it just an adjustment of language of things that are already in FF and can be disabled easily? If so, I just keep the following shit disabled and benefit from earlier update releases.

    • rottingleaf@lemmy.worldEnglish
      3·
      7 hours ago

      A big problem with such forks (same with packages made by Linux distributors) is that there is a delay between official FF release and the release of the corresponding update of the fork.

      That’s called a patched downstream, not a fork.

      LibreOffice was a fork of OpenOffice. OpenBSD was a fork of NetBSD.

    • cley_faye@lemmy.worldEnglish
      5·
      11 hours ago

      I have not dug too deep into it for now (especially if I end up changing browser), but even with everything in the preferences disabled, examining the content of about:config gives a lot of telemetry.whatever.enabled left to true, sometimes with names that do not seem to match any option given to the user. That’s not a good look either.

      • Kausta@lemm.eeEnglish
        3·
        7 hours ago

        And you cannot change those in the default mobile Firefox since about:config is disabled (by their claim that it may break stuff in the ui)

    • FooBarrington@lemmy.worldEnglish
      82·
      14 hours ago

      The issue is that Mozilla is actively hiding these settings. There’s one (I forgot which one) that you can’t find by searching for the title in the FF settings, you have to scroll to it yourself.

      • woelkchen@lemmy.worldEnglish
        43·
        12 hours ago

        The issue is that Mozilla is actively hiding these settings.

        They are under “Privacy”, just as I expected where they would.

        There’s one (I forgot which one) that you can’t find by searching for the title in the FF settings, you have to scroll to it yourself.

        🤷

        • cley_faye@lemmy.worldEnglish
          43·
          11 hours ago

          Yes, you can disable the settings that are exposed to you with a checkbox. How about all the other that have no checkboxes and you can find by snooping around in either the code or about:config ?

          • woelkchen@lemmy.worldEnglish
            6·
            11 hours ago

            How about all the other that have no checkboxes and you can find by snooping around in either the code or about:config ?

            Which are? Genuine question. I’m not aware of those either.

            • cley_faye@lemmy.worldEnglish
              11·
              3 hours ago

              I’m not going to enumerate them, mostly because I did not keep track of which one was on and which one was off before messing all of them up. If you’re curious, open “about:config” and search for “survey*.enabled”, “collect*.enabled”. Even with all settings disabled, some of them remains on, and they do cause traffic to the (documented) endpoints.

        • FooBarrington@lemmy.worldEnglish
          33·
          12 hours ago

          Dude, I’m not talking about the specific settings you’ve shown. There’s more settings you should set regarding privacy, and (at least a couple of months ago) one of them wasn’t appearing when searching for it.