3 ms·

Here's an interesting read on the subject of telemetry in Audacity: https://www.reddit.com/r/audacity/comments/of0b4s/breakdown_of_all_data_collected_by_audacit

Here's an interesting read on the subject of telemetry in Audacity: https://www.reddit.com/r/audacity/comments/of0b4s/breakdown_of_all_data_collected_by_audacity/ https://www.reddit.com/r/audacity/comments/of0b4s/breakdown_... Telemetry is used for the kind of boring stuff most devs would expect: reporting on exceptions so that bugs can be investigated. As the thread points out, Audacity is still open-source so you can audit the codebase if you'd like. There's certainly no "spyware" code in there that's logging keystrokes or turning on your webcam. I'm sure anyone who develops software understands why it's useful to get logs when your software catches exceptions.

antisol 5y ago
We could get into a huge and involved debate on the purported merits of telemetry. >I'm sure anyone who develops software understands why it's useful to get logs when your software catches exceptions. For example, if we were to get into such a debate, my first question would be "Why does that have to be an automatic process, happening without the users knowledge or consent?" But that's not really what I'm here for. You won't ever convince me that telemetry is a good idea. And you especially won't convince me that it's necessary. I think it's probably not worth the time that it'd take to have that debate. You will not convince me, and I can't be bothered trying to convince you.