As someone who's worked at a mobile app company, crash reports were described to me repeatedly as "I was blind but now I see". Is it reasonable to expect Audac

As someone who's worked at a mobile app company, crash reports were described to me repeatedly as "I was blind but now I see". Is it reasonable to expect Audacity developers to just ask all of their users "Hey, how are things? Are things crashing? How and why?" I'm not sure if you've ever tried to diagnose a user's crashing issues, but, especially with non-technical users, you're likely to get responses like "A dialog popped up but I closed it, I don't remember what it said", or "I wasn't doing anything and it just crashed out of nowhere". Automatic crash reporting is like night and day; sometimes, you can even find and fix problems before your users get a chance to report the crash (if they even bother to do so, which most don't). > If Audacity were to ask before sending data, a good chunk of people wouldn't be upset. But it doesn't, so here we are. From the pull request: https://github.com/audacity/audacity/pull/835 https://github.com/audacity/audacity/pull/835 > Just to reiterate, telemetry is completely optional and disabled by default. We will try to make it as clear as possible exactly what data is collected if the user chooses to opt-in and enable telemetry. We will consider adding the fine-grained controls that some of you have asked for. In other words, Audacity is asking before sending data and people are upset regardless, apparently due to just general ignorance about the situation thanks to some people blowing it out of proportion and describing it inaccurately.