Re:Transparent Telemetry for Open-Source Projects
by rogpeppe1 on Thursday February 09, 2023 @07:14AM
(#34722809)
Have you read the articles? How is this in any way violating privacy?
Re:Transparent Telemetry for Open-Source Projects
by deafpolygon on Thursday February 09, 2023 @07:34AM
(#34723034)
Because it's impossible to get telemetry from any source without violating some aspect of the users' privacy.
Re:Transparent Telemetry for Open-Source Projects
by rogpeppe1 on Friday February 10, 2023 @06:57AM
(#34738544)
So you see this as just the same, from a privacy perspective, as the way that the Go tool already dials out to the Go proxy by default? That is, if you're OK with that (I'd assume not, but it is at least existing functionality), you'd see the telemetry proposal as similar?
In other words, I think you object to the Go tool already, so this is really no different?
Go already has some form of telemetry built-in (by way of a google proxy, I suppose) and adding an official one that is opt-out is just going to make me refuse to ever work with it.
Telemetry should always be opt-in, and only opt-in. We have so much issues with telemetry, privacy, and such because the big players and corporations insists opt-out is better (maybe you get more data, but you violate end-users trust as well). Is that really worth it?
There is blow-back and distrust in the industry as a result and it's only going to get worse the more you try to push for opt-out telemetry (or just assuming telemetry should be the default).