Audacity, telemetry creeping in

"The addition of telemetry comes just days after Audacity was purchased by Muse Group"
Optional \ disabled by default ...ftm, seeing a future similar to ccleaner.

https://betanews.com/2021/05/08/audacity-gains-telemetry/

 

On a side note, try ocenaudio, it's basically Audacity with a more user friendly UI

 

^^^ Audacity works very well here, am anyway only using the basics for cleaning \ editing recorded streams \ downloads. And knowing it so well, would be a pain to switch to anything that looks different :O)

btw, came across this quite interesting and educating post, surely worth testing out if one got 'disturbances' in audio > Solution to Audio glitches
https://www.tenforums.com/sound-aud...how-ensure-general-real-time-performance.html

 

And telemetry is gone.
https://www.ghacks.net/2021/05/16/audacity-drops-plans-to-introduce-telemetry/

Plus, John makes a great point in the comments section.

 

One of the biggest reason software companies get the ire of software users but in this day and age they get caught flat footed. And now must back track typical.

 

Audacity branded 'possible spyware' after controversial privacy policy update betanews.com | July 5, 2021

Popular open source audio editor Audacity has become rather more familiar with controversy recently than it is probably comfortable with. Concerns built up following the software's acquisition by Muse Group and subsequent changes to telemetry and privacy settings. With the latest changes to its privacy policy page, the controversy continues.

Having already faced a fierce backlash and backing down a little in its plans, Audacity now finds itself hit with the label of "possible spyware" by an independent publisher covering open source software. FOSS Post even advises users to uninstall Audacity as soon as possible.

 

^^^ An entry or two in firewall to stop any telemetry.

 

You mean all should download and still support it? They’ll know how many of you download and use it. Then think you all accept their new nasty policy

 

^^^ Good point. And am keeping 3.0.0.

But similar to ccleaner and so many other useful programs\apps, telemetry infestation will only grow at accelerating speed. Someday one is more or less forced to update one's preferred software (bugs, new functionality, security, os compatibility, whatever), then firewall comes to the rescue.

 

Or just use the old version
https://blog.fosshub.com/audacity-old-version-without-data-collection-telemetry/

 

Yep. But why bother. The new owner run this software down the drain.

Audacity Mess Further Muddied by Muse Group's New Licensing Efforts geekreview.com | JUL 15, 2021

 

:O)

"some users have already forked the software into a new project, dubbed (appropriately) Tenacity"

 

I don't need any forks when ocenaudio exists

 

If old version worked well, why bother updating?

Nice find.

 

There is other options as you saw. And you'll be stuck with no security updates, Bug fixes and improvements forwards if you care about that. Not that newer has to be better

 

Thanks, I started using ocenaudio a while earlier than when Audacity started the telemetry BS simply because it has a better UI and is easier to use and does exactly the same things Audacity can do.

https://www.ghacks.net/2014/06/30/ocenaudio-easy-use-audacity-audio-editor-alternative/

 

Audacity says it is 'deeply sorry' for privacy policy fiasco, publishes lengthy update and explanation betanews.com | July 23, 2021


The development team behind Audacity learned the hard way that people do not take kindly to the introduction of telemetry, particularly when communication is poor.

Over the last few months, there has been a very public debacle involving Audacity's proposed changes to its privacy policy. It resulted in the software being branded "possible spyware" and led to explanations, apologies and backtracking. Now the team behind the open source audio editor has published its updated privacy policy along with a lengthy explanation about various elements of it and an apology for the "significant lapse in communication".

In its apology, the Audacity team blames the fact that the privacy policy was prepared as a legal text which resulted in the use of phrasing that was unclear to many people. Learning from this, the developers say: "From now on we will provide context for changes we make to the policy in a user friendly way".

Yep, better explanation/Phrasing on "why we need more" info from yoo

The post concluded by reiterating the apology, and inviting questions to be posted from anyone with concerns.

You can read through the full posting over on GitHub, while the updated privacy policy is available here.