Microsoft/.Net Foundation added telemetry to the dotnet command line last year

Post by mel919 » Mon, Jul 24, 2017, 6:26 PM UTC

strictnein wrote: post #79

mel919 wrote: post #33

Earlier quoted context omitted.

I'm not the author of the blog post. I think you're comparing apples and oranges, also this kind of reasoning is an example of "tu quoque" logical fallacy.

> tu quoque No, this is not that. The "tu quoque" logical fallacy follows this pattern (from Wikipedia): Person A makes claim X. Person B asserts that A's actions or past claims are inconsistent with the truth of claim X. Therefore X is false.[2] They are not saying their claim is false. They're saying that if they care so much, why are they subjecting their users to tracking that they are unable to opt out of?

Post by reitanqild » Mon, Jul 24, 2017, 8:27 PM UTC

blub wrote: post #56

nitinreddy88 wrote: post #27

Earlier quoted context omitted.

@blub can you explain me how it's exactly "spying on you"? There is difference between collecting information about how many people are using vs whether a particular person is using. Collecting diagnostic information from windows application failures/how many failures etc are there ever since Windows 95 era. Similarly, collecting information about how many people are using dotnet core build/test/publish is similar to…

Spyware is software collecting information about someone without their consent. Doesn't have to be malicious, doesn't have to be what's legally defined as personal information. The fact that many companies are doing it doesn't make it less inappropriate. Reputable companies will clearly inform users and ask for their confirmation. Then they respect their choice. Disreputable companies such as MS or Google take withou…

Post by staticelf » Tue, Jul 25, 2017, 7:56 AM UTC

shakna wrote: post #95

staticelf wrote: post #82

Earlier quoted context omitted.

No but it's big differences in the projects. If Powershell would have gotten telemetry I would understand the objections.

There is an earthshattering difference between a website, a place I go to let someone else run code, and a build tool I use to run code I write.

Post by staticelf » Tue, Jul 25, 2017, 10:11 AM UTC

shakna wrote: post #97

staticelf wrote: post #96

Earlier quoted context omitted.

What? You run the code in the browser when it comes to javascript just as you run the .NET SDK. The difference is that the .NET SDK tell you that they send telemetry, how to disable it and what they store are not really any sensitive information. Most websites run code with the sole purpose of identifying you.

JS engines are supposed to be sandboxed, and have limited APIs to draw from. Unless you use a jail, a local application can do just about anything. The difference is expectation. I expect websites to run things I don't control. I expect a local application to behave in a certain way.

Post by nmeofthestate » Tue, Jul 25, 2017, 4:03 PM UTC

uw_rob wrote: post #47

nmeofthestate wrote: post #17

Ah, 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.

> And that's easy - it's a setting. (Non) problem solved. I still don't think this is a non problem. When you are using many different tools that are updating constantly, it is easy to not notice one adding telemetry. And even if you disable it, it very well may be silently reenabled in the future.