People didn't lose their collective minds.
The Muse Group acquired Audacity, then introduced:
- a CLA (which, between other things, allows them to make closed source versions of Audacity)
- telemetry
- a very controversial privacy policy
People aren't losing their minds. And please, do not spread misinformation.
https://docs.github.com/en/github/site-policy/github-privacy...
https://www.debian.org/legal/privacy.en.html
https://fedoraproject.org/wiki/Legal:PrivacyPolicy
https://www.fsf.org/about/free-software-foundation-privacy-p...
Sure it's not "the norm" but personally I run a Poudriere[0] server and build all my own software packages. One server syncs the FreeBSD Ports collection and downloads the needed software source distfiles, but then none of my other machines/jails are allowed to install software from anywhere outside my own network. A lot of them don't get any Internet access at all.
That still has nothing to do with in-app analytics though.
It absolutely does have to do with analytics: in particular, Debian has an opt-in anayltics system called "popcon" which is mentioned in the privacy policy.
Presumably the objective is to have machines that do not connect to the network without at least a human in the loop. This used to be the default, and is still very helpful in a lot of situations. For one, it keeps the noise down when you are trying to debug network issues.
That FSF link relates to their site.
Audacity is an offline non-networked application.
But all previous commits they'd build on are GPL..
As for how they could make it better: make it opt-in not opt-out.
This is the kind of toxic behaviour we all tolerate from commercial software, but people get mad when it leaks into open source.
Roughly.
Here is the link towards the Privacy notice on the 2nd of July. https://archive.fo/d3LBR#selection-673.0-673.129
The school installing software that has terms not allowing those under 13 to use it, because those kids don't have the legal right to consent to the software collecting information from them, has a very real chance of becoming an issue - both for the school and whoever made the decision.
A more direct example would be in Chrome/Firefox/etc automatically checking for updates, which is the equivalent of what Audacity describes in the linked post.
It's not going to happen for all kinds of reasons, but there's a lot that could be said in favour of prohibiting _unsupervised_ Internet access to children 12 and under.
Having children in that age range use the app would require Audacity to seek parental consent by "[making] reasonable efforts (taking into account the available technology and risks inherent in the processing) to verify that the person providing consent holds parental responsibility for the child."1
While they wrote to minors "please do not use the App", they also wrote "The App we provide is not intended for individuals below the age of 13."2 Not being a lawyer, I cannot talk about the implications of these passages.
src1: https://ico.org.uk/for-organisations/guide-to-data-protectio... src2: link in my parent comment
I have never once used software I thought was actually good that was designed based on feedback from telemetry.
When I was a kid, computers weren't connected to the internet. The first time I had a connection it was at 33.6 kbit/s (at 25 cents per minute).
Can you imagine if I had had all these 'modern' programs on my computer that would suddenly try to talk over that tiny straw of a connection? It'd be unusable!
There are still a lot of reasons why you would like to maybe hope that a computer doesn't try to randomly talk to everyone and everything on the intertubes on a whim.
For instance: said computer might be acting as a firewall, or it's being used for SCADA, needs to comply with corporate or government security policy, or is otherwise supposed to be something-gapped.
I guess for regular consumer technology that hope has long fled. You'd think that floss software could automatically be trusted to be quiet-by-default, but I guess that time is now past as well.
Possibly software that is quiet-by-default needs to start explicitly noting that it is so; so that if you have a particular task that really needs a quiet-by-default machine, you can draw from that subset.
You are right that audacity probably doesn't need to be in the quiet-by-default category. But ...eh... somehow this feels like a retreat.
Their ability to make decisions doesn't matter. It is does not justify putting spyware into previously trusted software.
Also, nobody believes that excuse for a second. They couldn't care less about "improving" anything but their bottom line. They are merely capitalizing on the trustworthiness of an open source project in an attempt to extract maximum value out of its users.
If they wanted to improve the software, they would have hired somebody with good taste to work on it. People with good taste do not tolerate abusive spyware.
> Can someone fill me in on what this person could have done better?
They could have not collected any "metrics" in the first place. That way, this ridiculous privacy policy would never have been necessary.
"Just ask those people!" Is what I think every single time, when this kind of issue pops up. Ask the people what they find annoying about the product, ask them what they like. There are many questions you can ask and which yield a much more direct result than telemetry data, without upsetting a community and without coming across as sneaky and disrespectful of user privacy.
It's not uncommon for me to approve such features when I'm dealing with software I trust, and when I'm thoroughly informed of exactly what data they're collecting and why. If I see a list of reasonable data points and it's not too intrusive or overreaching (and if I can examine the data before it's sent) then I'm quite often okay with it (again, with software I already trust for other reasons).
I don't understand the reaction either. It's hard to talk about this stuff here because of the anti-analytics groupthink. Everyone seems to jump to the worst possible conclusion whenever it's brought up.
I can't help but wonder if the people screeching about it have ever actually put analytics in their own products. Understanding how your software is used in the real world by real users is absolutely invaluable!
Assuming integrity, I think the people complaining about it would indeed do unto others as they would have others do unto themselves. That is to say: not include telemetry.
Audacity needed a maintainer to help with support and development. Developer, who has a pretty active YouTube channel covering design in music software, takes interest and leads the project. Said developer adds telemetry to help make more informed decisions. People lose their collective minds.
Can someone fill me in on what this person could have done better? Honestly, it seems like pearl-clutching from a select group of users who never gave a shit in the first place and just want to whine about something they never contributed to and get to use for free.