3 ms·
> So, is it time to fork the go codebase and have a telemetry-free version? Or you know, be reasonable and set the GO_DISABLE_TELEMETRY=1 env variable, IF tel
by thiht 4y ago
> So, is it time to fork the go codebase and have a telemetry-free version?
Or you know, be reasonable and set the GO_DISABLE_TELEMETRY=1 env variable, IF telemetry actually ends up being added some day.
I'm not in favor of any kind of telemetry in my devtools but there's no reason to go nuclear at this point.
Honestly the proposal by rsc is even reasonable to me, I'm mostly against it because I have no trust in Google regarding any kind of data, personal or not.
> eventually the idea of opt-out will be completely removed from the product
That's never happened anywhere, and it's entirely illegal.
- sophacles 4y agoGoogle isn't particularly well known for caring about the laws related to privacy. Besides, opt out via env var is a broken idea. It forces me to go through all sorts of dockerfiles, ci config, dev machine scripts, etc to make sure its set. Not to mention the ongoing maintenance of keeping it that way. Id rather just use the go-with-at-least-some-minimal-respect fork and write scripts to verify that's the base docker image, installed golang, etc. It actually seems easier to do that than verify every environment that runs golang has that env var set.
- anon291 4y ago> That's never happened anywhere, and it's entirely illegal Jokes on you... Open source software is provided as is
- bmacho 4y agoThat's my problem too. I have a website, then A LOT of companies know a lot about my users. From their ISP to Microsoft (I host on github) they all know when my users poop, when my users go on vacation, or when my users are cheating their husbands and checking in from someone elses computer. It is so hard to create something, because of the dangers lurking everywhere. I think I need a reasonable creators license.
- remram 4y ago"to the extent permitted by law"