3 ms·

But it's not aggregated, and the combination of geolocation + os kernel build number + runtime id + osversion + sdkversion could very well be unique. Just take

by 0x0 8y ago

But it's not aggregated, and the combination of geolocation + os kernel build number + runtime id + osversion + sdkversion could very well be unique. Just take a look at some choice lines from one of the .tsv files at https://blogs.msdn.microsoft.com/dotnet/2017/07/21/what-weve-learned-from-net-core-sdk-telemetry/ https://blogs.msdn.microsoft.com/dotnet/2017/07/21/what-weve... : Timestamp Occurences Command Geography OSFamily RuntimeID OSVersion SDKVersion 5/8/2017 12:00:00 AM 3 fable Madagascar Windows win10-x64 10.0.14393 1.0.3 6/8/2017 12:00:00 AM 1 fable Germany Windows win7-x86 6.1.7601 1.0.1 4/11/2017 12:00:00 AM 3 user-secrets Vietnam Windows win10-x64 10.0.14393 1.0.0 5/1/2017 12:00:00 AM 1 user-secrets Thailand Windows win10-x64 10.0.14393 1.0.0-preview2-003131 4/3/2017 12:00:00 AM 1 restore3 Peru Linux debian.8-x64 8 1.0.1 Especially with commands being logged, one slip-up (paste, tabcomplete etc) could end up in public .tsv files for anyone to see.

josteink 8y ago
> Especially with commands being logged, one slip-up (paste, tabcomplete etc) could end up in public .tsv files for anyone to see. That argument can be extended to anything and as such cannot be deemed valid. I could accidentally post AWS secrets as my user-agent in my browser. Does that mean everyone on the internet should be held accountable to GDPR because I might visit them and my user-agent end up in their server-logs? Ofcourse not. Microsoft is clearly showing a reasonable effort w.r.t. limiting what gets logged and how. That should be more than enough to appease any GDPR-concerns. They can't be held accountable for all possible errors or error-modes in the known universe. If anyone here is claiming they should, what they then also claim is that any software handling user-data must be 100% bug-free to be GDPR-compliant. And that's obviously a ludicrous position. Stop the nonsense.
- 0x0 8y ago
  Why not just make the logging opt-in then? Opt-out for non-primary features like sneaky telemetry is not reasonable. There's a difference between not being bug-free, and purposefully implementing a user-hostile feature like this. Please, try to avoid crediting me for absurd arguments that I haven't made.
- partycoder 8y ago
  GDPR aside, this kind of "telemetry" is largely unwelcome.

by 0x0 8y ago

josteink 8y ago

> Especially with commands being logged, one slip-up (paste, tabcomplete etc) could end up in public .tsv files for anyone to see. That argument can be extended to anything and as such cannot be deemed valid. I could accidentally post AWS secrets as my user-agent in my browser. Does that mean everyone on the internet should be held accountable to GDPR because I might visit them and my user-agent end up in their server-logs? Ofcourse not. Microsoft is clearly showing a reasonable effort w.r.t. limiting what gets logged and how. That should be more than enough to appease any GDPR-concerns. They can't be held accountable for all possible errors or error-modes in the known universe. If anyone here is claiming they should, what they then also claim is that any software handling user-data must be 100% bug-free to be GDPR-compliant. And that's obviously a ludicrous position. Stop the nonsense.

0x0 8y ago
Why not just make the logging opt-in then? Opt-out for non-primary features like sneaky telemetry is not reasonable. There's a difference between not being bug-free, and purposefully implementing a user-hostile feature like this. Please, try to avoid crediting me for absurd arguments that I haven't made.
partycoder 8y ago
GDPR aside, this kind of "telemetry" is largely unwelcome.