Replying to @⁨Lexam@lemmy.world⁩

Surprisingly, the Internet seems to look mostly favourably on Audacity these days. I never really kept up with it at the time, but apparently all the allegedly heinous (mis)features were opt-in. (Further verification of this may be required.)

I can't tell if that's the result of a really good scrubbing of bad search results or whether they genuinely cleaned up their act.

Either way, Tenacity, the fork that came about as a result of the controversy, still exists, and apparently has themes to change the look just like Audacity is claiming to have done now, so if you're uncertain, that's always an option.

Replying to @⁨palordrolap@fedia.io⁩

I got tired of Tenacity staying stagnant for months, and still having documentation link issues. Meanwhile, Audacity was actually making meaningful improvements.

After diving deeper in the nontroversy, and seeing their in-depth video explaining their design decisions, I concluded that they genuinely want to improve the software and aren’t trying to fuck over the OSS community. So, I switched back when I dumped Windows and switched to Linux.

There’s an extreme black and white view of these kinds of issues that crop up in the community that just pisses me off, and shoddy tech reporting doesn’t help matters. This wasn’t a “Oracle buys MySQL” situation, and the response didn’t deserve a fork. But, hey, it’s free software, and people can fork whatever they want.

Replying to @⁨MetaStatistical@lemmy.zip⁩

It wasn’t about “shoddy tech reporting”. Why would a FOSS audio editing app need to know your country, any personal “Data necessary for law enforcement, litigation and authorities’ requests (if any)”, share it with a wide network of people and potential buyers, as well as their “main office in Russia”? There should be no telemetry of any sort. Any logs kept should be strictly local, which would allow users to send them to the support team voluntarily.

en

Replying to @⁨SlurpingPus@lemmy.world⁩

Also your city and ISP, but that information isn’t mentioned, so it’s evident it wasn’t to catch all. Nothing in the way it’s worded is consistent with your rationale, and the actual policy is significantly more broad. They’re not specifying the information shared with law enforcement would be limited to the IP address or data that can be gathered from it. It’s a completely separate row.

Replying to @⁨Zagorath@quokk.au⁩

Why would I want an auto-update mechanism in the software? That’s what my distro’s package manager is for. And it doesn’t care who I am or where I’m from. Nor has any other software I’ve encountered with such a useless-to-Linux-users mechanism demanded any information about me.

In short, that rationale is obvious nonsense. That may be why they claim they’re doing it, but it doesn’t hold up.

Replying to @⁨Zagorath@quokk.au⁩

I apologize for phrasing things so poorly that several people seem to have missed my actual point, which was: no one else with an auto-update feature requires any information about you, therefore if they claim that’s their reason for asking for users’ personal information, they’re lying. They may have other reasons, which they have not stated. They may even be good reasons, although I’m not holding my breath.

And yes, I have compiled my own copy with that nonsense switched off, thanks for asking. However, it’s the job of people who understand that this is overreach to push back against it on behalf of the people who lack the knowledge, time, or energy to investigate it. I don’t like throwing even Windows users under the bus.