3 ms·

You're comparing web tools/browsers to an offline audio editor. Though I agree it's a PR disaster—people are upset, I don't think folks can be reasoned with si

by theden 5y ago

You're comparing web tools/browsers to an offline audio editor. Though I agree it's a PR disaster—people are upset, I don't think folks can be reasoned with since it's partly a backlash of yet another small community being taken over by corporate mediocrity.

noobermin 5y ago
People are not getting the point. If you have to download the software they will get this info, full stop. There is no way that they won't get your user agent. That's what this privacy policy refers to. Same if you download auto-updates, you have to download the updates from the internet which requires connecting to their webserver, and they'll get this information. As for the telemetry, that's opt-in. May be the bloat and other things that are being mentioned are about that? But for the first two bullets on information that is mentioned as collected (IP addr and os info) that is mentioned in the linked github discussion, they are literally what they will get because you had to visit their site to download it or because you automatically download updates.
- Kim_Bruning 5y ago
  'Anyone who says "full stop" is an idiot, full stop.' One of the more common ways to get audacity (via your distribution) happens to [often] not provide your/a user agent string to the audacity developers, nor do they get a copy of your ip. In the context of a distribution: the auto-update mechanism is also problematic and needs to be disabled at install time. And all of this is a) reinventing the wheel. b ) breaks the assumption that the computer will only connect to the network with a human-in-the-loop. c) completely unnecessary in the first place. Let the distributions keep track of issues and report them upstream.
  - justaj 5y ago
    What about users who don't download it via their distribution package managers (for example because their distributions ship very old versions of Audacity)? And what about Windows users?
    - Kim_Bruning 5y ago
      I was replying to "If you have to download the software they will get this info, full stop" . The full stop was not as full as they claimed ;-)

by theden 5y ago

noobermin 5y ago

People are not getting the point. If you have to download the software they will get this info, full stop. There is no way that they won't get your user agent. That's what this privacy policy refers to. Same if you download auto-updates, you have to download the updates from the internet which requires connecting to their webserver, and they'll get this information. As for the telemetry, that's opt-in. May be the bloat and other things that are being mentioned are about that? But for the first two bullets on information that is mentioned as collected (IP addr and os info) that is mentioned in the linked github discussion, they are literally what they will get because you had to visit their site to download it or because you automatically download updates.

Kim_Bruning 5y ago
'Anyone who says "full stop" is an idiot, full stop.' One of the more common ways to get audacity (via your distribution) happens to [often] not provide your/a user agent string to the audacity developers, nor do they get a copy of your ip. In the context of a distribution: the auto-update mechanism is also problematic and needs to be disabled at install time. And all of this is a) reinventing the wheel. b ) breaks the assumption that the computer will only connect to the network with a human-in-the-loop. c) completely unnecessary in the first place. Let the distributions keep track of issues and report them upstream.
- justaj 5y ago
  What about users who don't download it via their distribution package managers (for example because their distributions ship very old versions of Audacity)? And what about Windows users?
  - Kim_Bruning 5y ago
    I was replying to "If you have to download the software they will get this info, full stop" . The full stop was not as full as they claimed ;-)