3 ms·

I mainly get it straight from golang.org, but this will be able to be disabled via environment variable just like the modules proxy stuff was. https://research.

I mainly get it straight from golang.org, but this will be able to be disabled via environment variable just like the modules proxy stuff was. https://research.swtch.com/telemetry-design#opt-out https://research.swtch.com/telemetry-design#opt-out

sidewndr46 4y ago
Running the command in that just shows me a message of "go: unknown go command variable GOTELEMETRY"
- 4ad 4y ago
  Because this proposal has not yet been implemented.
  - sidewndr46 4y ago
    So is there a way to disable this ahead of time? Or do I have to install the version with telemetry first?
    - mseepgood 4y ago
      Yes, you can set an environment variable at any point in time.
      - rsc 4y ago
        You can also echo GOTELEMETRY=off >> $(go env GOENV)
        chaps 4y ago
        There are tons of cases where the person installing go won't know that telemetry is enabled otherwise. For example, let's say you're at a bootcamp and the go installation instructions from your teacher don't mention telemetry -- how would the person know to disable telemetry? My concerns are around nation state actors, domestic abuse, journalist privacy, lawyer confidentiality and fully believe that this sort of telemetry can and will be abused in someway somehow, eventually, and probably in some obscure fashion. Would be nice if this system threw something to stderr at runtime every. single. time. unless the message was explicitly disabled. Something like: Go telemetrics are enabled! We are collecting {json:object} from your machine for X purposes. If you would like to opt out, run "echo GOTELEMETRY=off >> $(go env GOENV)". To disable this message, "echo GOTELEMETRYWARNING=off >> $(go env GOENV)"
        sidewndr46 4y ago
        If you run your build inside of a docker container, wouldn't it be enabled by default as well? Docker containers do not inherit the environment from the host that I know of.
        chaps 4y ago
        From the description of the implementation, it would only send telemetry data after seven days of being on. So, yes, as long as the docker container is up for that long. I didn't see anything that mentions whether it would communicate to any telemetry server on initialization.

sidewndr46 4y ago

Running the command in that just shows me a message of "go: unknown go command variable GOTELEMETRY"

4ad 4y ago
Because this proposal has not yet been implemented.
- sidewndr46 4y ago
  So is there a way to disable this ahead of time? Or do I have to install the version with telemetry first?
  - mseepgood 4y ago
    Yes, you can set an environment variable at any point in time.
    - rsc 4y ago
      You can also echo GOTELEMETRY=off >> $(go env GOENV)
      - chaps 4y ago
        There are tons of cases where the person installing go won't know that telemetry is enabled otherwise. For example, let's say you're at a bootcamp and the go installation instructions from your teacher don't mention telemetry -- how would the person know to disable telemetry? My concerns are around nation state actors, domestic abuse, journalist privacy, lawyer confidentiality and fully believe that this sort of telemetry can and will be abused in someway somehow, eventually, and probably in some obscure fashion. Would be nice if this system threw something to stderr at runtime every. single. time. unless the message was explicitly disabled. Something like: Go telemetrics are enabled! We are collecting {json:object} from your machine for X purposes. If you would like to opt out, run "echo GOTELEMETRY=off >> $(go env GOENV)". To disable this message, "echo GOTELEMETRYWARNING=off >> $(go env GOENV)"
        sidewndr46 4y ago
        If you run your build inside of a docker container, wouldn't it be enabled by default as well? Docker containers do not inherit the environment from the host that I know of.
        chaps 4y ago
        From the description of the implementation, it would only send telemetry data after seven days of being on. So, yes, as long as the docker container is up for that long. I didn't see anything that mentions whether it would communicate to any telemetry server on initialization.