cli

Hm. I assumed that the "telemetry" they were talking about was on their own servers (measuring uploads, downloads, etc.) but given that it was introduced after the Microsoft acquisition, is this telemetry actually client-side, like the telemetry[1] they put in the .NET Core dev tools? [1] https://github.com/dotnet/cli/issues/3093

The linked thread discusses the telemetry and if you follow it through telemetry is now off by default, opt-in only. https://github.com/dotnet/cli/issues/10816

My only beef right now with Microsoft is their insistence on having creepy telemetry in everything. As someone _very_ interested in F#, I encountered this recently with both Visual Studio Code and .NET Core. https://github.com/dotnet/cli/issues/3093

> MS now is kind to its developers As long as you like telemetry: https://github.com/dotnet/cli/issues/3093

They have certainly changed – the .NET installer used to ask if you wouldn't mind participating in their product improvement program by sending data to Microsoft (defaulting to disabled by default), but now .NET Core will send your data to Microsoft by default without asking: https://github.com/dotnet/cli/issues/3093 The data is supposedly anonymized, except sometimes (according to comments on above-mentioned issue) when it accidentally isn't. You can also disable it, except when the disabling mechanism is accidentally broken.

Hey folks, don't forget that these guys still do this: https://github.com/dotnet/cli/issues/3093 https://github.com/dotnet/cli/issues/10497

One reason might be that the tools have telemetry (i.e., automatically gathering and sending data about your system and your use of it to Microsoft) enabled by default[1], which is unexpected and off-putting to people in the free software world. It seems to reflect a very different attitude to some fundamental cultural values. According to the comments on the issue tracker, it was supposed to be OK because it was anonymized – but oops, there was a bug, so it wasn't totally anonymized. But it's OK because you can disable it if you happen to know about it – but oops, the disabling mechanism had a bug. Things that are important to many free software users are not important to Microsoft. I was excited about .NET Core until I became aware of this stark misalignment of goals and priorities. [1] https://github.com/dotnet/cli/issues/3093

and their response is even worst: https://github.com/dotnet/cli/issues/10497#issuecomment-4494... Sadly, I thought they would have fixed it and not ignore it.

Also stuff like this: https://github.com/dotnet/cli/issues/3093#issuecomment-44343... Trust, is an issue.

It's just a shame they felt they had to put in the sneaky telemetry. https://github.com/dotnet/cli/issues/3093

When they’re not screwing it up: https://github.com/dotnet/cli/issues/3093#issuecomment-44343... I suggest anyone interested reads the entire thread.

Names.. Satya Nadella is directly responsible here. There has been no response from him on petitions about it. Google the various sources: Ben Evans is responsible for enforcing the state of affairs on .Net core at least. https://github.com/dotnet/cli/issues/3093 Joey Ailleo, Powershell PM said this https://news.ycombinator.com/item?id=18629942 "I'm a huge privacy advocate, but telemetry doesn't have to be a dirty word. With PowerShell Core, we went through an RFC process to define our telemetry goals and implementation[1], we publish our data to a public dashboard[2], and all of the telemetry source code is out there in the open[3]. Our telemetry enables to help drive prioritization and decisions around platform/OS usage, and disabling it as simple as setting an environment variable[4]." That's basically MSFT policy: 1. Telemetry is good

Does this justify hashing user identification for later correlation with other products? https://github.com/dotnet/cli/blob/b45f1fb439b36872c249b07f1...