Sitelet https://github.com/Stephenson-Software/trace-client-python/pull/9/files
Skip to content

Point the usage-reporting link at a public page #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dmccoystephenson merged 1 commit into from
Oct 6, 2026
Merged

Point the usage-reporting link at a public page #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
<https://github.com/Stephenson-Software/trace#usage-reporting>.
<https://danielstephenson.dev/usage-reporting>.

## Getting it

Expand Down
3 changes: 1 addition & 2 deletions trace_client/trace_client.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading