Thanks for engaging. I still don't see Google Analytics referenced. Second paragraph reproduced below.
> Since Go 1.13, the go command by default downloads and authenticates modules using the Go module mirror and Go checksum database. See proxy.golang.org/privacy for privacy information about these services and the go command documentation for configuration details including how to disable the use of these servers or use different ones. If you depend on non-public modules, see the documentation for configuring your environment.
Nothing about GA. Of course, or naturally as you wrote, they will have server logs. I can't imagine anyone in good faith arguing they should not have server logs and those that do can host their own proxy.
Not sure where you're getting GA from? This doesn't really have anything to do with GA, as far as I know.
> I can't imagine anyone in good faith arguing they should not have server logs.
???
That seems like a really, really strange take to me. "Server logs" is just one way of capturing usage data. GA (as you mentioned above) would be another, though I don't think that's in play here.
The point being, usage data is available to Google. Whether they use it (or not), now or in the future, is unknown to me.
And yep, the people who care can disable it. aka opt out
> elondaits: For anyone wondering: Homebrew sends data to Google Analytics...
> aliqot: Go does this too :/
> sneak: No, it does not.
> akerl_ 1: yes, it does: <<link>>
> sethammons: (summary) I don't see it (GA usage) at <<link>>
> akerl_1: (summary) see paragraph 2
> sethammons: (summary) no GA stuff still
> akerl_1: (summary) wait, why are we talking GA?
The thread started with GA, and I though you were saying that Go uses GA.
Given that Homebrew is using GA basically as a raw database / dashboard, the distinction between “google” and “google analytics” feels pointless here.
The thing that makes GA worse for your privacy than other 3rd party datastores is the linking/inferences because of its shared nature. If you visit 100 sites that use GA for tracking, Google (and to an extent, those 100 site operators) are benefitting from the joining of your browsing history across all the sites.
By contrast, Homebrew is submitted logs to GA with a custom UUID not shared by any other application / requests / browsing that you do, without your IP address, and without any metadata that would link your Homebrew activity to other non-Homebrew activity. They needed a place to send metrics, and GA is providing them the data storage and visualization layers.
If I wrote a FUSE filesystem called “GAFS”, that stored arbitrary encrypted files as GA metrics using their API, I’d technically be using GA but it would be weird to file issues about the privacy impact of having GA code in my CLI tool.
A super short summary is that when you install Go modules, by default it'll grab them via a Google controlled proxy solution.
Naturally this means your IP addresses, exact modules your projects use, (etc) are all information available to Google.