Telemetry tracking coming to an audio editor near you!
Their decision is official.
(Not hot-linking to PR in question on purpose)
> We're closing this PR. We've taken on board 'no Google' and 'no Yandex' and Muse are now looking for a good alternative (thanks to those who recommended other open source solutions by the way). Please understand that this will take a little time to organize and a concrete plan will be published soon - at any rate this week.
@falktx it seems it is disabled by default, opt in optional, and if enabled, only used to gather data to help app development. If that's true, I have no problem with that. Just keep it turned off.
But worth to keep an eye on what changes.
@ilvipero that is fair and some are ok with it, sure.
I am personally against it, I think analytics is the first step for many bad things. What is acceptable today would be unthinkable just a few years ago. All driven by corporations and/or profits, Audacity had no tracking of any kind for its 20 year lifetime.
And anyway a network layer has no place in an offline audio editor.
@falktx I understand and value different point of view. Certainly it was not the best start. First change made to a foss software after it got acquired , was to introduce telemetry. At least it is disabled by default. Good thing is, now audacity got a lot of eyes on it, and if new owners try something sneaky it will most likely result in backlash and possibly a fork.
@falktx @ilvipero yeah, I kept raising the fact to an Audacity team member that an offline audio editor doesn't need any code for networking and that it would be completely out-of-scope, but they won't listen...