zlacker

>>gorman+(OP)
" Modern cars regularly send basic data about vehicle components, their safety status and service schedules to car manufacturers, and mobile phones work in very similar ways." -Google

This is a beautiful quote because it is an example of one industry's bad behavior leading to another industry's bad behavior, upon which the first industry then users the second's similarity to justify themselves. Cars only started doing this because phones made it normal. It's wrong in both cases.

It's similar to when Apple defended it's 30% store cut by claiming it's an "industry standard"... specifically, an industry standard that Apple established.

>>ocdtre+e3
I disagree that telemetry is inherently bad. As product engineers, telemetry is often our only visibility into whether or not a system is functioning healthily. How else can you detect difficult-to-spot bugs in production?

>>wmiche+Jn
As a software engineer I disagree. You are saying that you want to collect my personal information so you can fix your bugs. I don't see it being a valuable trade. I'll just find someone who can fix their bugs without tracking me.

>>kuratk+vs
Personal information is a bit nebulous. Do we consider the list of function calls in a stack trace "personal information"?

>>babypu+Iy
If I sent the stack trace to you, no. Otherwise, yes. It's my stack trace after all.

(Perhaps "private" not "personal" is a better term here, but stack traces can expose personal information too, if they include details about function arguments.)