2 ms·

I don't consider things like crash logs and debug stuff to be telemetry. This can easily be dealt with by a popup saying "want to upload the crash log?". It can

by ItsBob 2y ago

I don't consider things like crash logs and debug stuff to be telemetry. This can easily be dealt with by a popup saying "want to upload the crash log?". It can just be a text file with a bunch of data. I'm fine with that. Telemetry to me is knowing what I'm doing, like clicking a button, using a feature etc. They record that shit! Also, sending data about my websites back to the mothership so they can sell ads (or sell to ad companies... same thing). That's what I mean when I talk about telemetry.

bossyTeacher 2y ago
Fairs. But logging and similar is a type of telemetry. It is worth being clear about this stuff. And surely, you don't want to send logs only when your software crashes (which seems to be your proposal) as it might never crash. Not all software bugs lead to crashes. Doesn't mean they don't need investigation.
- ItsBob 2y ago
  > Doesn't mean they don't need investigation. True. But there was a time when we managed to program software and not send every keystroke back to the mothership. It's possible to have a daily/weekly/monthly popup that says "We've detected a few bugs over the last week, can we send the reports to the mothership?" It's as simple as zipping the text files and sending them to an API endpoint. I have no issue with this. Hell, you could even make it automatic where I can check a box that says "Automatically send weekly crash reports". I have a massive issue with the devs thinking that it's ok to send telemetry back about every single thing I do in the software I've installed on MY computer so that they can "improve my experience" or whatever bullshit they use to justify it. It's time for that to stop.