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
So why does $product need to send telemetry data via google? Why can highly complex software that runs most of the worlds internet infrastructure (linux) work without telemetry? Why is telemetry not opt-in or relies on reports in situation where a bug causes an issue like firefox crash reports? I'd rather have privacy and buggy software then bug free software in exchange for no privacy at all

>>dtx1+Ro
>So why does $product need to send telemetry data via google?

Because Google is responsible for most of the software on said product. Who would be receiving that telemetry data if it wasn't Google?

>Why can highly complex software that runs most of the worlds internet infrastructure (linux) work without telemetry?

First, this is a false premise because it ignores the potential that telemetry could help improve this software but most Linux distros have decided against it for other reasons. Secondly, it ignores that some distros do in fact include telemetry.

>Why is telemetry not opt-in

It probably should be when it comes to something that has potential to invade privacy, but we have to be realistic that practically no one will actively turn on telemetry if it is initially set to off. That drastically decreases the value of the collected data and it basically turns into nothing more than something customer service can tell someone to turn on while trying to troubleshoot a specific issue.

>or relies on reports in situation where a bug causes an issue like firefox crash reports?

Telemetry isn't just about bugs. It is also about guiding future development, knowing what features are used, knowing the workflow for users, etc. It can provide value beyond crash reports.

>I'd rather have privacy and buggy software then bug free software in exchange for no privacy at all

This is completely fair. I would generally agree with you and bet that most HN readers would too. However this is not a binary choice. Not all telemetry is inherently bad. Not all loss of privacy is inherently damaging. This is a complicated issue that will involve compromises and anyone sticking to a complete extreme of it being all bad or all good isn't going to offer anything productive to this conversation.