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

Respect DO_NOT_TRACK as standardized alternative to DOTNET_CLI_TELEMETRY_OPTOUT #3917

Open
khellang opened this issue Nov 15, 2019 · 5 comments
Milestone

Comments

@khellang
Copy link
Member

khellang commented Nov 15, 2019

DO_NOT_TRACK is a proposed unified standard for opting out of telemetry for TUI/console apps.
It would be nice if the dotnet CLI followed the same standard. See https://consoledonottrack.com/

@fowl2
Copy link

fowl2 commented Jun 17, 2021

It seems like this has been denied. #17472 (comment)

@Extarys
Copy link

Extarys commented Jan 9, 2024

A year and a half later, any update on using this? I feel like it's a standard now on many OSS.

@nagilson nagilson added the needs team triage Requires a full team discussion label Feb 20, 2024
@marcpopMSFT marcpopMSFT removed the needs team triage Requires a full team discussion label Mar 12, 2024
@marcpopMSFT marcpopMSFT added this to the 9.0.1xx milestone Mar 12, 2024
@marcpopMSFT marcpopMSFT assigned nagilson and unassigned nagilson Mar 12, 2024
@marcpopMSFT marcpopMSFT removed this from the 9.0.1xx milestone Mar 12, 2024
@marcpopMSFT
Copy link
Member

Coming back to this, we reviewed the original effort and it doesn't appear to have been picked up broadly so we're going to continue to hold off for now.

@marcpopMSFT marcpopMSFT added this to the Backlog milestone Mar 12, 2024
@coopbri
Copy link

coopbri commented Jun 25, 2024

I respect the concern for the lack of widespread usage. With that being said, adoption by an entity such as Microsoft would likely be a monumental step towards such public usage, and it seems to me like this would not only be a straightforward implementation in the .NET project, but a well-received publicity and marketing measure for .NET and Microsoft as a whole. Considering there are 125 upvotes at the time of writing on the OP in this issue, and the lack of other well-known console opt-out standards (please correct me if I'm wrong), I am curious what is desired by the .NET team to move this budding community effort into the SDK. I believe as a general technology community (beyond .NET), we should combine efforts to hone in on standards such as what was done in hardware with e.g. USB. Despite the claim that there is no broad adoption, there certainly is a meaningful amount of it. Perhaps there is simply a lack of marketing and awareness; I argue that the idea itself has merit.

I would be curious to hear concrete adoption hesitations. I noticed the denied PR (#17472) supports both the existing opt-out strategy (bespoke env var), as well as the standard one and simply checking for either, but I don't see clear rationale for denying it.

EDIT: Just noticed #17472 (comment) which echoes my thoughts

@khellang
Copy link
Member Author

khellang commented Jun 25, 2024

Considering there are 125 upvotes at the time of writing on the OP in this issue

It's the #⁠2 most upvoted issue in this repo 😅

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

6 participants