[HN Gopher] Google's Go may add telemetry that's on by default
___________________________________________________________________
Google's Go may add telemetry that's on by default
Author : mikece
Score : 25 points
Date : 2023-02-10 20:01 UTC (3 hours ago)
(HTM) web link (www.theregister.com)
(TXT) w3m dump (www.theregister.com)
| filereaper wrote:
| This is a nuanced discussion, the linked article may evoke snap
| responses.
|
| I strongly recommend readers to read the GitHub issue discussions
| and Russ Cox's three blog posts.
| nescioquid wrote:
| The issue is Go/Google forcing default-on "transparent"
| telemetry. The _only_ nuance here is that by forcing default-
| on, a) they get more data, and b) they believe few would opt-in
| because of the level of trust Google merits.
|
| If people had no reason to mistrust Google, people would opt
| in. If people would opt-in, they wouldn't bother with
| "transparent telemetry".
|
| Hoist, meet Petard.
| InfamousRece wrote:
| There is lots of tools written in Go these days, so this can
| potentially have wide reaching consequences. Prepare for your
| friendly docker executable to start shoveling telemetry to
| Google.
| patch_cable wrote:
| > To be clear, I am only suggesting that the instrumentation be
| added to the Go command-line tools written and distributed by
| the Go team, such as the go command, the Go compiler, gopls,
| and govulncheck. I am not suggesting that instrumentation be
| added by the Go compiler to all Go programs in the world:
| that's clearly inappropriate.
|
| It doesn't seem like that is the proposal.
___________________________________________________________________
(page generated 2023-02-10 23:02 UTC)