Curious to hear how this change could harm any customer. Judging by the vitriol and strong language in this thread, there must be some grievous harm telemetry causes that I am not aware of.
Lack of transparency - lack of communication - lack of at the very least an opt-out.
Lack of Transparency: No specific details on what or when they transmit.
Lack of Communication: Didn't tell customers they were putting this in place.
Forcing customers to employ additional network security on a network device if they don't trust what you're doing ... which is hard to do given the lack of transparency and communication.
>there must be some grievous harm telemetry causes that I am not aware of.
What you're not aware of is the same thing the rest of us aren't aware of ... and that is what is actually sent and what triggers that etc.
What is a “crash report”? Is it just a log saying that the machine crashed? Is it a core dump? Is there PII in the logs? Does it expose information that is protected by law? It’s not the fact that there’s telemetry, it’s that it wasn’t communicated well so people can mitigate risks. This shows that there isn’t a culture of paying attention to this sort of thing over business intelligence.
It’s not the fact that there’s telemetry, it’s that it wasn’t communicated well so people can mitigate risks.
I respectfully disagree. It is also the fact that there's telemetry. It is not OK for me to punch you in the face just because I tell you I'm going to do it first. You shouldn't have to mitigate that risk. The risk wouldn't exist if I weren't punching you in the face.
