audacity VS Sentry

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"

First, sign up for a free account at https://sentry.io. Create a new project and make note of your DSN (Data Source Name).

Using APM tools like NewRelic, Sentry, Datadog, etc to monitor the performance of your application and while you're on it, they can help you identify N+1 queries.

However, ensuring the reliability and performance of your Next.js app is equally crucial. That’s where Sentry comes into play. Combined with Sentry, an industry-leading error monitoring platform, Next.js empowers developers to proactively identify and resolve issues that may arise in their applications. In this article, we’ll explore how to integrate Sentry into your Next.js project for effective error monitoring and performance optimization.

Sentry: Error monitoring for applications, including APIs. Also offers application performance monitoring (APM).

Indeed, webapps are not immune to distribution problems. Wayward and invasive browser extensions are a clear threat, as are 3rd-party dependencies (and their dependencies) loaded at runtime. Which is why companies like https://sentry.io exist. I think the difference is that webapps are "distributable by default" and it takes real work to break this. Versus having local desktop apps which require work to distribute. A potent example of the power of defaults.

Sentry produces nothing of value? You don't value an open source error tracking and performance monitoring platform? https://github.com/getsentry/sentry

> You invent something, and then immediately turn it into a cheap commodity by releasing it for free.

Exactly. A 71-line python script https://github.com/getsentry/sentry/commit/3c2e87573d3bd16f6... was groundbreaking when it came out and the fact that it springboarded into a startup is commendable.

sentry.io: 5

Sentry - Open Source Alternative For Error Tracking

11. Sentry