A great example of why I’d just about always prefer to get software packaged by my distro (Debian) over “straight from the developer” methods (including pip, npm, flatpak, etc.). I remember hearing about this and being like “Oh, that’s bad, but it’s not going to affect me.”
Yes tenacity is a community fork that happened during the hubbub with the musescore takeover and telemetry additions and doesn’t have any of it.
It also has a couple of quality-of-life additions and a few new features but nothing specifically different as of yet. Mostly, it’s a good community-lead fork that has some momentum behind it - since it also unifies the developers behind 2-3 protest forks that happened at the same time and I think that’s generally (if not a safe bet) a good thing to support.
Too
longvideo, didn’treadwatch.So what happened to audacity?
Basically, they were bought out by MuseGroup. MuseGroup tried to add telemetry and some bad TOS stuff. It all got reversed.
A great example of why I’d just about always prefer to get software packaged by my distro (Debian) over “straight from the developer” methods (including pip, npm, flatpak, etc.). I remember hearing about this and being like “Oh, that’s bad, but it’s not going to affect me.”
So Audacity is fine to use (again)?
The version you want to use is Tenacity. It seems good, but I haven’t done extensive reading on it.
Yes tenacity is a community fork that happened during the hubbub with the musescore takeover and telemetry additions and doesn’t have any of it.
It also has a couple of quality-of-life additions and a few new features but nothing specifically different as of yet. Mostly, it’s a good community-lead fork that has some momentum behind it - since it also unifies the developers behind 2-3 protest forks that happened at the same time and I think that’s generally (if not a safe bet) a good thing to support.
I hope they will fork MuseScore too. I really don’t like the direction in which that company is going…