tl;dr please?
The OP is not happy with the fact collects the telemetry data when you use their .NET tools and demands that they stop.
(I'm almost sure this post will be featured on n-gate.com.)
Microsoft/.Net Foundation added telemetry to the dotnet command line last year
11–20 of 101 posts
Re: Microsoft/.Net Foundation added telemetry to the dotnet command line last year
#12Come on folks, this is printed out on the use of the command and basically any site today does more intrusive telemetry.
I think they should ask people like Yeoman, but I don't think they deserve this much shit for such a small thing.
Re: Microsoft/.Net Foundation added telemetry to the dotnet command line last year
#13Here's what Microsoft have learnt from the telemetry [1].
[1] https://blogs.msdn.microsoft.com/dotnet/2017/07/21/what-weve...
Re: Microsoft/.Net Foundation added telemetry to the dotnet command line last year
#14For reference, they collect[1]: The command being used (for example, "build", "restore") The ExitCode of the command For test projects, the test runner being used The timestamp of invocation The framework used Whether runtime IDs are present in the "runtimes" node The CLI version being used I'm actually OK with this to be honest. Here is the telemetry code itself: https://github.com/dotnet/cli/blob/5a37290f24aba5d35f…
So this is yet another case of someome blowing something completely out of proportions and spending their time working on something completely useless that will never benefit them.
"Out of proportions" for now. Nothing stops them from changing this later, updating the small print saying "oh we changed that" and blaming you for not checking for changes to their EULA regularly.
Re: Microsoft/.Net Foundation added telemetry to the dotnet command line last year
#15For reference, they collect[1]: The command being used (for example, "build", "restore") The ExitCode of the command For test projects, the test runner being used The timestamp of invocation The framework used Whether runtime IDs are present in the "runtimes" node The CLI version being used I'm actually OK with this to be honest. Here is the telemetry code itself: https://github.com/dotnet/cli/blob/5a37290f24aba5d35f…
That's not quite correct. More is collected, but the docs are still being updated. [0]
The other things being collected are:
* Geographical location
* Operating system and version
Re: Microsoft/.Net Foundation added telemetry to the dotnet command line last year
#16Here's what Microsoft have learnt from the telemetry [1]. [1] https://blogs.msdn.microsoft.com/dotnet/2017/07/21/what-weve...
The data is also public, at:
-q.tsv" rel="nofollow">https://dotnetcli.blob.core.windows.net/usagedata/dotnet-cli...
So, the latest would be:
https://dotnetcli.blob.core.windows.net/usagedata/dotnet-cli...
Re: Microsoft/.Net Foundation added telemetry to the dotnet command line last year
#17Ah, these geeks that hallucinate themselves as Will Smith in Enemy of the State. Never gets old. I think in this case the onus is on the paranoid coder with an inflated sense of their own importance to stop MS getting their hands on the super sekret dotnet usage information. And that's easy - it's a setting. (Non) problem solved.
Re: Microsoft/.Net Foundation added telemetry to the dotnet command line last year
#18People remain the same people and companies remain the same companies.
It's in microsofts DNA to build stuff that captures and watches and monitors and logs.
Just because they've started to be more open, won't change the fundamental company attitude and approach to doing things.
Microsoft will simply be bringing more "Microsoftiness" to the open source world. Get used to it, there's more coming cause that's the way they build software.
I would suggest that it is time to rethink some of those outdated assumptions that tools won't spy on you. Microsoft have arrived at the open source party, so open source isn't the same any more, just accept that the world has changed and now it's entirely possible that your open source is logging and watching.
Re: Microsoft/.Net Foundation added telemetry to the dotnet command line last year
#19For reference, they collect[1]: The command being used (for example, "build", "restore") The ExitCode of the command For test projects, the test runner being used The timestamp of invocation The framework used Whether runtime IDs are present in the "runtimes" node The CLI version being used I'm actually OK with this to be honest. Here is the telemetry code itself: https://github.com/dotnet/cli/blob/5a37290f24aba5d35f…
Also, when you run `dotnet restore`, you get the following message: Welcome to .NET Core! --------------------- Learn more about .NET Core @ https://aka.ms/dotnet-docs. Use dotnet --help to see available commands or go to https://aka.ms/dotnet-cli-docs. Telemetry -------------- The .NET Core tools collect usage data in order to improve your experience. The data is anonymous and does not include command-line arguments…
The author must not be used to the new spyware-by-default mentality coming from Microsoft.
Hard to believe, but they used to sell products a while ago and had no telemetry.
If you want to see how it's done properly, look at OmniGroup: their apps have toggleable telemetry and it's off by default.
Re: Microsoft/.Net Foundation added telemetry to the dotnet command line last year
#20For reference, they collect[1]: The command being used (for example, "build", "restore") The ExitCode of the command For test projects, the test runner being used The timestamp of invocation The framework used Whether runtime IDs are present in the "runtimes" node The CLI version being used I'm actually OK with this to be honest. Here is the telemetry code itself: https://github.com/dotnet/cli/blob/5a37290f24aba5d35f…
do you actually inspect every github commit, that this won't change?
It already has. [0]