Telemetry just means any data about operations that are sent back to the mothership. Crash logs are just as much telemetry as a click event log. Equating any telemetry=spying is a knee jerk reaction to tech companies abusing telemetry.

Wiki https://en.wikipedia.org/wiki/Telemetry disagrees, note the automatic transmission

> Telemetry is the in situ collection of measurements or other data at remote points and their automatic transmission to receiving equipment (telecommunication) for monitoring

>> Equating any telemetry=spying is a knee jerk reaction to tech companies abusing telemetry.

> Wiki https://en.wikipedia.org/wiki/Telemetry disagrees

It feels like your response fails to address the point colejohnson66 is making. They are saying "some spying is done via telemetry, but not all telemetry is spyware." The automatic nature of it is orthogonal to its spy-ness or user hostility.

Basically, "automatic" here is an antonym to "manual" e.g. user emailing a bug report.

Personally, I consider the following sorts of telemetry "not spyware":

- coarse grained crash report (build version, arch, etc). this is usually a manual prompt on crash, so "semi-automatic telemetry" is how I'd define it

- anonymized metrics/spans. Basically "foo_bar() took 20ms". These are "automatic" in that the collection and transmission happen without user input, but that's orthogonal to whether the user opted in/out.

Fine-grained usage information is a lot more spyware-esque.

Nope, you just pasted the wrong sentence, if you do the quote correctly (his first 2 sentences), then the feeling should go away