141–150 of 314 posts
Earlier quoted context omitted.
If 0% of your users disable it, that kind of screams there's something wrong with your opt-out mechanism. Is it broken? Hidden? Difficult to do? I mean, with any group of people, there will always be a percentage that will disable it. If the telemetry is popular, that percentage might be very small, but it would be non-zero.
I think you missed the joke.
This week one of my tasks is to figure out how to neutralize some telemetry in one of our apps. We had no idea it was there, we do not want to be sending data. Last week, the parent company decided they didn't want to maintain the telemetry server any longer, and got rid of it. Now the tool has generated thousands of log messages that it can't phone home. And so it must be silenced, since it is cluttering up the logs…
Probably related to[0]. To anybody complaining that this should be opt-in: opt-in telemetry doesn't work. The reason for this is that most people don't care, but they don't care either way. They don't disable it when prompted, nor would they enable it manually. The idea of telemetry is being able to prioritize the work that will be most widely useful. For this you need a good and balanced sample of your users. You do…
> opt-in telemetry doesn't work. Then don't do telemetry at all. Google doesn't have a right to data.
Very much against this. Sure, it sounds naive enough, and can give reasons why. But I have 3,436 items in /usr/bin. What if -every- one of these started doing their own telemetry, their own envvars, etc? If we have to deal with telemetry, then I'd instead hope that there can exist a single telemetry systemwide interface. Not sure how that would be designed or implemented, but would be better than everyone doing their…
> " What if -every- one of these started doing their own telemetry, their own envvars, etc? " What bad thing are you suggesting would happen if they did? Your computer and internet connection can't handle four thousand strings or four thousand HTTP POSTS, or four MB more disk space of telemetry libraries? I bet it can. This isn't a technical problem, it's a control and consent problem.
The information and rate of upload as described seem reasonable. Is the fear from most people that it will be a foot in the door? And a way for Google to collect extra overtime? Note: I think Go is a regressive technology. That would have been great in 1970s. Not today. But that's a different topic. My point is that I tend to be biased very negatively against Go. But here I don't see something wrong.
Earlier quoted context omitted.
Finding the collection of a person's data without consent unethical is not an "extreme position". Since when "consent" or more correctly "autonomy of individual" is called "extreme"? If you did the same thing in my field (medicine), you would lose your license.
I agree, that's not what I think was extreme about your position. I think you've invented straw men in this comment and your previous comment.
Turns out, my straw man can't read.
> To be clear, I am only suggesting that the instrumentation be added to the Go command-line tools written and distributed by the Go team, such as the go command, the Go compiler, gopls, and govulncheck. I am not suggesting that instrumentation be added by the Go compiler to all Go programs in the world: that’s clearly inappropriate."
Well that dispels any lingering thoughts I might have had about ever using golang for anything (not many to be sure). Someone feels the need to assure everyone that they won't be stuffing telemetry code into every binary their compiler produces? Google just wants all the data about everyone everywhere all the time...
https://www.komando.com/security-privacy/ways-google-invades...
Honestly, this may be unpopular with hacker news, but just add your own telemetry. If people don't like it they can turn it off, and telemetry is essential for a good product. Do let people turn it off though please.
> telemetry is essential for a good product No, it isn't, and the idea that is is toxic.
But I'm confident I'll make a better product with telemetry vs without.