Audacity pull request to introduce telemetry - Don't let them get away with it!

[Disappointed Kenny]

Yes, you need pretty graphs to keep clueless business types from fucking your software into the dirt. If an uppity bean counter starts chimping about the money it costs to support XYZ, you need to show them a pretty graph that justifies XYZ in a language they understand. If you don't then they'll start slashing critical features while their fellow retards congratulate them for their business acumen.

I'd wager this is the reason that every single one of your favorite softwares goes to shit suddenly and without warning.

Mild powerlevel: I kept getting pestered to pull an analytics report for one of the websites I was responsible for, or the project would lose its funding. Despite 10 concurrent users on a website per day, I showed them a graph of those 10 users and they were satisfied to give the project its full budget.

Business executives are fucking retarded.

 

[Flabba_Wabba_Jabba_Noonga]

Who the fuck even updates their Audacity? Haven't updated it since 2016 because there's really nothing else that warrants an update?

Any form of telemetry is definitely just going to be sold, there's no other reason why audacity would be using user data for their own software development

 

[Flabba_Wabba_Jabba_Noonga]

What's up with usage statistics anyway?
Has this ever had any practical use at all and improved anything?

At best someone feeds it to a program to make a pretty graph out of it.

Probably monetary gain. Just another means of software on its last legs providing some level of utility. Just install spyware and start data harvesting the people who update it and don't know.

 

[gooseberry-picker]

The annoying things about this PR are them vendoring dependencies and relying on Google. I like that the chimp out is going to make this all optional at build-time now.

I guess on the plus side we can at least be glad that people do give a shit about Audacity.

 

[Flabba_Wabba_Jabba_Noonga]

The annoying things about this PR are them vendoring dependencies and relying on Google. I like that the chimp out is going to make this all optional at build-time now.

I guess on the plus side we can at least be glad that people do give a shit about Audacity.

People give a shit we're they'll fork Audacity and just remove the spyware. The beauty of FOSS.

 

[Kosher Dill]

People give a shit we're they'll fork Audacity and just remove the spyware. The beauty of FOSS.

Serious question: how often does that actually work? LibreOffice is the only example I can think of where people successfully forked a major FOSS project that went bad.

 

[Flabba_Wabba_Jabba_Noonga]

Serious question: how often does that actually work? LibreOffice is the only example I can think of where people successfully forked a major FOSS project that went bad.

If it's on Github, just fork it, go through the code to find spooky spyware elements (it's pretty obvious in a software application about audio), and then remove it, build it again and release it as OpenAudacity or something along those lines. I might even give it a crack myself if I have time.

I think I found the passive statement about it having spyware now

 

[Kosher Dill]

If it's on Github, just fork it

Well yes, I'm not questioning whether it is technically possible. Just if it's realistic to expect people (both users and developers) to migrate in large numbers from a big-name project to a fork, or failing that, for the fork to be maintained long-term.

By pure coincidence, Glimpse (the fork of GIMP that does nothing but change the "offensive" name) closed up shop just today.

A Project On Hiatus | Glimpse

glimpse-editor.org

I suppose Iceweasel held on for a decade, along similar lines.

 

[Flabba_Wabba_Jabba_Noonga]

Well yes, I'm not questioning whether it is technically possible. Just if it's realistic to expect people (both users and developers) to migrate in large numbers from a big-name project to a fork, or failing that, for the fork to be maintained long-term.

By pure coincidence, Glimpse (the fork of GIMP that does nothing but change the "offensive" name) closed up shop just today.

A Project On Hiatus | Glimpse

glimpse-editor.org

I suppose Iceweasel held on for a decade, along similar lines.

I think it depends on how bad it is. If people really aren't happy with how Audacity implements this (and if this sets a precedent for other bad shit down the track), then yes there will be a dedicated fork for it.

Otherwise some autist will just fork it, delete all that shit and then merge new changes and keep the telemetry out.

 

[BootlegPopeye]

Serious question: how often does that actually work? LibreOffice is the only example I can think of where people successfully forked a major FOSS project that went bad.

Part of the reason Libreoffice worked was because the original project that it was forked from had such massive and total defection because it had been a flawed project for several years anyway. Openoffice.org was so long in the tooth and corporately mismanaged that a fork would have been justified earlier than one appeared.

 

[VIPPER?]

just remove the analytics code and build it yourself?

Alternatively, why not just build or find an old version? It's not even like it's a web browser or something for security, isn't Audacity just VirtualDub for .wav files?