sneedacity VS audacity

They're looking into a new name as well, https://github.com/temporary-audacity/audacity/issues/5

Here's a forked version with telemetry code removed (not mine, and I haven't read the diffs to verify, but it's all visible). But this is the beauty of open source, stuffs available you aren't required to follow new owners if they pull stuff like this: https://github.com/temporary-audacity/audacity/

Audacity will be fine and will continue to be at the top but I think we will see some new popular Forks/Competitors out there, such as this one8, that may or may not rise to the challenge of maintaining a complex application and be able to keep it up to date, work on bugs and issues and also continue to upgrade its feature set an UI. Its something I plan on paying attention to for the foreseeable future and hope this serves as a reminder, Much like OpenJDK, OpenOffice and XFree86 before them, to any other open source projects or Corporate Companies that buy up the Open Source Community Projects that they need to stay true to the community and the Open Source ethos.

It looks like everyone is using this fork: https://github.com/temporary-audacity/audacity

for more context please see this exact comment: https://github.com/temporary-audacity/audacity/issues/48#iss...

TLDR: he’s taking a day off the internet after him and his closed ones getting thousands personal threats over phone, e-mail, etc. for not choosing “Sneedacity” name for the fork

It's a shame the fork doesn't use better commit messages than they do.

For example, "Fixes" is the entire commit message for https://github.com/temporary-audacity/audacity/commit/d9f30b...

Commit messages like these do not inspire a lot of confidence. It would be a lot better (and easier to compare the original and the fork) if the commit message was something like "[Remove-Tracking] Remove SentryHelper.h and sentry ADD_EXCEPTION_CONTEXT usage"