lucasw89/gacha-event-tracker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: all four Fandom sources have a snapshot now

Browse Source 
The previous commit landed the first live pages for nikke and nikki, which
retires the last version of a sentence that has been wrong twice in one session
— it counted which of the four had ever been fetched, and that number kept
moving underneath it.

So it no longer counts. What matters about these four is not how many have a
snapshot but that every one was taken by hand and always will be: their
freshness is exactly as old as the last person who ran the refresh themselves,
because the schedule cannot read Fandom's robots.txt. Points at
--assume-robots-on-403, which is what makes that run possible.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
Lucas Winther
2026-08-19 04:52:34 +02:00
co-authored by Claude Opus 5
parent 2447a4295e
commit 240e4d59d1
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+5 -5
View File
@@ -367,11 +367,11 @@ to our fetcher, and a real headless browser gets a Cloudflare managed challenge
Two consequences, and neither is a licence to work around it: Two consequences, and neither is a licence to work around it:
- **All four** built Fandom sources report `skipped_robots` on **every** run, from any address we - **All four** built Fandom sources report `skipped_robots` on **every** run, from any address we
have, so `r1999`, `fgo`, `nikke` and `nikki` are permanently fixture-backed until someone have, so `r1999`, `fgo`, `nikke` and `nikki` only ever move when someone refreshes them from an
refreshes them from an address Fandom serves. `r1999` and `fgo` have snapshots, both taken by hand address Fandom serves. All four have a snapshot as of 2026-08-19 and every one of them was taken
on 2026-08-19; `nikke` and `nikki` have never had one and are served from their fixtures. That is by hand. That is not a source being down — nothing is broken — but nothing will ever update these
not a source being down: nothing is broken, and nothing will ever update any of the four on a four on a schedule either, so their freshness is exactly as old as the last person who ran
schedule. `bun run refresh` themselves. `--assume-robots-on-403` below is what makes that run possible.
- A **new** Fandom source can still be added, but only once someone reads that wiki's `robots.txt` - A **new** Fandom source can still be added, but only once someone reads that wiki's `robots.txt`
from an address Fandom serves and records it here. That is exactly how Nikke was cleared on from an address Fandom serves and records it here. That is exactly how Nikke was cleared on
2026-08-19: the file was read in a browser, is the standard Fandom file — no `Disallow: /` for 2026-08-19: the file was read in a browser, is the standard Fandom file — no `Disallow: /` for