4 ms·
> 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 extende
by 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 agoWhy 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 agoGDPR aside, this kind of "telemetry" is largely unwelcome.