Did they ever fix that issue from a while back where they started collecting personal data on users?
https://www.engadget.com/audacity-privacy-policy-spyware-accusations-data-collection-210001803.html
There was a Lemmy post with a video about how things have changed, which I even commented on, but I can’t find anymore.
What I remember was that yes they did address most of the concerns. There were some issues still (unrelated to data collection iirc), and there’s one other fork that’s being maintained if you don’t want that
Edit: I think the was the video, I don’t want to watch it again but I’ll link my TLDW if I find it: https://m.youtube.com/watch?v=QfmDn1IaDmY
That is the real question. Would like to recommend the program to people again.
Tenacity is a fork designed to address those concerns, and it is mostly beyond fork growing pains at this point
Oh very cool. Thanks a lot.
Growing pains?
Tearing branding and telemetry and build deployment stuff and crap out of forked software is a lot of work that takes some time
I see. Makes sense now.
The oss community forked it into ’ tenacity’ after audacity went into spyware mode
IKR. Why are we even covering news about audacity releases anymore?
Wait what information does audacity collect when your using it?
please use Tenacity
Is there a fork of MuseScore too (the same devs, I think)?
I am not sure, would you post the repo for me, please?
nice :)
deleted by creator
please use Tenacity
I’m still using 2.3.3 as 3.3.3 won’t save project files on Google Drive. As a radio station, that’s kinda important for creating sponsor messages etc.
Will check out Tenacity.
Couldn’t you just setup a local folder with syncing to drive enabled, and then save to that folder?
I don’t work with music at all, so most of this update doesn’t mean much to me. However, it’s nice to see the export window was improved—I want my single-click behavior, damn it.
The telemetry is limited to update-checking and error reports. Distributions will disable update-checking because they already handle updating Audacity. Error reports need to be manually submitted. It’s possible that most distributions just disable networking altogether when building Audacity, if it even exists in their repositories at all. Fedora’s package is waaay out of date. Arch disables networking altogether.
Audacity has still instituted a CLA. This is quite worrying. But nothing has happened yet.
A CLA isn’t worrying and in of itself. Not all CLAs are made equal. No idea about Audacity’s specifically.
I should have specified that the Audacity CLA allowed Muse Group to relicense Audacity from GPLv2 to GPLv3. Yes, I agree with you that not all CLAs are bad. While you keep the copyright to all your contributions, because the copyright is assigned to them (? I’m not actually sure about this), they can relicense it. The CLA agreement.
You grant MUSECY SM LTD, an affiliate of MuseScore and Ultimate Guitar, (“Company”) the ability to use the Contributions in any way. You hereby grant to Company , a perpetual, non-exclusive, worldwide, fully paid-up, royalty free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute your Contribution and such derivative works.
There was quite a lot of confusion and outrage about this at the time, so I can’t recall whether Muse Group specifically said they wanted to include Audacity in Apple’s app store or this was given as an example of why the CLA could be beneficial. My rebuttal was this is not a particularly noble cause. There was also the argument that the FSF requires you to sign a CLA for its own projects so it can reserve the right to relicense it if it benefits the project. My rebuttal to this was…well, it’s the FSF. The day the FSF relicenses their software under a non-free license is the day they die.
All in all, I’m not worried yet.
Spyware
just use OcenAudio
