Oh very nice… Alternatives?
Guess the company needs quick statistical information and a census to determine the travel direction for the newly acquired project. Can we milk more for support / extra features or more from selling a license / subscription? We cannot ask these questions or they will just make a fork tanking returns on our investment. Seems there are some already ready and willing to do a fork.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
Right now the plan seems to be – have telmetry ON by default, but you should be able to disable telemetry from the options window (once the next version is released). If one of the devs does it properly, it should also have a compilation option –disable-telemetry, so that it’s easy for maintainers to build Audacity without telemetry (but for sure the package downloaded from the audacity website will have it enabled), so there is no need for a fork just yet.
The Audacity team will no longer include telemetry.
The only things that may worry others is the auto-updates (used also for tracking, but can be disabled) and the error reporting (a dialog will ask if you want to send the error log to the devs, it doesn’t do it automatically). But they say it is only set up this way for the release downloaded from their website.
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.