sdk icon indicating copy to clipboard operation
sdk copied to clipboard

Respect `DO_NOT_TRACK` as standardized alternative to `DOTNET_CLI_TELEMETRY_OPTOUT`

Open khellang opened this issue 6 years ago • 5 comments

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/

khellang avatar Nov 15 '19 13:11 khellang

It seems like this has been denied. https://github.com/dotnet/sdk/pull/17472#issuecomment-855087362

fowl2 avatar Jun 17 '21 03:06 fowl2

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

Extarys avatar Jan 09 '24 01:01 Extarys

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 avatar Mar 12 '24 20:03 marcpopMSFT

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 https://github.com/dotnet/sdk/pull/17472#issuecomment-1175591096 which echoes my thoughts

coopbri avatar Jun 25 '24 05:06 coopbri

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 😅

khellang avatar Jun 25 '24 07:06 khellang

I would be very, very surprised if a company such as Microsoft aligns with consumer initiatives—even as light as this one in their open-source projects.

cos4ni2s avatar Jul 17 '25 19:07 cos4ni2s

I would be very, very surprised if a company such as Microsoft aligns with consumer initiatives—even as light as this one in their open-source projects.

Interesting and imo misaligned with reality, considering they have been extremely responsive to consumers in FOSS projects such as VS Code and TypeScript (I don't use VS Code anymore btw, just credit where credit is due)

coopbri avatar Jul 17 '25 19:07 coopbri

Interesting and imo misaligned with reality, considering they have been extremely responsive to consumers in FOSS projects such as VS Code and TypeScript (I don't use VS Code anymore btw, just credit where credit is due)

Ironic considering this was posted in 2019—six years ago. I don't use VSCode and .NET anymore because of these enabled by default/opt-out user tracking and telemetry practices Microsoft apparently couldn't stop themselves from doing even in the FOSS ecosystem.

cos4ni2s avatar Jul 18 '25 13:07 cos4ni2s