tenacity-legacy

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"

he started a poll to choose a name for the fork and “Sneedacity” was given as an option, purely for jokes 4chan folks voted for the name after refusing to accept the name (since the the fork had a serious intent), the folks started to threaten him and his family for what followed and author’s comment, see his exact comment: https://github.com/temporary-audacity/audacity/issues/48#iss...

The fork of Audacity due to some questionable changes[1] is here: https://github.com/temporary-audacity/audacity. It already has 2k stars. Telemetry for Audacity: https://github.com/audacity/audacity/pull/835 The issue about the Privacy Policy (related to the above): https://github.com/audacity/audacity/issues/1213 [1] Description of the fork: Audacity Fork without any Sentry Telemetry or Crash Reporting.

> So, without GPL, how would Oracle render RedHat useless with telemetry? I cannot understand your question. > And why didn't it prevent the Audacity drama? It does. See https://github.com/temporary-audacity/audacity

It doesn't help that the maintainer is already mishandling basic stuff like naming the repo: https://github.com/temporary-audacity/audacity/issues/33. If the maintainer had waited out the initial flurry of attention, they probably could have chosen the name they wanted without much drama at all. Instead, they overreacted, deleted the first thread, and then immediately started editing and deleting user comments in the second. Ouch.

They're doing a vote for the new name. https://mobile.twitter.com/cookiengineer/status/141211479074... Edit: non-dead link https://github.com/temporary-audacity/audacity/issues/33

Sneedacity seems popular! https://github.com/cookiengineer/audacity/issues/18

Fork is already here: https://github.com/cookiengineer/audacity

Link: https://github.com/cookiengineer/audacity OK, there are more forks! This is one of the first ones i've found that reverts telemetry. If anyone has a more reliable one, please share :)

Hey, thanks for the hint :) I thought I amended those changes to the latest commit, but I seem to have forgotten to push those fixes. Originally I just injected the macro via command line as it didn't do anything when reporting was disabled. Can you please confirm that your HEAD contains the ":bug: Fixes" commit? [1] - I'll upload the built Arch package to the GitHub releases as soon as it's built again. I was using the "audacity-git" [2] AUR package's PKGBUILD file (replaced repo URL with my one) to generate my package and it seemed to work without issues with those fixes applied. There was also a "pthread_cleanup_pop(1)" patch in the PKGBUILD for the alsa library which I wondered about why it hasn't been pull requested upstream...but no idea what's up with that tbh. [1] https://github.com/cookiengineer/audacity/commit/d9f30b2b729... [2]

I've forked the codebase and removed most of the code related to networking, crash reports or sentry telemetry. While I have been cautious and was trying to make sure that not any code could run by mistake (or false environment variable / ifdef checks down the line), I have to say that The Muse Group's intent seem to have been clearly that the code can be built without any of the tracking. All networking related features seem to have been optional, and could be disabled via environment variables like `HAS_NETWORKING` or `HAS_SENTRY_REPORTING` etc. I've detailed this more in my comment in the GitHub repository's issue [1] to make sure others will read about it, too. Personally I think this is a classical miscommunication error, and it seems as the intent of Muse Group was to be as legally compliant as possible. Of course, a dialog where en