3 ms·
> That is presuming people aren't turning it on because they don't like it, while the reason they aren't turning it on could be they are lazy and don't want to
by anonymousab 4y ago
> That is presuming people aren't turning it on because they don't like it, while the reason they aren't turning it on could be they are lazy and don't want to do any extra work
The solution in these scenarios is to simply ask the user, with no default, whether they want telemetry to be enabled or disabled. To do so in a modal or required dialogue in fresh install and the update in question.
If the telemetry is worth changing defaults to you then IMO it should be worth a bit of friction to introduce it more ethnically.
- cube2222 4y agoI think a lot of users don't actually interact directly with the CLI. Think IDEs, editors, CI/CD. You'd be cutting them out, again skewing the stats heavily.
- anonymousab 4y agoThat's true. I think this would therefore need to be a bit of a breaking change for that tooling - systems that integrate with Go would need to be updated to deal with this prompt. Whether that's showing it to users or autofilling an answer with a --telemetry==x flag, that's up to them and their community. Is that painful? Yes. Would it turn some people away from Go through this kind of friction? Sure. IMO those kinds of costs and pain points should be necessary considerations of adding telemetry. Worth at least a minor version change, and therefore not too crazy that it would cause some annoyance.
- groestl 4y ago> The solution in these scenarios is to simply ask the user, with no default, whether they want telemetry to be enabled or disabled. And this is the way the Debian installer asks for participation in the Debian Popularity Contest. Which is the ethical (and legal) way.