Earlier quoted context omitted.
> I also never understood the massive hard-on that the technical user-base has against useful telemetry. > it seems that most of them have never worked on an user-facing product If you have worked on user-facing products, then I think you do understand. I think you just don't like the answer. Here it is in a nutshell: In the general case, how do you distinguish 'telemetry' from 'surveillance'? And the answer is you c…
> how do you distinguish 'telemetry' from 'surveillance'? Granularity. Telemetry data can be privacy-respecting (e.g. anonymously aggregated) while still being useful. E.g. "143 people flew from NYC to LA this month" vs. "John Smith flew from NYC to LA at 2:00 pm on Tuesday."
You can do it with cameras and ID plate detection tools, which allows tracking where anyone is at any time.
You can also put magnetic loops into the roads, which just tells you how many drive over a certain area of the road, without any individualized tracking.
Good telemetry is like the magnetic loops. But nowadays very few implementations are that privacy respecting