News for hackers. Stuff that matters.
Re:Go claims telemetry objectors arguing in bad faith and vi... by growse on Monday February 13, 2023 @08:37AM (#34773184)
> So, is it time to fork the go codebase and have a telemetry-free version?

Why is maintaining a fork and remembering to use it everywhere easier than just setting an environment variable?

> ... product because "everyone seems to be happy with it... No one turns it off anyway".

How would they know who turns it off?

Re:Go claims telemetry objectors arguing in bad faith and vi... by blibble on Monday February 13, 2023 @08:57AM (#34773391)
20 years ago no software had telemetry (any reporting back was "spyware")

in 20 years from now will I need 700 environment variables, one for nearly every piece of software on my machine?

LS_TELEMETRY=off VI_TELEMETRY=off BASH_TELEMETRY=off CAT_TELEMETRY=off

Re:Go claims telemetry objectors arguing in bad faith and vi... by jeroenhd on Monday February 13, 2023 @09:36AM (#34773864)
You joke, but I already have a couple telemetry env variables in my env file because of various tools using them for opt-outs.

It's infuriating.

Re:Go claims telemetry objectors arguing in bad faith and vi... by jefftk on Monday February 13, 2023 @09:54AM (#34774115)
There's a proposal for DO_NOT_TRACK=1 https://consoledonottrack.com

Unfortunately it's not been widely adopted. My guess is this is running into the same problem that DNT=1 in the browser did, which is that different people mean different things by "tracking" and it's very hard to come to agreement on where to draw the lines.

Re:Go claims telemetry objectors arguing in bad faith and vi... by WhyNotHugo on Monday February 13, 2023 @10:13AM (#34774372)
20 years from now?

Try disabling all telemetry in Firefox.

Re:Go claims telemetry objectors arguing in bad faith and vi... by remram on Monday February 13, 2023 @10:16AM (#34774421)
AdBlock/PrivacyBadger for the shell. What a nightmare.
Re:Go claims telemetry objectors arguing in bad faith and vi... by justinclift on Monday February 13, 2023 @08:59AM (#34773416)
This hypothetical Go fork/distribution (with telemetry disabled by default), should have an option to send bogus telemetry data to the Google servers. :)

So the occasional person that doesn't mind sending data to Google can leave it on, but enabled in that way instead.

Re:Go claims telemetry objectors arguing in bad faith and vi... by growse on Monday February 13, 2023 @09:06AM (#34773497)
Not quite sure what the logic of "I want to use this tool because it provides me value, but I also want to sabotage the development process of this tool" is meant to be.
Re:Go claims telemetry objectors arguing in bad faith and vi... by justinclift on Monday February 13, 2023 @09:12AM (#34773578)
Quite simply to "Stick it to the man".

If this group of dev's are going to violate the privacy of their Community members, they're asking for stuff like this.

Maybe once they realise the telemetry they collect is utterly useless, they'll actually do the right thing and remove it.

Re:Go claims telemetry objectors arguing in bad faith and vi... by bmacho on Monday February 13, 2023 @09:54AM (#34774112)
I luw<3 this tool so I help it to be better *-* :3 =^.^=

Also can work as a general protesting against a harmful trend.

Re:Go claims telemetry objectors arguing in bad faith and vi... by Yizahi on Monday February 13, 2023 @10:41AM (#34774851)
Sabotage of the specifically mass surveillance part of the development.
Re:Go claims telemetry objectors arguing in bad faith and vi... by kgwxd on Monday February 13, 2023 @09:02AM (#34773452)
To answer both questions: because the variables don’t always work.

If the code doesn’t exist, it can’t run. It’s the only way.

At the very least, it should be a compiler compiler flag and all code with telemetry should be in a separate library to make it easy to be sure no mistakes caused it to sneak it’s way in.

Re:Go claims telemetry objectors arguing in bad faith and vi... by sophacles on Monday February 13, 2023 @09:15AM (#34773615)
This argument is nonsense. Everywhere you have to remember to use the non tracking compiler and everywhere you have to remember to set the variable are at best the exact same set. More likely it's actually more places that require remembering to set the variable since various build environments and tools tend to strip out variables in all sorts of places.

It also assumes setting the variable actually works - even without malicious intent, it's an approach that assumes there are never any bugs.

Re:Go claims telemetry objectors arguing in bad faith and vi... by growse on Monday February 13, 2023 @09:28AM (#34773769)
The fork is created out of thin air, and maintained invisibly, for free?
Re:Go claims telemetry objectors arguing in bad faith and vi... by sophacles on Monday February 13, 2023 @09:39AM (#34773905)
We'll have to see the implementation of course, but it shouldn't be a huge effort to replace the telemtry reporting function with `return success`.
Re:Go claims telemetry objectors arguing in bad faith and vi... by ModernMech on Monday February 13, 2023 @02:19PM (#34778774)
The complexity of the patch isn't the issue, it's keeping up-to-date with the upstream code. This can be done but it requires constant work, discipline, and it probably would need funding.

But the worst part is that it sends the message that we as a community will tolerate megacorps injecting telemetry tracking into our compilers, and our response will be not only to stay in their ecosystem, but to do extra work for them to keep us there. That's not the the message I want Google to hear; I want them to hear us tell them where they can take their telemetry and shove it. We do that with our feet.

Re:Go claims telemetry objectors arguing in bad faith and vi... by carapace on Monday February 13, 2023 @09:59AM (#34774186)
> Why is maintaining a fork and remembering to use it everywhere easier than just setting an environment variable?

1) Presumably, you're just deleting a few bits of code here and there.

2) It's not going to stop at one lil ENV var, eh?