3 Commits
Author SHA1 Message Date
poli0981andClaude Opus 5.5 a74a004e19 docs: publish role contact addresses and the maintainer's website
contact@ stays the default. Three role aliases go where a reader of that
document will look for them, and nowhere else:

- security@  SECURITY.md, security.txt, SECURITY_SETUP section 8
- privacy@   the Privacy Policy's "Your rights"
- copyright@ LICENSE-DATA (new "If you hold rights" section) and ToS
             section 6, one address for copyright, DMCA and takedown notices

security.txt now lists GitHub's private vulnerability reporting first and
security@ second, in RFC 9116 preference order; the links page is not a
security channel and is dropped from it. The About page gains a Website card
(https://poli0981.dev/), two columns at sm and three from md so the email
handle never truncates. AUTHORS, Contact, CONTRIBUTING and username.txt carry
the full map.

The copyright text promises a human reading, not an outcome: an override
cannot blank a field and the store refresh rewrites description monthly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 23:31:09 +07:00
poli0981andClaude Opus 5 e2b2187ee4 feat(data): truncate description to 180 chars
The field held each publisher's store blurb verbatim — median 213 characters,
longest 340. At that length it reproduced whole blurbs rather than quoting from
them, which is not what LICENSE-DATA claims it does when it calls them "short
identifying quotations" and excludes them from the CC BY grant. This makes the
claim true.

Measured: 2,156 of 3,426 rows (63%) shortened, data/ 671 KB -> 517 KB (-23%),
no stored value now exceeds 180 characters.

Truncation happens in exactly ONE place — save_main(), the same choke point
apply_overrides() uses. `description` has three write paths (apply_details in
fetcher.py, merge_extension_data and the legacy desc->description migration in
data_store.py), so putting it at any of them would have left the others
producing full-length values and the shards flip-flopping between writers.
save_main() is the only code that writes data/data_*.jsonl, so covering it
covers everything, including any future writer.

Idempotent by construction: the result is always <= the cap, so a second pass
returns it unchanged. Verified on the real catalogue — a second run reports 0
records changed. That property is load-bearing rather than nice-to-have,
because this runs on EVERY write to data/; without it the truncator would nibble
a character off every description on every run and rewrite all five shards
forever.

Cuts on a word boundary when one falls in the last 40% of the budget, so a
blurb whose tail has no spaces keeps its text instead of losing most of it, and
the ellipsis is included in the 180 rather than pushing past it. Verified
byte-level: U+2026, e2 80 a6, not a mojibake three-dot.

Deliberately does NOT bump each record's last_updated. That field means the
game's data changed; shortening how much of a publisher's blurb this repository
stores is a change to our representation, not news about the game. Bumping it
would have shown ~2,150 games as freshly updated on the Activity and Health
pages on the day this first ran.

Ordered before apply_overrides() so a human decision always has the last word —
no override can set `description` today, but the ordering should not depend on
that staying true. Confirmed the live override (Draw Party, genre) survived the
full-catalogue rewrite intact.

The blurb is now attributed where it is actually read, not only in
LICENSE-DATA: the detail drawer carries a "Blurb by the publisher, via Steam —
shortened" line, translated in both locales. LICENSE-DATA's figures updated to
match the new shape.

Note this rewrites every shard, so index.json.last_updated moves and every
client's IndexedDB cache invalidates at once. That is expected and is why this
is its own commit.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-11 07:24:15 +07:00
poli0981andClaude Opus 5 5ab4f27347 docs: split the licence, correct the legal docs, add deployment and admin guides
The docs had drifted badly from the code. This makes them true.

LICENCE SPLIT. Code stays MIT; the dataset moves to CC BY 4.0 in a new
LICENSE-DATA, which is explicit about what the project cannot license: the
`description` field is the publisher's own store blurb stored verbatim (median
213 characters), `header_image` is a URL to publisher artwork, and game names
are trademarks used nominatively. Blanket-MIT over that material was a claim
the project was never entitled to make. Facts — player counts, review
percentages, platform support — are noted as unownable; the CC BY grant covers
the compilation and the project's own derived fields.

PRIVACY POLICY, rewritten rather than patched. The previous one said "no
backend, no server-side log, no cookies, no server other than GitHub's CDN".
Every clause of that is now false: the site runs on a Cloudflare Worker that
processes IP and User-Agent and keeps operational logs. It also documents the
one honest exception — the Activity page still calls api.github.com and loads
GitHub avatars from the browser, so GitHub sees a visitor's IP there while no
other page does — and lists every localStorage, IndexedDB and Cache Storage key
with why it exists.

SECURITY.md, rewritten. The old one claimed "no executable code, no
dependencies, no backend, no user data" and said there was no contact address,
while four other files publish one. It also told people to report
vulnerabilities in public issues. There is now a real scope (the Worker, the
proxies, D1, Actions secrets, the Tauri signing key), a private channel via
GitHub's vulnerability reporting, and specific things worth probing.

EULA corrected on two counts: it asserted a single MIT licence over everything,
and claimed there is "no installable software" despite the signed desktop and
Android builds. ToS and DISCLAIMER updated for the licence split, the new
domain, and the removal of in-browser editing and GPG signing — the disclaimer
described a signing flow that no longer exists.

README contradictions fixed: 1.2k games -> 3,424 across 5 shards not 2, 11
workflows -> 24, two scripts listed that were never in the tree, a TanStack
Table dependency the project does not use, and nine links to the old Pages URL.

New: docs/DEPLOYMENT.md (how a push becomes a deploy, the two wrangler.jsonc
fields that silently break it, and the stale-service-worker trap when verifying)
and docs/ADMIN.md (Cloudflare Access plus the GitHub App, with the exact
permission set — Contents write and Metadata only, and why Actions and
Workflows are deliberately withheld).

Two live fixes came out of writing this. GitHub Pages was serving a blank page:
it had the new index.html, which references assets at `/`, while Pages serves
under /free-steam-games-list/, so every asset 404'd — and deploy-pages.yml kept
redeploying it. That workflow now publishes a redirect that preserves the #/
fragment, since Pages cannot issue a 301. And CI pinned Python at 3.11, 3.12
and 3.14 across different workflows while the docs claimed 3.12 was pinned;
all fourteen references are now 3.12, which makes the claim true.

TERMS_VERSION 1 -> 2, so everyone re-consents. A privacy policy that now
discloses edge logging where it previously promised none is not a change to
apply silently.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-10 16:09:04 +07:00