DO_NOT_TRACK=1 proposes a single standard env var to replace dozens of conflicting CLI/SDK telemetry opt-out mechanisms.
Key Takeaways
The problem: every tool has its own opt-out – DOTNET_CLI_TELEMETRY_OPTOUT, HOMEBREW_NO_ANALYTICS, GATSBY_TELEMETRY_DISABLED, and many more, all different.
The spec covers ad tracking, usage reporting, crash reporting, and any non-essential network requests to software creators or third parties.
Software authors are asked to check DO_NOT_TRACK=1 and disable all tracking, while also considering making telemetry opt-in by default.
Modeled after NO_COLOR and FORCE_COLOR as composable shell environment conventions.
Hacker News Comment Review
Skepticism runs high that adoption will mirror browser DNT’s failure – voluntary compliance means the tools most likely to adopt it are already privacy-conscious, not the problematic ones.
Commenters noted the naming itself reveals the problem: a “do not track” flag implies tracking is the default, with some preferring a positive-form variable like ALLOW_TRACKING=0 or even a comma-separated allowlist.
As a practical workaround while adoption lags, toptout.me and DNS-level blocklists already aggregate opt-out env vars and telemetry domains respectively.
Notable Comments
@spudlyo: Hugging Face transformers kept phoning home even after HF_HUB_DISABLE_TELEMETRY=1 and local_files_only=True; only HF_HUB_OFFLINE=1 stopped outbound connections.
@ximm: “Any tool that will publicly announce support for this spec is a tool I know to avoid” – framing adoption as a self-incriminating signal.
