[traceroute66]

> Opt-in telemetry. A very rare sight these days. Glad to see.

Ahem. Cough.

Given Google's ties to Go, of course it was NOT opt-in when originally announced.

After, shall we say, a "lively" discussion on the relevant Github topic[1], it was changed to opt-in. :D

Opt-in is the correct stance.

[1]https://github.com/golang/go/discussions/58409

[frosting1337]

But it is now, and that's good and should be applauded.

[_xiaz]

I don't believe the Go team deciding not to break GDPR law after massive backlash is anything that should be applauded.

[frosting1337]

I'm not really understanding the logic here, but you do you bud.

[euroderf]

I'd bet you dollars to donuts that the Go team originally asked for opt-in and got overruled by suits.

[adonovan]

You have it backwards. The suits are way more comfortable with privacy violation than the Go team.

[euroderf]

You have me backwards cos I had it forwards. I was unclear perhaps.

I meant (a) "someone" (suits?) said let's install telemetry, (b) the Go team said well hey come on let's make it opt-in rather than defaulting to "on", (c) suits said no we just sneak in the default "on" (cos google ebil).

[adonovan]

Well I can assure you that is not what happened. Our team tried to come up with a telemetry design that set a higher bar for privacy preservation than the norms of the industry (including Google), something so safe that it would be acceptable to enable by default. Of course, the community rejected it and that plan died. But the "suits" at Google afford our team enough autonomy to act in the best interests of the Go community.

Google is not quite the monolithic James Bond villainy of your caricature.

[euroderf]

Glad to hear.

FWIW I wasn't suggesting "villainy" so much as "SNAFU". Google's record on privacy in general leaves something to be desired.

[bananapub]

there's infinity things to criticise google for, but "the go team want useful metrics" isn't one of them.

[kjs3]

There's the "If you have nothing to hide..." guy.