4 ms·
Articles is from July 8th. This is a fast moving story. The current state of affairs (from Muse Group's perspective) is here: https://github.com/audacity/audac
by PaulDavisThe1st 5y ago
Articles is from July 8th. This is a fast moving story.
The current state of affairs (from Muse Group's perspective) is here: https://github.com/audacity/audacity/discussions/1353 https://github.com/audacity/audacity/discussions/1353 (published today)
- Karunamon 5y agoFrom the Github thread: >I have been doing 3.0.3 Release Candidate testing and all seems good: >a) error and crash reporting are one-off opt-in each time you get such a dialog, >b) the update checking dialog that you get on initial launch of 3.0.3 enables you to turn off update checking in Application prefs BEFORE you hit the OK button - and thus no data is sent. Everything is now as opt-in as it can be expected to, and the privacy policy has nothing untoward in it. I'm not super happy with how long it took to get to this point, but at least the wound has been debrided.
- infogulch 5y agoThis seems like a reasonable and thorough response. They revised and cut unnecessary bits and added clarification where possible within a reasonable time frame for these matters. Good job. I really don't get the wailing and gnashing of teeth against even the principle of adding update checking and error reporting features. Real, regular people will get tangible benefits from these features. Their scope is so limited and implementation (now) drawn down to such a sharp point I can't really sympathize with a hard-line counterposition that these features must be defacto evil.
- TeMPOraL 5y agoThe "wailing and gnashing of teeth" is against updates and error checking being opt-out, or even not opt-outable at all. Sometimes this gets mixed with observations that telemetry and auto-updates are modern-day antipatterns, encouraging bad software development practices and resulting in subpar products. Personally, I feel that a ToS/privacy policy for Audacity would be more palatable if it explicitly limited scope of data collection to optional features of update checks and error reports.
- rhizome 5y agoThe question of data collection could use a little reverse consideration: what could Audacity possibly collect that would be of interest to law enforcement? The only thing I can think of is IP address with a timestamp (which I'm not sure would be admissible as evidence anywhere) given their current stance, or....more? They want to add video so they have to be prepared for e.g. pedo interest? The circumstances in the movie "Blow Up?" I really can't think of anything from the real world. Beyond that, there's nothing that requires them to allow for this in their TOS. There's no loose end by not including it; it's not a 't' to be crossed or an 'i' to be dotted. I'm eager to be corrected, but I just don't see why they'd need to change the TOS at all except to replace some ownership info.
- infogulch 5y agoI had a big comment drafted but I'm realizing that I'm basically copy-pasting the whole policy and comments (as said elsewhere itt, "Everything is now as opt-in as it can be expected to be"), so it would be quicker and more accurate to ask you to just read the new privacy notice directly to see that everything you asked for and more is already present. It's quite readable: https://www.audacityteam.org/about/desktop-privacy-notice/ https://www.audacityteam.org/about/desktop-privacy-notice/
- bmn__ 5y agoYou have to come up with the modicum of empathy to put yourself in the shoes of the users to be able to understand why they are angry. • You must acknowledge that privacy is a basic human right.¹ Maybe you were brought up in a culture where these rights don't count; well, here's your opportunity to learn and grow. Maybe you have simply forgotten your school lessons, that's not good and the blame falls squarely on your shoulders then. • The users were promised UI improvements and an eighth zoom button, instead they got malicious software and bad treatment from the new owners. • Look at what Muse originally planned, not what they compromised to after the public push-back. • There is a person at Muse named Daniel Ray who is a sociopath and lacks the basic decency/internal filter in communicating with other people and utter lack of self-preservation for avoiding bad consequences for himself, such that he thinks that threatening a software developer on public Github with doxxing him into the gulag is an acceptable thing to do. ¹ Let's see how these rephrases violating some other human rights feel: "I really don't get the wailing and gnashing of teeth against even the principle of forced castration and hysterectomy." "I really don't get the wailing and gnashing of teeth against even the principle of trading and using chattel slaves."
- mastazi 5y ago> We have removed the provision that discourages children under 13 years old from using Audacity This point is very important. Like many other open source projects, Audacity is used in a very large number of education-related projects. Having 13 as the minimum age was going to be a huge problem.
- papishow 5y agoI agree, but if memory servers correct they are lying here. Or at least being extremely disingenuous. They didn't discourage children under 13 years old from using Audacity. They forbade children under 13 years old from using Audacity.
- viraptor 5y agoThat's not correct. The actual quote was: > The App we provide is not intended for individuals below the age of 13. If you are under 13 years old, please do not use the App. They did not forbid it.
- okamiueru 5y agoThat's a very interesting nuance. What does "please do not" mean in this context, and could its intended effect be?
- papishow 5y agoThank you for that correction, it seems I have been led astray by some interesting reporting then.
- heurisko 5y ago"Please do not use the App" is forbidding use of the app.
- Gravityloss 5y agoWhat's the motivation for age being mentioned at all?
- deleted 5y ago[deleted]
- ChrisArchitect 5y agocorrect and it was shared 2 weeks ago also. Best to move along to more current developments. Discussion on the mentioned Latest Update https://news.ycombinator.com/item?id=27927407 https://news.ycombinator.com/item?id=27927407