[0cf8612b2e1e]

The problem is you never know what they will share. Today, they just want to track which buttons get clicked. Tomorrow, maybe some eager PM wants to upload all of my environment variables.

If it can fully run locally on my machine, I do not want it sending anything external.

Lastly, as an abused Firefox user, it seems that telemetry is only ever used to justify removing features I like.

[saintmatthieu]

> it seems that telemetry is only ever used to justify removing features I like

If the removed features are only features you like, then they probably aren't doing things right... The one most relevant purpose for telemetry I see for Audacity is precisely preventing this from happening, meanwhile fostering a more vigorous growth of the repo by cutting off dead branches. Audacity is over 20 years of development of features, some of which we every now and again wonder if they're still used. Not knowing, we try our best maintaining these, which slows down Development, QA and Design in delivering features that are relevant now.

[djur]

The problem with this argument is that there's no reason to believe a slippery slope exists. It's just as easy to go from "no tracking" to "digital colonoscopy" as it is when your starting point is "anonymized crash reporting". Any new release of any software could start spying on you.