• @drislands
      link
      English
      2210 months ago

      What? You must be joking. Really? The entire thing was about opt-in error reporting?

      … seriously, that can’t be it, can it?

      • Eager Eagle
        link
        English
        32
        edit-2
        10 months ago

        Not really that simple, it was an apparent change to the privacy policy that vaguely anticipated collection of arbitrary user data, which shook the confidence of the open source community on the project. The fact this happened right after audacity was sold was the cherry on top.

        https://github.com/audacity/audacity/issues/1213

        Changes were eventually reverted or revised.

        • @StereoTrespasser
          link
          English
          710 months ago

          If opt-in telemetry is spyware then the FOSS community truly is off the rails.

        • @[email protected]
          link
          fedilink
          English
          110 months ago

          I’ve read this exact or very similar comment from you for the fourth time at least. You’re a spambot as far as I’m concerned.

    • @books
      link
      English
      610 months ago

      Point a has always me me wonder, is that accurate? Are there actually people going through the code to make sure open source isn’t malicious? I can barely read my coworkers code… Let alone a strangers.

      • @aidan
        link
        English
        310 months ago

        Its way less work than going through the code to check for telemetry unless it is an intentionally hidden attack- just use Wireshark and check if there is network traffic other than checking for an update on program start.

      • @[email protected]
        link
        fedilink
        English
        210 months ago

        If a project is popular people will make changes to it every day. But you can look at the repo and judge for yourself.