From 1ce52ae0f88a9ce7dad6d23b1b3e8c53ed1a612d Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Mon, 5 Oct 2026 21:26:50 -0600 Subject: [PATCH] Point the usage-reporting link at danielstephenson.dev/usage-reporting The old link went to a section of a private repository and 404'd for everyone following it from a program's startup notice. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01BZQMN1M5hQKfUpPwDkMjqd --- README.md | 2 +- trace_client/trace_client.py | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index ae1e93c..4437196 100644 --- a/README.md +++ b/README.md @@ -127,7 +127,7 @@ it. A program that runs on other people's machines should expose the `enabled` switch in its settings — and say so once, the first time it runs, so the player knows reporting is on, that `TRACE_USAGE_REPORTING=off` turns it off, and where the details are: -. +. ## Getting it diff --git a/trace_client/trace_client.py b/trace_client/trace_client.py index 4aed2b4..03989cb 100644 --- a/trace_client/trace_client.py +++ b/trace_client/trace_client.py @@ -91,8 +91,7 @@ class TraceClient: (``"environment"``, ``"config"`` or ``"no key"``; ``None`` when on) so the program can say so in its notice. Programs that run on other people's machines should expose that switch in their settings and say - so once, pointing at - https://github.com/Stephenson-Software/trace#usage-reporting. + so once, pointing at https://danielstephenson.dev/usage-reporting. Every event carries the program's own version as the tag ``version`` -- the third argument, required, so a ``command`` event can be tied to a