There are no โnewsโ, but Iโm worried about this business actually. Iโm in knowledge that post already exists but Iโm not clear at all.
Resuming: Google is trying to add telemetry to Goโs toolchain (such as .NET and Dart/Flutter). It also added the GOPROXY environment variable that uses the Googleโs Go proxy toโฆ Just collect more user data?
Iโm a pretty beginner Go dev, but Iโd like a toolchain without these telemetry or at least some instruction of how to opt out this thing.
Sorry for repost, but I donโt find enough information in any other place. :(
deleted by creator
I searched A LOT about this information and got no information (but misinformation) about. Plus just look at this decision.
What that means? I need to do a
torsocksto every single command I type? (That last is just sarcasm. Please, Iโm not so paranoid (by now))
As long as itโs opt-in (which it is), Iโm not sure I understand the concern. Youโd have to enable it.
Go has been routing module requests through GOPROXY since modules were introduced; itโs where all of the mod version is cached, so any time anyone builds a Go package from source, calls are made to the mother ship. Unless the builder is running their own proxy, which is mostly corps, who care less about this sort of telemetry. There are good, valid reasons for the main Go proxy, but itโs certainly also a valid concern that the Go core dev team is utterly deaf to.
In any case, the only thing thatโs new is the telemetry which, as I mentioned, is opt-in. I donโt see any reason for new concern.
So, that means telemetry is optional? How I ensure is currently active or not? Just wanna an explanation. I (as I said) searched about this thing and got almost nothing :(
itโs where all of the mod version is cached, so any time anyone builds a Go package from source, calls are made to the mother ship.
I donโt understand it at all. Why Iโll need something like that?
Thank you for your response!
Why Iโll need something like that?
IIUC it is mostly to avoid placing huge load on the original package host when people download the same package hundreds of times a day in their CI workflow. It also means that Google can take control over the user experience rather than huge issues coming up every time some smaller host goes down or someone deletes an existing package version.
Overall I doubt that this proxy was added as a source of tracking. And the privacy policy on the service is pretty strict: https://proxy.golang.org/privacy. So even though I am pretty wary of Google overall I think this is actually a fairly reasonable decision by them to have enabled by default.
Thatโs a pretty good explanation about. Care if you reply the source of your information? Iโd wanna keep it as reference <3
Thank you!
I donโt really have a source. It is just me thinking logically about the system and many offhand comments I have read over time. Other than the privacy policy which I have linked.
I donโt know what you mean by โthe source of this conceptโ.
Sorry my english spell is a shees.I corrected my post
deleted by creator
Well, this makes sense to me.
Honestly I wouldnโt be surprised, I donโt know much about Go but based on Googleโs track record it seems like the gameplan is to sell a bunch of user data to third parties and go rich
Lmao Hope youโre not right (I mean, I hope no telemetry is imposed on my favorite programming language). But as you said, Google tracking/survillance history say that people privacy really donโt concerns him
You can always switch to another language later on if anything goes south, since a lot of the thought process is the same behind the scripting ๐ค
Rust is my โalternativeโ. But I see Rust pretty hard (is a system level programming language lol) and differently scoped.
I like some Go characteristics like garbage collection, simpler syntax, crossplatform, 1 second C bindings, and so on.
Do you want a good product? [opt-in] Telemetry is the way to get that.
Is this a joke?





