Making Go telemetry opt-in is a mistake

Re:Making Go telemetry opt-in is a mistake by aatd86 on Sunday February 26, 2023 @08:40AM (#34945449)

They should simply allow for people to pick their default at installation. (so at download)

Even better if the go tool were to have a `go update` with a `telemetry-off` flag or something. (and possibly a prompt to remind people otherwise they will complain again)

Problem solved.

[ Parent | on HN ]

Re:Making Go telemetry opt-in is a mistake by jonhohle on Sunday February 26, 2023 @08:56AM (#34945561)

`telemetry-on` flag. Sending data to third parties should _never_ be implicit or the default. Every PM, marketer, and mid-level manager needs to be firmly reminded that this is grossly invasive, user-hostile, impolite, and creepy.

Without an explicit agreement, it could even run afoul of wiretapping laws (unresolved in courts, as far as I’m aware).

[ Parent | on HN ]

Re:Making Go telemetry opt-in is a mistake by majorhelmet on Sunday February 26, 2023 @11:47AM (#34946950)

I still think it depends on the telemetry itself. Companies knowing my location at all times? Disgusting and creepy. Company knowing I ran `go help` 200x as opposed to running `go build` 10x is fine imho.

[ Parent | on HN ]

Re:Making Go telemetry opt-in is a mistake by aatd86 on Sunday February 26, 2023 @01:49PM (#34948156)

It depends on the previously installed default.

When you 'go upgrade' your compiler, if telemetry was off it should stay off. No need to further specify in most cases.

If telemetry was on, you might want to turn it off, however.

[ Parent | on HN ]