main
9
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
7449489519 |
docs: anti-cheat is the developer's declaration on Steam; the extension is archived
- DISCLAIMER section 5 and ToS item 5: anti-cheat is read from the anti-cheat disclosure on the Steam store page, which the developer fills in; an undeclared one shows "-", and a declaration can be wrong. Both are consent documents: the web gate shows these two diffs once. - README, CONTRIBUTING, Contact (shown at /legal/contact, not consent-gated): no more extension; a missing game or a correction goes in Discussions > Ideas; the manual fork path queues store links only. - CLAUDE.md: the anti-cheat sweep and its rules, the trio as the one manual set a writer replaces (an override still wins), OverrideGuard, links-only queue, clean_notes, the pattern mirror; 15 data writers. - ADMIN, dev_env (+vi), web/README: the extension is no longer a producer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
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>
|
||
|
|
fa8b81fd9b |
docs: the Turnstile check and the Referer fix, and what they made untrue
Legal (both reopen the consent gate for returning visitors, showing only the changed lines - edited line-locally so that diff stays small): - PRIVACY_POLICY: a section on the website's Turnstile check - after acceptance, at most daily, what challenges.cloudflare.com reads (IP, User-Agent, TLS fingerprint, page signals), that Cloudflare is processor for the site and controller where it improves its bot detection (the Turnstile Privacy Addendum), that the Worker forwards the token and IP and keeps neither; the f2p:human_check storage row. "The only third party", "the verification step" and "No fingerprinting" are corrected. - ToS section 9: the check exists; /api/data/*, /img/* and the apps stay excluded from both human checks. SECURITY_SETUP: - section 10 rewritten. It said the apps survived Hotlink Protection only because their webview sent no Referer (untrue since WebView2 started sending tauri.localhost), recommended switching the protection off, and said no allowlist could express the apps' origin - a Configuration Rule on http.referer can. Now: the per-<img> fix and its test, the rule for 2.0.0 installs, and the check, with the results measured today. - new section 12: widget settings (hostname, Managed, pre-clearance off), the TURNSTILE_SECRET secret and rotation, what the check is not, local testing with Cloudflare's test keys, the optional rate-limit expression. - the CSP block, the script-src/frame-src prose, "no form posts", the rule budget (Configuration Rules 1/10), and two stale paths. CLAUDE.md gains the human-check and <img> invariants and says "after consent and the human check" where the service worker, analytics and /welcome used to say "after consent". README, web/README, DEPLOYMENT, ACKNOWLEDGEMENTs, SECURITY (bypassing the client-side gate is out of scope), TAURI troubleshooting and the changelog follow. _headers and worker/lib/http.ts: comments only - why images override Referrer-Policy, what X-Frame-Options does and does not govern, and the public/_headers and SITE_ORIGIN references that were stale. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
5dfd9dd36e |
docs: analytics, the two WAF rules, and the claims they made false
The privacy policy said the site had no analytics, set no cookies, loaded nothing from a third party and did not have Cloudflare Web Analytics enabled. Three of those were already shaky and all four had to change, so this rewrites the affected sections rather than bolting a paragraph on: what the beacon does and does not do, why it waits for consent, the human-verification step, and where the site is no longer served. ToS gains section 9, which did not exist - there was no availability or automated- access clause at all. SECURITY_SETUP section 9 is reversed. It recommended turning Web Analytics OFF; it now records why the automatic mode can never work under a hash-based CSP, so nobody re-enables it, and what the JS-snippet setup is. Section 4 keeps "leave Bot Fight Mode off" and adds the two custom rules that are safe here, each exclusion annotated with what breaks without it, plus the country block with its real costs: Yandex indexing ends, the packaged apps stop working there, VPNs evade it trivially. The verification command for the country block is deliberately NOT the obvious one. `-H 'CF-IPCountry: CN'` proves nothing: geo.ts reads request.cf.country first, which cannot be spoofed, and Cloudflare overwrites that header on ingress. The doc gives the two checks that do prove something, including the local one whose expected result is 403 on every Worker route AND 200 on / - which is the whole argument for the WAF rule. Also corrected: the CSP transcribed in section 1 was missing both new hosts and still listed a frame-ancestors this policy has never carried (it is ignored in a meta CSP; X-Frame-Options covers it). CLAUDE.md gains four standing rules - the navigateFallback invariant, the two web-only CSP hosts and why automatic injection is impossible, per-document consent hashing and why it lives outside prefs.svelte.ts, and BLOCKED_COUNTRIES being defence in depth rather than the boundary. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
122075c9bf |
feat(admin): genre dropdown, bulk retag; ingest reduced to the extension
## /admin/edit
Genre is a dropdown instead of free text, built from the genres ACTUALLY in
use with their counts — the counts are the point, since they are how a vague
bucket announces itself ("Action" holds 287 games, "Adventure" 232). A
"Custom…" option still allows a value the catalogue has never used, and the
game's current genre is always offered even when absent from that list, so
loading a game can never silently change it.
New "Bulk by genre" mode: pick a genre, see everything carrying it, retag up
to ten in ONE commit. The cap is enforced in the UI (remaining checkboxes
disable, with "limit reached") and again on the server.
Supporting work:
- commitFiles() replaces commitFile(): several files in one commit, reading
the head and every file in ONE aliased GraphQL query so expectedHeadOid
still means what it says across ten files. Ten commits would be ten pushes,
ten workflow triggers and ten chances to land half a change.
- listByGenre() and genreCounts() in records.ts. Genres are counted by regex
over shard TEXT rather than parsing 3,426 records — verified to agree with a
full parse exactly (92 distinct, 3,426 games). listByGenre prefilters by
substring and only then parses, so cost scales with matches, not catalogue
size; an exact field check rejects the substring appearing in a description.
Found by driving the page: renderBulk() rebuilt all 60 cards on every checkbox
click, replacing the element just clicked and losing keyboard focus. Selection
now updates in place.
## Ingest: extension only
Removed the GitHub-issue and Telegram paths. Kept the browser extension, which
pushes to scripts/temp_info.jsonl directly, plus the /admin approve flow that
appends to the same file.
Deleted: bot-ingest.yml, ingest-from-issue.yml, ISSUE_TEMPLATE/add_games.yml,
docs/telegram-bot.md, and both copies of the bot QR.
Four things would have broken, and a fifth was already broken:
- BUILD BREAK. web/tsconfig.json sets noUnusedLocals, so removing the Telegram
and add-games UI orphans the PlusCircle and Bot icon imports — four TS6133
errors, web-ci red, site unbuildable.
- A live button. About.tsx linked issues/new?template=add_games.yml; GitHub
silently ignores an unknown template and drops the user on a blank form.
- CommandPalette linked "/add" — a route that does not exist. Every
`<Route path=…>` in web/src confirms it: left behind when sign-in and
in-app editing were removed, so selecting it navigated to the 404 page.
- notify-ci-failure.yml matches by exact workflow NAME and its own comment
warns a stale entry breaks silently.
- ALREADY BROKEN: README and CONTRIBUTING both linked
poli0981/free-steam-games-list-extension, which does not exist
(`gh repo view` → "Could not resolve"). The real repo is
poli0981/steam-f2p-extension. That was the link to the one path being kept.
README's Contribute section and CONTRIBUTING §2 still documented signing into
the web app with a Classic PAT — removed months ago. Both rewritten: the
extension is the submission route, issues are for reports, and discovery plus
/admin is how most games actually arrive now.
docs/ToS.md §5.1 governed sending a Telegram user_id to a bot that no longer
exists; removed, and TERMS_VERSION bumped 2 → 3 because ConsentGate exists to
re-ask when the terms change. Workflow counts corrected 24 → 23 in README and
SECURITY.md.
Kept deliberately: the maintainer's own @SkullMute0011 DM row and its QR, with
the "whitelist requests" framing dropped — that is a contact channel, not part
of the ingest path.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
||
|
|
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> |
||
|
|
16eabcbbf5 |
docs(v3.1.0): Telegram bot flow, AUTHORS at root, version bumps (#63)
- AUTHORS.md (new) at repo root — maintainer + canonical handle map
+ AI disclosure. Mirror of `username.txt` (now includes telegram bot,
telegram user, email).
- assets/qr/ (new) — QR PNGs for `@my_skull_bot` and `@SkullMute0011`,
mirrored to web/public/qr/ so the SPA serves them.
- About page (web): new Maintainer entries (Telegram bot + DM with
inline QR thumbnails + Email) and a dedicated "Telegram QR codes"
card with full-size scannable codes. Privacy note added.
- CONTRIBUTING.md rewrite: explicit `@my_skull_bot` flow as a
first-class path (find user_id → DM maintainer privately → whitelist
→ run when bot's online → follow prompts). Loud warning about
NEVER posting Telegram user_id in public channels.
- docs/PRIVACY_POLICY.md: new "Telegram bot" section covering data
flow, storage, retention, and the maintainer's commitment.
- docs/ToS.md: new section 5.1 with non-negotiable rules about private
vs public channels for personal info.
- docs/Contact.md: Telegram bot + DM entries at the top.
- README: version badge 3.0.0 → 3.1.0; quick links + workflow table
+ contributor section + docs index updated; Mark Dead Games and
Bot Ingest workflows listed.
- CHANGELOG: v3.1.0 entry covering PRs #60-#62 + this docs PR.
- Versions bumped:
web/package.json 1.0.0 → 1.1.0
web/src-tauri/Cargo.toml 1.0.0 → 1.1.0
web/src-tauri/Cargo.lock 1.0.0 → 1.1.0
web/src-tauri/tauri.conf.json 1.0.0 → 1.1.0
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|
|
00d9dc0fb5 |
Phase 7: date-sort fix + hamburger nav + About expansion + legal rewrite + Node 24 (#54)
date-sort fix
Steam release_date strings ("22 Aug, 2012", "Dec 19, 2025", "Coming
Soon", "TBA", year-only "2025"…) were sorted as strings, which mixes
alphabet-first chars ahead of numeric prefixes and scrambles years.
New parseReleaseDate() in lib/utils.ts hands back a comparable
timestamp via Date.parse with a 4-digit-year fallback. Unparseable /
TBA values get -Infinity so they cluster out of the way regardless of
sort direction. GamesTable's released column now uses it.
hamburger mobile nav
Sidebar was hidden below the lg breakpoint with no way back. New
ui/sheet.tsx Radix-Dialog-based drawer that slides in from the left,
Sidebar refactored into shared SidebarBody + desktop / mobile wrappers,
Topbar gets a Menu button (mobile-only). Drawer auto-closes on route
change so tapping a nav entry doesn't require an extra X click.
About page expansion
• New "Heads-up before you trust this" card with the four accuracy
caveats from the maintainer's notes:
- genre is best-effort (tags+description heuristic)
- English-only assumption (regional storefronts can break parsing)
- test data may have leaked in during development
- "unsigned" Activity entries are dev artefacts, not malicious
• New "AI disclosure" card naming Grok (v1) + Claude (v2+) and noting
that LLM calls only happen on the maintainer's dev machine, never
from the visitor's browser at runtime.
• New "Legal & license" card linking MIT + DISCLAIMER + ToS + EULA +
PRIVACY + ACKNOWLEDGEMENTs + Contact, all opening on GitHub.
• Per-third-party SPDX licence badges in the stack list, each linking
to the dep's actual LICENSE file.
• Added echarts-wordcloud + idb-keyval to the deps roster.
Legal docs rewrite (DISCLAIMER, EULA, ToS, PRIVACY)
Tightened wording while keeping the casual voice. Each doc now
explicitly references the four accuracy caveats, the third-party
trademark situation (Steam, Akamai, GitHub), and the AI-assistance
status. PRIVACY_POLICY enumerates exactly what the static site does
and does not do (no analytics, no fingerprinting, lists the four
third-party endpoints touched at runtime + their privacy links).
EULA + ToS now name-check Steam Subscriber Agreement / Akamai
appropriately rather than just shrugging.
Node 24 / refreshed actions
Phase 5+ deploy-pages was running on Node 20 (which deprecates June
2026). Bumped:
actions/checkout v4 → v5
actions/setup-node v4 → v5 (node-version 20 → 24)
actions/upload-pages-artifact v3 → v4
actions/deploy-pages v4 → v5
notes.txt
The maintainer's local working notes that they explicitly didn't want
pushed. Added [Nn]otes.txt / [Nn]otes.md to .gitignore (the existing
rule only matched the singular [Nn]ote.txt).
Build 4.87 s; bundle index 113 KB gz (+4 KB for Sheet primitive +
About expansions). All other chunks unchanged.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|
|
6dc9f75945 | add initial documentation files including acknowledgements, code of conduct, and policies |