Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement dotnet telemetry on/off command #10009

Closed
4 tasks
nopara73 opened this issue Dec 20, 2018 · 4 comments
Closed
4 tasks

Implement dotnet telemetry on/off command #10009

nopara73 opened this issue Dec 20, 2018 · 4 comments

Comments

@nopara73
Copy link

I am building a privacy focused software (https://github.com/zkSNACKs/WalletWasabi/) with .NET Core.
While I am used to getting MS-shamed by some over-enthusiastic Linux users, once in a while their complains are on point. The issue of .NET telemetry is one of those things.
I have read the related issue here (https://github.com/dotnet/cli/issues/3093) and while I do not agree with, I acknowledge and respect the opinion and the decisions of the maintainers on this matter.

However I believe providing a

  • preemptive and
  • easy way to
  • permanently turn off the telemetry
  • while avoiding future telemetry notifications at updates

is reasonable to ask for.

By preemptively I mean it should not start collecting data, only after the first notification is shown to the user.
I would suggest a command dotnet telemetry on/off to be an easy way to turn off the telemetry.
It is important that it should turn off the telemetry permanently, so future updates won't set it back. I can't imagine that the user's intention is that updates to turn on the telemetry.
And finally the purpose of avoiding future telemetry notifications is more like making sure the user won't get uncomfortable by reminding him or her about a feature (that is already turned off) that he or she may consider to be slightly unethical.
image

@livarcocc
Copy link
Contributor

There is a long discussion about this here: https://github.com/dotnet/cli/issues/3093. I am going to close this issue against that one, which has also been closed.

cc @KathleenDollard @richlander

@nopara73
Copy link
Author

@livarcocc Please read my issue before you close it. I mentioned the issue that you pointed me to in my comment.

@KathleenDollard
Copy link

@nopara73

I understand that it felt like Livar had not read your issue before closing it. I doubt that was the case because we do talk about this question and the issue he quoted is a way of indicating "I can't tell you any more today than we said here."

Thank you for articulating specific requests in a functional manner without bringing a lot of thoughts on telemetry.

We aren't in a position to address this right now.

@ichensky
Copy link

Do you know the right easy way to firewall dotnet tool telemetry with white rules for the nftables/ dns proxy server?

@msftgits msftgits transferred this issue from dotnet/cli Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants