you are viewing a single comment's thread
view the rest of the comments
[–] 66 points 1 month ago (2 children)

they stopped that very soon after the controversy started

  • source
  • parent
  • hideshow 4 child comments
  • [–] 33 points 1 month ago (2 children)

    The fact that they even considered this, made me lose trust in them. Tenacity FTW.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 22 points 1 month ago (3 children)

    i never understood the vitriol against debug-only opt-in telemetry

  • source
  • parent
  • hideshow 6 child comments
  • [–] 21 points 1 month ago (1 child)

    I'll venture, it's a natural if misdirected immune reaction from people who are all too aware they are being tracked ceaselessly and relentlessly, all day, everyday, not to their benefit. So sure, this one piece of software swears its own tracking is just for debugging purposes... But why risk it?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 11 points 1 month ago (2 children)

    It only became opt-in when people found out.

    And it's not the only problem I have with Audacity, this is from an article in slashgear

    "...For example, it says that it collects data necessary for law enforcement but doesn't specify what kind of data is collected.

    There are also questions regarding the storage of data, which is located in servers in the USA, Russia, and the European Economic Area. IP addresses, for example, are stored in an identifiable way for a day before being hashed and then stored in servers for a year. The new policy also disallows people under the age of 13 from using the software, which, as FOSS Post points out, is a violation of the GPL license that Audacity uses."

  • source
  • parent
  • hideshow 4 child comments
  • [–] 10 points 1 month ago* (1 child)

    it was always opt-in.

    people finding out: https://github.com/audacity/audacity/pull/835#issuecomment-833778895

    people highlight the opt-in dialog text: https://github.com/audacity/audacity/pull/835#discussion_r627756976

    there are no commits in between; it could not have been changed to opt-in "when people found out" as you claim.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 1 month ago (1 child)

    Perhaps you are right, I could be remembering it wrong (but really I don't feel like wading through that comment-section), the telemetry was just the tip of the iceberg for me, violating GPL licence and things like using google and yandex are among many reasons I just don't trust them with my music.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 month ago

    the google and yandex thing is the telemetry thing, and i talk about the privacy policy (the GPL thing you mention) below. what are the other reasons? all i see is the CLA thing which is very very legit, but again all of these things are from four or five years ago, and we can always riot when they do turn it proprietary.

  • source
  • parent
  • [–] 3 points 1 month ago

    It only became opt-in when people found out.

    source? this is an open-source respository and everything i've found contradicts that

    the privacy policy thing was a different thing that was definitely a strike in my eyes, but keep in mind that they reverted that too pretty soon after controversy, claimed it was overzealous lawyering, and it's been four years since without any further incidents.

  • source
  • parent
  • [–] 6 points 1 month ago (1 child)

    First, it was never meant to be opt in.

    Second, that's like saying you don't see the problem with the Nuremberg laws.

    Taken out of context, they're bad.

    Taken in context, they're the first step towards something much, much worse.

    And when such a canary in the coalmine dies the rational response is to not understand how it died and proceed further down the mine.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 1 month ago* (1 child)

    it was never meant to be opt in.

    Source? I've posted numerous pieces of evidence to the contrary:

    people finding out: https://github.com/audacity/audacity/pull/835#issuecomment-833778895

    people highlight the opt-in dialog text: https://github.com/audacity/audacity/pull/835#discussion_r627756976

    there are no commits in between; it could not have been changed to opt-in "when people found out" as you claim.

    For one thing the Nuremberg Laws (1935) prohibit interracial marriage. That alone is bad. I also believe laws that restrict citizenship are bad. Of course I see a big problem with allat.

    There were also many more "incidents" in the four years following the Nuremberg Laws... Audacity, none.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 1 month ago (1 child)
  • [–] 15 points 1 month ago* (last edited 1 month ago)

    technically it was never shipped and only planned to be enabled in testing builds, and no code ever touched anything outside of audacity on the computer except maybe hardware and dependency details though i’d have to check again for those

    edit: besides audacity stuff it only collected the audacity sqlite3 engine and OS version

  • source
  • parent