Do_not_track
The DO_NOT_TRACK initiative proposes a standardized environment variable to allow users to opt out of telemetry, usage reporting, and tracking by software tools. Currently, different tools use various methods to disable data collection, creating inconsistency and user burden. A single standard would simplify privacy control across command-line tools and software development kits.
- ▪The DO_NOT_TRACK proposal introduces a unified environment variable to disable telemetry and tracking in software.
- ▪Many tools like .NET, AWS SAM CLI, and Google Cloud SDK currently use different opt-out methods for telemetry.
- ▪The standard recommends setting DO_NOT_TRACK=1 in shell configuration files to apply the setting globally.
- ▪Software authors are encouraged to respect this variable and consider making data collection opt-in by default.
- ▪Similar standards like NO_COLOR and FORCE_COLOR serve as precedents for environment-based behavior control.
Opening excerpt (first ~120 words) tap to expand
DO_NOT_TRACK A standard for respecting user privacy in software The Problem Many CLI tools, SDKs, and frameworks collect telemetry data by default. Each one has its own way to opt out: Tool Opt-out method .NET DOTNET_CLI_TELEMETRY_OPTOUT=1 Copy AWS SAM CLI SAM_CLI_TELEMETRY=0 Copy Azure CLI AZURE_CORE_COLLECT_TELEMETRY=0 Copy Gatsby GATSBY_TELEMETRY_DISABLED=1 Copy Go go telemetry off Copy Google Cloud SDK gcloud config set disable_usage_reporting true Copy Homebrew HOMEBREW_NO_ANALYTICS=1 Copy Netlify CLI netlify --telemetry-disable Copy Syncthing STNOUPGRADE=1 Copy You get the idea. There are too many, and they are all different.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News: Front Page.
Discussion
0 commentsMore from Hacker News: Front Page
