DO_NOT_TRACK=1 proposes a single standard env var to replace dozens of per-tool telemetry opt-out variables across CLI tools and SDKs.
Key Takeaways
The problem: tools like .NET, AWS SAM CLI, Gatsby, Homebrew, and Netlify each use a different env var to disable telemetry, with no shared standard.
The proposal: set export DO_NOT_TRACK=1 in your shell config; compliant tools should disable all tracking, analytics, crash reporting, and non-essential network requests.
Software authors are asked to check DO_NOT_TRACK=1 alongside existing opt-out mechanisms and consider switching to opt-in telemetry.
The spec follows precedent set by NO_COLOR (no-color.org) and FORCE_COLOR (force-color.org) for terminal behavior standardization.
Hacker News Comment Review
Commenters broadly agree the fragmentation is real but doubt the proposal fixes it: tools that adopt this standard are self-identifying as opt-out-by-default offenders, which one commenter called a “helpful honeypot.”
A practical thread emerged around the incomplete variable list: SEMGREP_SEND_METRICS, NEXT_TELEMETRY_DISABLED, SLS_TELEMETRY_DISABLED, HF_HUB_OFFLINE, and others were surfaced as missing from the site, with HuggingFace’s transformers library called out for being especially hard to silence even with HF_HUB_DISABLE_TELEMETRY=1.
Skeptics argue opt-out framing legitimizes surveillance defaults; the browser DNT precedent was cited as evidence standards without enforcement are ignored.
Notable Comments
@huksley: shares a production deploy snippet with eight additional telemetry opt-out vars not covered by the site.
@spudlyo: details how HuggingFace transformers still phones home despite HF_HUB_DISABLE_TELEMETRY=1; only HF_HUB_OFFLINE=1 stopped outbound connections.
