News for hackers. Stuff that matters.
Re:Telemetry in the Go Toolchain by cube2222 on Wednesday February 08, 2023 @02:58PM (#34713978)
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 don't really get any kind of sensible sample if you only do it opt-in. Additionally, this ship has long sailed, everybody does opt-out.

What I do think however, is that it should very clearly notify the user of this, and give them an easy way to disable it. Like in OctoSQL[1] (disclaimer: which I'm the author of) which prompts you on first run and shows explicitly how to disable it.

All things considered, this is an open source project, so you're free to maintain a fork without telemetry. The Go toolchain also uses the Google-hosted module proxy by default, which really is a bit like telemetry already.

[0]: https://news.ycombinator.com/item?id=34707583

[1]: https://asciinema.org/a/eWQsyXQKi1fmithyTekAD5fWS

Re:Telemetry in the Go Toolchain by marginalia_nu on Wednesday February 08, 2023 @03:09PM (#34714166)
> The idea of telemetry is being able to prioritize the work that will be most widely useful.

It does sort of hinge on the highly suspect assumption that usefulness is correlated with use. An obvious counter-example to this is something like a fire-extinguisher, which will in the ideal case just sit on a wall until it's use-by date passes and then it's discarded having never been used; or on the flip side, an incredibly byzantine workflow that could be reduced to something much simpler will appear important and useful.

Even without these edge cases, interpreting statistics is really hard. Like people with PhDs who have studied these things for years still get them wrong all the time.

What ends up happening more often than not is it's used as a tool to quiet the critics when pushing through unpopular changes.

Re:Telemetry in the Go Toolchain by cube2222 on Wednesday February 08, 2023 @03:22PM (#34714391)
All this boils down to "an unskilled engineer will misinterpret data even if they have it". I'll assume the Go team knows what they're doing, based on their track record so far.

There's a lot of very simple questions you can answer very reliably, too, like "what proportion of the users are still using a certain compatibility flag".

Re:Telemetry in the Go Toolchain by marginalia_nu on Wednesday February 08, 2023 @03:27PM (#34714480)
My point is that scientists whose job is to interpret data and construct experiments gets this wrong on a regular basis, despite years of training in constructing experiments and interpreting data, despite peer review, despite staking their career and reputation on not making these kinds of mistakes. They still happen! A lot!

Interpreting data is very hard.

Re:Telemetry in the Go Toolchain by masklinn on Wednesday February 08, 2023 @04:44PM (#34715715)
> I'll assume the Go team knows what they're doing, based on their track record so far.

Funny, I’d assume the exact opposite. After all much of the understanding of privacy and statistics at scale was developed after 1980.

Re:Telemetry in the Go Toolchain by philosopher1234 on Wednesday February 08, 2023 @08:14PM (#34718360)
Normally Hacker News is ruthless with stupid comments like this, but some sort of unexamined feelings of inadequacy make Go devs a fair target. I hate this attitude.
Re:Telemetry in the Go Toolchain by remram on Wednesday February 08, 2023 @08:27PM (#34718475)
Go is actually well known for dubious choices they reverted later, like not using libc, their weird major version scheme, or the absence of generics. There's a good record of charging ahead against the popular wisdom and being proven wrong.
Re:Telemetry in the Go Toolchain by nine_k on Wednesday February 08, 2023 @03:30PM (#34714516)
Most software features are not like fire extinguishers.

More than that, the interesting stats may be not even around user-visible features, but around internal mechanisms, like some cache hit rate, or how often is some branch in the compiler invoked.

As long as stats are clearly inspectable, reasonably anonymized, and are opt-out, I'd be fine with sending them.

Re:Telemetry in the Go Toolchain by marginalia_nu on Wednesday February 08, 2023 @03:40PM (#34714696)
The features that are like fire extinguishers are the ones most likely to be unjustly removed with the rationale of looking at telemetry.

See for example Mozilla's bizarre decision to remove the ability to change the override the character encoding of a webpage with some half-baked detector.

Re:Telemetry in the Go Toolchain by philosopher1234 on Wednesday February 08, 2023 @07:53PM (#34718169)
We cant solve this problem by carving out our eyes. We must adapt to having data about the world.
Re:Telemetry in the Go Toolchain by stonogo on Wednesday February 08, 2023 @09:09PM (#34718862)
Nobody wants you to carve out your eyes. They want you to stop shoving eyes into everything you touch.

Meanwhile, I'll decide what I must or must not adapt to, thank you.

Re:Telemetry in the Go Toolchain by philosopher1234 on Thursday February 09, 2023 @12:19AM (#34720068)
Read more carefully
Re:Telemetry in the Go Toolchain by stonogo on Thursday February 09, 2023 @02:49AM (#34720936)
Write more clearly
Re:Telemetry in the Go Toolchain by philosopher1234 on Thursday February 09, 2023 @11:03AM (#34726024)
Wouldn’t have mattered if I did
Re:Telemetry in the Go Toolchain by simoncion on Thursday February 09, 2023 @05:29AM (#34722000)
If folks were using just their eyes, they'd be calling users in to watch them interact with the software, calling users up to perform user surveys, doing all sorts of live-user testing.

But, that costs money: folks don't generally like to do surveys for free, don't like to come to your site (or have you come to theirs) for free, don't like to participate in tests for free... and the caliber of person who can design and orchestrate all that is _notably_ expensive.

So, companies have discovered that it's far, far cheaper to shove remote eyes into their products. No need to schedule user observation sessions, pay for transportation and participation, have to bother with hiring people who are capable of coming up with a good set of questions and scenarios to walk through.

Re:Telemetry in the Go Toolchain by pmontra on Monday February 13, 2023 @08:24AM (#34773055)
Except that those remote eyes don't look at what a person would look at. They know if a feature was used but they cannot see the frustration on the face of a user when some feature is missing or does not work as expected or is hard to find.
Re:Telemetry in the Go Toolchain by bitwize on Wednesday February 08, 2023 @04:15PM (#34715286)
There are essential, fire-extinguisher-like features. The canonical example is the joke about backup software: if it were developed according to today's standard of telemetry-driven engagement analytics, the restore from backup functionality would be removed because it's used so infrequently.

This actually happens sometimes: when developing the demo ".kkrieger", a first-person 3D shooter in 96 KiB, demogroup theprodukkt tried to shrink it down to get it under the 96 KiB wire. One of the tricks they used was using a profiler to identify code sections that were never reached and could be removed. One of the sections they removed was the handler for the up arrow key in the main menu, simply because the test player never pressed up in the menu.

If you think that Google or another large software organization won't misuse telemetry by cutting or neglecting important but infrequently used functionality to hit some KPI... have you ever worked in a large software organization?

All stats can be deanonymized. The more data you make available, the more you identify yourself. I do not need software I use stealthily tying up bandwidth by "phoning home" with data about me. It is simultaneously betrayal and resource theft. If I wanted to contribute to the improvement of the software, I'd file a bug report.

Re:Telemetry in the Go Toolchain by nine_k on Wednesday February 08, 2023 @05:36PM (#34716538)
I think your view of the ways usage stats are used is a bit simplistic. Not everyone remove "underused" features without giving some consideration, even in big corporations.

But since you clearly don't like telemetry, you should have a way to reliably switch it off. Here we are on the same page: there must be a well-documented and easy way to switch any telemetry off.

Re:Telemetry in the Go Toolchain by bitwize on Wednesday February 08, 2023 @06:19PM (#34717103)
If telemetry is on by default, the vendor obviously wants you to have telemetry on. They are incentivized to make switching it off as difficult as possible, and even pull tricks like turning it back on after a delay of 7 or 30 days or so.

Telemetry should be opt-in, if it's provided at all.

Re:Telemetry in the Go Toolchain by BonoboIO on Wednesday February 08, 2023 @05:27PM (#34716408)
„ Most software features are not like fire extinguishers. „

Amen

Sometimes some pretty niche feature, that is used by one individual that is loud, gets more attention than a feature, used by thousands or millions that are just silent users.

Re:Telemetry in the Go Toolchain by BonoboIO on Wednesday February 08, 2023 @06:59PM (#34717614)
Really, a downvote …
Re:Telemetry in the Go Toolchain by saurik on Wednesday February 08, 2023 @03:13PM (#34714230)
The argument for this being opt-in isn't about "it works better", it is about it being ethically correct. There are a ton of things that "don't work" unless you do something unethical: that doesn't mean they are OK, it doesn't mean they should be tolerated, and it doesn't mean the people who do them--and, at the end of the day, it is people who make these decisions: there is a human being who refused to say "no" and whose name we might even be able to find out--shouldn't be judged by their peers for doing these things... and that is all true even if it is (currently) legal for them to do it!!
Re:Telemetry in the Go Toolchain by cube2222 on Wednesday February 08, 2023 @03:25PM (#34714447)
You're framing this as though the "ethical" choice were obvious, or that there was a person who "knew this was the ethical thing to do, but turned a blind eye".

I disagree, I think it's a very contested topic, with lots of discussion whenever it's raised here, with either side possibly being a vocal minority.

Re:Telemetry in the Go Toolchain by atahanacar on Wednesday February 08, 2023 @03:47PM (#34714841)
Anyone who can't see the ethical problem with opt-out telemetry should never be put in a place to make any ethical decisions.
Re:Telemetry in the Go Toolchain by JohnFen on Wednesday February 08, 2023 @04:18PM (#34715333)
I agree that opt-out is a Bad Thing, but I disagree with this stance. And I think lots of people in the pro-telemetry camp see that there's an ethical issue to be discussed, but they reach a different conclusion. They shouldn't be dismissed so glibly.
Re:Telemetry in the Go Toolchain by atahanacar on Wednesday February 08, 2023 @04:23PM (#34715398)
Reaching a different conclusion is one thing, but not seeing a dilemma is another. One can always argue that invading a person's autonomy might be necessary given the benefits but seeing no issue is just turning a blind eye.
Re:Telemetry in the Go Toolchain by JohnFen on Wednesday February 08, 2023 @04:39PM (#34715638)
In the Golang announcements, it's clear that they completely see and understand the dilemma, and have provided a lengthy explanation of why they decided for opt-out anyway.

I respect that. I don't agree with the decision, but it was made with understanding and thought.

Re:Telemetry in the Go Toolchain by atahanacar on Wednesday February 08, 2023 @05:22PM (#34716315)
I made my original comment misunderstanding what the parent comment meant as "not knowing an ethical problem exists". I also am not talking about this specific decision, but criticizing ethical decision making in the tech industry in general.

In ethics, there is no right or wrong answers (mostly), just right and wrong methodologies. If you go the pragmatic way, you'd argue that the benefits of telemetry are greater than the downsides and implement it. If you go Kant's way, you would already have a maxim (either "never invade privacy" or "prioritize technical benefits regardless of the users" in this case) and act according to that maxim regardless of the situation. If you go the intent way, all that matters is whether your intent for the action is good or bad, in contrast if you go the outcome way, all that matters is the outcome regardless of the intent or the methods.

These are all "valid" ways to discuss an ethical dilemma. However, one must always acknowledge the dilemma. This industry, especially big tech, seems to ignore this quite often, mostly because it's very easy to see people as "just numbers" when you don't see them directly. Don't even get me started on lawmakers who are also ignoring this whole issue. Many standard practices in this industry would be straight up illegal in lots of other areas, especially where there is face-to-face contact.

Re:Telemetry in the Go Toolchain by philosopher1234 on Wednesday February 08, 2023 @03:52PM (#34714915)
This is a very extreme position. It's hard to take you seriously when your comment doesn't have any nuance.
Re:Telemetry in the Go Toolchain by atahanacar on Wednesday February 08, 2023 @04:15PM (#34715278)
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.
Re:Telemetry in the Go Toolchain by philosopher1234 on Wednesday February 08, 2023 @04:25PM (#34715429)
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.
Re:Telemetry in the Go Toolchain by atahanacar on Wednesday February 08, 2023 @04:30PM (#34715492)
Reading your comment again, I can see it now. I misinterpreted "knew this was the ethical thing to do, but turned a blind eye" as "knew there was an ethical problem, but turned a blind eye".

Turns out, my straw man can't read.

Re:Telemetry in the Go Toolchain by philosopher1234 on Wednesday February 08, 2023 @04:40PM (#34715657)
Props to you for saying so publicly! I'm not sure if you're unusually open or if I just found the right words to persuade you, but this is a first for me :)
Re:Telemetry in the Go Toolchain by mort96 on Wednesday February 08, 2023 @06:17PM (#34717084)
Spying on people without their consent is not ethical.
Re:Telemetry in the Go Toolchain by 0x6c6f6c on Wednesday February 08, 2023 @06:34PM (#34717318)
Is it not consent if you tell the user that it's on, how to turn it off, and the user confirms the prompt having decided to not disable telemetry?

Because that's how OP framed it. There is an ethical way to track how your app is used, with user consent.

Re:Telemetry in the Go Toolchain by mort96 on Wednesday February 08, 2023 @06:41PM (#34717406)
Putting text on the screen which would inform the user if the user was to read and comprehend it is not consent, no. (I mean, try to apply that logic to any other situation. You put a post-it note somewhere noticeable which says that you will silently mix some medication into your coworker's lunch unless they write some text on another post-it note placed on the kitchen fridge. When you then notice the absence of that second post-it note, and mix in some medication into their food, is that "consent"?)

Furthermore, looking at the asciinema from OctoSQL, users apparently have to edit their profile files on every single machine they intend to use Go on, then remember to verify that the profile applies and has no typos, make sure to never ever accidentally run the program in a context where environment variables aren't respected (would you remember to always use `sudo -E` if you need to use the tool as another user for example?). The danger seems extremely high that the user would, at some point, accidentally run the command without the env var set, even if they were technically proficient and did their best to opt out.

This is not how consent works.

Re:Telemetry in the Go Toolchain by ragall on Thursday February 09, 2023 @06:14PM (#34733113)
No because consent is required for it to be on in the first place.
Re:Telemetry in the Go Toolchain by badrequest on Wednesday February 08, 2023 @09:25PM (#34718986)
How would you use compiler telemetry to spy on people?
Re:Telemetry in the Go Toolchain by eps on Thursday February 09, 2023 @02:52AM (#34720957)
Working hours, work location, home location, favourite cafes, sick days, vacations, hotels, wealth level. And that's just from IP addresses and timestamps alone, and without cross-referencing with all the data that Google vacuums over other channels.
Re:Telemetry in the Go Toolchain by rogpeppe1 on Thursday February 09, 2023 @04:21AM (#34721528)
That ship has already sailed. The Go tool already by default makes network requests to the Go proxy, which potentially allows everything that you're talking about there. What's significantly different about this telemetry proposal?
Re:Telemetry in the Go Toolchain by mort96 on Thursday February 09, 2023 @04:54AM (#34721774)
A couple things IMO.

First, making network requests when downloading packages is necessary for the tool to function and unavoidable. People who care about this will be using a VPN of some kind. It's just how the Internet works. But telemetry is something the tool author is choosing to add, not something that's necessary due to the architecture of our computing infrastructure.

Second, the Go telemetry would apparently create a unique, persistent user ID. Normal Internet use doesn't, there's just the IP address which is different from location to location, shared by a bunch of people behind the NAT, and can be masked using common tools.

And yeah, I know this is "anonymised"... but if you have one user ID which uses Go sometimes with an IP address from a particular apartment complex land sometimes from a particular office space, finding out which individual that user ID belongs to is trivial.

Re:Telemetry in the Go Toolchain by rogpeppe1 on Friday February 10, 2023 @07:10AM (#34738639)
> First, making network requests when downloading packages is necessary for the tool to function and unavoidable.

It's technically not unavoidable. The Go authors could have made use of the proxy opt-in rather than opt-out, making the tool less usable as a result. A similar argument applies here, I think.

> Second, the Go telemetry would apparently create a unique, persistent user ID

Where did you see this? I scanned through the "Telemetry Design" article reasonably carefully and couldn't find any mention of this concept, and the type definition for the posted JSON (the `Report` type) doesn't seem to include any such user ID.

In the end, ISTM that you're not complaining about something that actually affects your privacy in any way, but just the _idea_ of telemetry. Is that really something worth taking such a hardline stance on?

Re:Telemetry in the Go Toolchain by justinclift on Thursday February 09, 2023 @10:46PM (#34735353)
> The Go tool already by default makes network requests to the Go proxy

Frankly, that crap should be expunged from the Go toolchain as well. :(

Re:Telemetry in the Go Toolchain by ergonaught on Wednesday February 08, 2023 @10:12PM (#34719315)
The ethical choice is obvious.

The distinction is between "What I do with my computer is none of your business unless I choose to make it your business" versus "What I do with my computer is your business unless I choose to not make it your business".

It's insane that we are still having to justify privacy as a default, or that people continue to rationalize away the concerns.

Yeah, maybe if it's opt-in they won't have much telemetry data. Perhaps, in fact, it would not be much better than having no data at all. That will make some things harder. Major bummer. If it was easy to do the right thing, more companies would do it.

Re:Telemetry in the Go Toolchain by eps on Thursday February 09, 2023 @02:46AM (#34720910)
> It's insane that we are still having to justify privacy as a default

Half of the HN is in love with Chrome and nearly all are on Gmail.

The relentless drive towards the erosion of privacy powered by free carrots worked.

There is now a whole generation of people that sees all this as a norm.

Re:Telemetry in the Go Toolchain by Faark on Thursday February 09, 2023 @10:34AM (#34725452)
Any program is opt-in, so you just don't have to use it. Mayor bummer. Assuming data collection is properly disclosed, ofc, but i don't see anyone here arguing against that.

The "there shouldn't be any" argument just seems so entitled with there being such demand / reasons to do so. I applaud everyone trying to find ways to satisfy both sides, as done by the original article.

Re:Telemetry in the Go Toolchain by bheadmaster on Saturday February 11, 2023 @06:26AM (#34751366)
You can't satisfy both sides by completely ignoring one side.

"What I do on my machine is none of your business, unless I decide it's your business" is a strong argument, presented multiple times in multiple places, and I haven't seen any rebuttal by any Go representative.

You can ignore the community and do whatever is good for business, but it's hypocritical to pretend you're a "community-driven" project if you do that.

Re:Telemetry in the Go Toolchain by rcme on Wednesday February 08, 2023 @03:54PM (#34714942)
What is the argument for opt-out telemetry being unethical?
Re:Telemetry in the Go Toolchain by masklinn on Wednesday February 08, 2023 @04:41PM (#34715664)
Because that goes against informed consent.

Opt-out is generally rejected by European privacy laws.

Re:Telemetry in the Go Toolchain by remus on Wednesday February 08, 2023 @05:20PM (#34716287)
> Opt-out is generally rejected by European privacy laws.

...where personal data is involved.

It strikes me that this proposal goes to considerable lengths to avoid collecting anything that could be considered personal data.

Re:Telemetry in the Go Toolchain by IanCal on Wednesday February 08, 2023 @06:00PM (#34716855)
I agree it does do that though for context of others reading the thread personal data is a very broad topic:

https://gdpr.eu/eu-gdpr-personal-data/

You have to be very careful to do it properly.

Re:Telemetry in the Go Toolchain by balena on Wednesday February 08, 2023 @06:02PM (#34716882)
IANAL but European law is nuanced over whether IP addresses are PII. If I'm not mistaken it's been ruled they are for ISPs, rationale being they have enough other data points that once correlated with IP addresses allow to identify individuals. Whether the same applies to Google (I suppose) is definitely not clear to me.
Re:Telemetry in the Go Toolchain by Scaevolus on Wednesday February 08, 2023 @06:17PM (#34717078)
The proposal explicitly says they don't collect IP addresses or _any_ unique identifiers.
Re:Telemetry in the Go Toolchain by gwillen on Wednesday February 08, 2023 @06:27PM (#34717212)
As far as I'm aware/recall, European privacy laws consider any connection back to a telemetry server to count as "collecting" IP addresses, since the telemetry server learns it (even if they pinky swear not to write it down.)
Re:Telemetry in the Go Toolchain by notpushkin on Wednesday February 08, 2023 @07:40PM (#34718023)
Can you sent telemetry data through Tor, though? :thinking:
Re:Telemetry in the Go Toolchain by rcme on Wednesday February 08, 2023 @07:55PM (#34718185)
I think privacy laws only apply to things that “process” PII. Accepting a network connection is not, in and of itself, considered to process PII.
Re:Telemetry in the Go Toolchain by ohgodplsno on Thursday February 09, 2023 @04:11PM (#34731525)
You don't recall perfectly well.

Storing IP addresses in logs means that you are now responsible for them, yes. Drop them out of your logs, and you're perfectly fine.

Re:Telemetry in the Go Toolchain by balena on Wednesday February 08, 2023 @06:42PM (#34717420)
I assumed you need consent to receive PII, full stop. Again IANAL, but I assumed saying you don't do anything at all with the PII you receive doesn't exempt you from anything under GDPR. I may be wrong, though I hope not to be.
Re:Telemetry in the Go Toolchain by cowl on Wednesday February 08, 2023 @07:20PM (#34717820)
They are Court cases that have established that the very fact that a connection is being established constitutes a potential collection of IP adresses and needs to be declares under GDPR. (this was specifically about sites using links to Google Fonts on their websites, this was enough to warrant a GDPR declaration that IP are being collected or the sites needed to remove their Font CDNs and supply them locally). Under the same Rule, Companies will need to ddeclare this usage of Go Compiler in their employee GDPR declaritions.
Re:Telemetry in the Go Toolchain by _ph_ on Wednesday February 08, 2023 @03:57PM (#34715000)
Because it most likely means that people are sending data without their consent. Perhaps I am naive or just very old, but I wouldn't expect a compiler to "phone home" with information about what I do with it. Certainly not without me expressing consent first.

So if you want that information, find a way to ask the user first. If you can give a good and understandable explanation on how the information is useful, the users might give their consent happily.

Re:Telemetry in the Go Toolchain by delusional on Wednesday February 08, 2023 @04:20PM (#34715351)
I don't think it's all telemetry. I suppose telemetry could be designed in a way that preserves the users privacy to an extent that is compatible with their native assumption. I suppose that design also depends on what you're building.

If you're building a website, I think it's fairly reasonable for you to store my IP. That's inside my expected privacy loss when dealing with a remote party. I have to connect to your computer, much like i have to physically walk into a store. I don't mind you remembering that I was there. Running a compiler on the other hand feels more "private" to me somehow. My expectation when using a compiler is that it won't send anything to anyone, because why would it?

In general I think our industry is starved for relevant and foundational ethics research, outside of the FSF at least.

Re:Telemetry in the Go Toolchain by Terretta on Wednesday February 08, 2023 @03:22PM (#34714402)
> What I do think however, is that it should very clearly notify the user of this, and give them an easy way to disable it.

You make a good point.

As a for instance from a popular Mac-based package manager that (unexpectedly for many) defaults to telemetry from your CLI:

`brew analytics off` is not hard to type after installing homebrew, but the installation text doesn't mention that; instead it points to a web page you have to read about how wonderful the analytics are before eventually finding the incantation:

https://docs.brew.sh/Analytics

I wonder how many people care enough to click that link, read all the "analytics are actually good for you" copy, and then change their mind to leave it on. I'm guessing almost zero?

But perhaps most users won't cut and paste the link, where if it just suggested `brew analytics off` many users would type it.

Re:Telemetry in the Go Toolchain by msla on Wednesday February 08, 2023 @03:43PM (#34714758)
> opt-in telemetry doesn't work.

Then don't do telemetry at all.

Google doesn't have a right to data.

Re:Telemetry in the Go Toolchain by geodel on Wednesday February 08, 2023 @04:28PM (#34715467)
Yeah, but they do have right to modify projects that they sponsor as they see fit.
Re:Telemetry in the Go Toolchain by yencabulator on Wednesday February 08, 2023 @06:05PM (#34716918)
At which point they lose the "right" to claim it's a community project...
Re:Telemetry in the Go Toolchain by cwkoss on Wednesday February 08, 2023 @03:46PM (#34714827)
> opt-in telemetry doesn't work

That's too bad. Guess you don't get any telemetry data if you want to develop ethical open software.

The answer isn't to bend your ethics.

If a take a dollar from everyone but it's opt out, that's just theft with extra steps.

If I make it opt in, nobody is going to give me the dollar, but that doesn't make opt out morally justifiable.

Re:Telemetry in the Go Toolchain by philosopher1234 on Wednesday February 08, 2023 @04:42PM (#34715688)
Why is it unethical? People in every day life constantly assume things about one another and take actions that affect one another without asking first, and this is a practical necessity, so if the reason is that "you may not do anything without me tell you its ok" I don't think thats a defensible position.
Re:Telemetry in the Go Toolchain by mh7 on Wednesday February 08, 2023 @03:48PM (#34714854)
Any evidence that telemetry actually works? (i.e makes the program better)
Re:Telemetry in the Go Toolchain by charcircuit on Wednesday February 08, 2023 @08:45PM (#34718665)
Yes, the simplest example is crashes being reported.

Developers can see that a specific crash is being hit by 1% of their userbase and then check the logs to see what went wrong and where the cash happened. The fix is made the program is indeed better.

Re:Telemetry in the Go Toolchain by account42 on Thursday February 09, 2023 @11:30AM (#34726541)
You can let users report crashes. You can even prepare the data for them. You can even provide a wizard that automatically opens on crashes to help upload that data. But you need to obtain informed consent. Sending data behind the user's back without ASKING FIRST is not ok. Stop doing it.
Re:Telemetry in the Go Toolchain by eps on Thursday February 09, 2023 @03:00AM (#34721009)
If it collects actionable data, yes, of course it works.

Crashes, common failures, UI/UX friction points, avarage usage patterns - all can be used to prioritize work to take care of things that have the biggest impact.

Re:Telemetry in the Go Toolchain by mh7 on Friday February 10, 2023 @06:39PM (#34747599)
I asked for actual concrete evidence, not "can be used".

Is there an example of a program that was crap, implemented telemetry and then got better afterwards? (and of course controlled for factors that might have improved the program anyway)

I mean since telemetry advocates are so into how useful data is, surely they must have data on whether telemetry itself works?

Re:Telemetry in the Go Toolchain by omginternets on Wednesday February 08, 2023 @03:54PM (#34714941)
So it sounds like we can't have telemetry?
Re:Telemetry in the Go Toolchain by the_gipsy on Wednesday February 08, 2023 @03:58PM (#34715028)
> this is an open source project, so you're free to maintain a fork without telemetry.

That option is a joke. The real alternative is rust - or any non-corporate platform that isn't gonna pull these kind of stunts.

Re:Telemetry in the Go Toolchain by msla on Wednesday February 08, 2023 @04:04PM (#34715122)
> opt-in telemetry doesn't work.

Opt-out telemetry won't work when people send false data to the servers.

Re:Telemetry in the Go Toolchain by gowld on Wednesday February 08, 2023 @04:04PM (#34715131)
Why does the dev team to optimize a use-case that the user doesn't want optimized?
Re:Telemetry in the Go Toolchain by JohnFen on Wednesday February 08, 2023 @04:15PM (#34715285)
> Additionally, this ship has long sailed, everybody does opt-out.

This is a meaningless point.

Re:Telemetry in the Go Toolchain by wrldos on Wednesday February 08, 2023 @04:56PM (#34715917)
But that's wrong. There is no position for this in a civilised society:

"If we ask everyone is going to say no, so we will steal it unless someone tells us not to"

Re:Telemetry in the Go Toolchain by BonoboIO on Wednesday February 08, 2023 @05:32PM (#34716473)
I think the comparison of telemetry and stealing is pretty harsh.

Is opt-out telemetry unethical ... depends. If you use it in a privacy preserving way no, if you spy on your Users, sell the data for money or advertising obviously it is unethical.

The hard truth is, nobody reads the manual. Opt in telemetry is often a minority, and you then work with niche data for a minority that influences your development in certain ways.

Re:Telemetry in the Go Toolchain by wrldos on Wednesday February 08, 2023 @05:36PM (#34716525)
But is that not the decision of the person who owns the data?
Re:Telemetry in the Go Toolchain by philosopher1234 on Wednesday February 08, 2023 @08:16PM (#34718373)
The world is full of people making decisions for one another. Did you consent to unix files not flushing on every write() call? Its not a meaningful complaint.
Re:Telemetry in the Go Toolchain by JohnFen on Wednesday February 08, 2023 @05:43PM (#34716637)
It really all boils down to meaningful consent.

> if you spy on your Users

In my opinion, any data collection about me or my machines that occurs without my active informed consent is "spying". This is my fundamental problem with opt-out mechanisms. They do not indicate or imply that active consent was obtained.

Re:Telemetry in the Go Toolchain by BonoboIO on Wednesday February 08, 2023 @07:00PM (#34717622)
A Flash screen at installtime that logging is on an you can disable it in the settings.

Would that be enough for you?

Re:Telemetry in the Go Toolchain by simoncion on Thursday February 09, 2023 @05:35AM (#34722038)
Unless a Windows user is installing the software, that screen would be displayed in approximately zero of the cases where a package manager was used to install the software. Similarly, exactly zero widely-used Docker images that contain the software would display this splash screen, as the software would already have been installed.

In short, unless you're a Windows user there are so __very__ many ways to install software that aren't "Go to the project home page, download a generic install binary, run that binary with world-write permissions.". Aside from very small-time projects, I can't think of the last time I used an officially-maintained install script that I got from the project's servers to install something.

Re:Telemetry in the Go Toolchain by JohnFen on Thursday February 09, 2023 @11:34AM (#34726621)
It would be better than nothing, but not really adequate. There are numerous circumstances where such a screen is impossible or impractical, and if every program did this, it would be as good as not doing it because people will react to it like they react to other common warning dialogs -- not really seeing it at all.
Re:Telemetry in the Go Toolchain by lokar on Wednesday February 08, 2023 @06:56PM (#34717578)
That’s not their argument. They say if you ask everyone if it is ok most just ignore your question.
Re:Telemetry in the Go Toolchain by wrldos on Wednesday February 08, 2023 @07:04PM (#34717658)
That's how they presented their argument. It can be presented both ways depending on how you want to promote it.
Re:Telemetry in the Go Toolchain by lokar on Wednesday February 08, 2023 @07:05PM (#34717672)
Not responding is not the same as responding no
Re:Telemetry in the Go Toolchain by account42 on Thursday February 09, 2023 @11:28AM (#34726498)
It is when it comes to giving informed consent.
Re:Telemetry in the Go Toolchain by msla on Wednesday February 08, 2023 @06:31PM (#34717267)
Related, with further discussion:

https://news.ycombinator.com/item?id=34709078

Re:Telemetry in the Go Toolchain by dang on Wednesday February 08, 2023 @06:57PM (#34717583)
(This comment was originally posted to a different thread that we merged here; that's why it now links to the page it's on.)
Re:Telemetry in the Go Toolchain by js8 on Thursday February 09, 2023 @12:40AM (#34720169)
> 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.

Why, in OSS, do you care about the users that do not care? If the users truly care they should buy support, or at least enable telemetry.

If someone complains about feature getting removed - tell them to enable telemetry next time. Maybe people who want so much privacy shouldn't be expecting free support for features they want.

Maybe you're worried about people like your grandma installing Linux. Then this should apply on the distribution level - there should be an opt-in setting for telemetry, that enables it in various programs being distributed (at the discretion of the package maintainers), so that user doesn't have to opt-in individually.

Being opt-in will also make it compliant with EU data privacy laws.

Re:Telemetry in the Go Toolchain by eps on Thursday February 09, 2023 @02:39AM (#34720865)
> they don't care either way

This is not true. You know it and you are being coy about it.

If your "easy way to disable it" was a simple question next to that unexpected notification displayed once in response to a completely unrelated action - "Would you like to keep telemetry on?" - you bet you'd have massive opt out rates. Nobody wants telemetry.

What you have is a gray pattern. The same pattern that caused the EU to clarify its cookie law to require Yes and No choice to be equally accessible. And what you have is "Accept all" and "See details". Except that yours is worse by being a one-time notification.

Re:Telemetry in the Go Toolchain by msla on Thursday February 09, 2023 @09:42AM (#34724610)
Re:Telemetry in the Go Toolchain by account42 on Thursday February 09, 2023 @11:07AM (#34726106)
To anybody complaining that this should be opt-in: opt-in petty doesn't work. The reason for this is that most people don't care, but they don't care either way. They don't allow it when prompted, nor would they report it when not prompted.
Re:Telemetry in the Go Toolchain by msla on Thursday February 09, 2023 @05:06PM (#34732281)
There's a reason it can't be opt-in: Google intends collect information about politically sensitive software and give that information to governments who wish to punish developers.