Our great sponsors
-
It also seems like the telemetry wasn't even implemented. The Pull Request adding the telemetry was never merged. This PR proposed merging the crsib:telemetry branch to add telemetry to the audacity:master branch. It was closed when the telemetry branch was deleted, on May 24.
-
Hi everyone, I’m going to describe the actions we propose to take to address the concerns raised about PR #835 (opt-in Telemetry using Google and Yandex as 3rd party hosts): We are dropping the telemetry features proposed in PR Basic telemetry for the Audacity #835 Regarding features that require networking, we would like to include error reporting and the ability for Audacity to check for updates (details below) We will self-host all collected data from error reporting and checks for updates, removing any need for Google or Yandex analytics What happened? The creation and subsequent discovery of PR #835 was a bad communication/coordination blunder that caught us completely by surprise. We're very sorry for causing so much alarm. Our intention was to make an initial announcement about our plans to introduce telemetry on the Audacity forum, similar to how we discussed the topic for MuseScore in 2019. In that instance, I think the fact that we introduced the issue openly resulted in a lot less suspicion. What are we proposing now? I have spent the last few days working with the heads of Muse to try and reach a solution that would accommodate the requests of the community as much as possible. Apologies about the delay. These decisions took time to arrive at because - despite my role as the lead on the project - calls on this specific issue are not mine to make. First, it is important to stress that we have absolutely no interest in harvesting or selling personal data and Audacity will always be free and open source. The response to PR #835 has brought about a realisation at Muse that the convenience of using Yandex and Google is at odds with the public perception of trustworthiness, so we will be self-hosting instead. The next item is telemetry. I believe our communication mistake contributed to a lot of misunderstanding about our intentions here. Telemetry is a practical tool that tells us a lot about how an app is performing or underperforming (is this new feature being used a lot? Is this button being discovered? etc.) We assumed that making it opt-in would allay privacy concerns but since this isn't the case, we are dropping it. In the future, we may want to determine if there are any acceptable alternative solutions that could achieve the same goal. Feedback would be appreciated on this point. In the meantime, I will continue user testing, interviewing, reading feedback and conducting surveys to learn more about what our users want. I will happily discuss this in the comments section. Before delving into the specifics, it is important to mention that we have been asked a lot of different questions. For the purposes of not muddying the conversation, I have stuck only to the most pressing issues raised about PR #835. There will be a lot more communication from Muse about its goals in the near future. I will be continually talking about Audacity and discussing what we are working on over the coming weeks and months. Please ask questions here. We're ready to answer. Below is more specific information related to error reporting and update checking. Error reporting We are currently interested in SQLite errors, application crashes, and non-fatal exceptions. If one of these events is detected, a dialog will appear that explains the nature of the problem and offers to send an error report to us, the Audacity developers. This dialog will contain: An option to view the complete error report data before it is sent For crashes and errors, it will send the OS used For crashes it will send CPU data, like number of cores Equally prominent buttons to “send” or “don’t send” this particular error report A checkbox (unchecked by default) offering to remember the user’s decision and do the same for future error reports without asking The decision for future error reports can be changed in Preferences at any time Error reports of course take place over the internet, which naturally allows us to see an IP address. The error report is stored in our self-hosted Sentry database on a server located in the EU. No information will be sent to any third parties unless required by law. Sentry stores crash data and system/hardware specifications. Here is a link to their source code: https://github.com/getsentry/sentry Update checking When the program starts, Audacity will check whether a newer version of the program is available for download. If there is a new version, the user will be shown a dialog to notify them. There will be an option to disable automatic checking This decision can be changed in Preferences at any time Update checking reveals three things: the IP address, the OS version and the Audacity version. We will use a self-hosted geolocation database to determine the country the IP address is located in and nothing more. The raw IP address will not be stored or logged, but we will store and log a non-reversible hash of the IP address to improve the accuracy of the daily statistics. The server is located within the EU to comply with the GDPR. No information will be sent to any third parties unless required by law. Compiling from source and Linux distribution packages The behaviour described above for error reporting and update checking would only apply to official “release” versions of Audacity available from our website or GitHub page. In other builds, the error reporting and update checking code will be excluded by default via CMake options.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
audacity
Discontinued Tenacity is an easy-to-use, privacy-friendly, FLOSS, cross-platform multi-track audio editor/recorder for Windows, MacOS, GNU/Linux and other operating systems. It is developed by a wide group of volunteers. Contributions welcome! [Moved to: https://github.com/tenacityteam/tenacity] (by temporary-audacity)
There's already a fork right now that seems to be the most dominant one. Seems true to Audacity's spirit, too.
-
audacity
Discontinued Tenacity is an easy-to-use, cross-platform multi-track audio editor/recorder for Windows, MacOS, GNU/Linux and other operating systems and is developed by a group of volunteers as an open source software that respects user privacy. [Moved to: https://github.com/tenacityteam/tenacity] (by cookiengineer)
Do you mean this https://github.com/cookiengineer/audacity
