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

docs: safe-ip does not fix Fandom either

Browse Source 
The runner move to [self-hosted, safe-ip] was recorded here as untested, with
the next cycle to settle it. It ran, and all four Fandom sources came back
403 (an interstitial challenge) — so that address is challenged too, and these
four still only move when a person refreshes them on the recorded permission.

Worth being exact about what the cycle did not settle, because the summary
looks fuller than it is: the nine game8 sources were all skipped_interval, not
due until 23:46 UTC, so nothing asked game8 anything and its 202 is unmeasured
on the new runner.

The reason string is doing the job it was added for one commit ago — the
challenge-or-refusal distinction is what says this is covered by the flag
rather than a host that turned us away, and it answered that from the summary
alone.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
Lucas Winther
2026-08-19 23:49:48 +02:00
co-authored by Claude Opus 5
parent 617b529dfd
commit d0b0f2e00c
1 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+10 -3
View File
@@ -390,9 +390,16 @@ into that one claim, and they have to be held apart:
`ubuntu-latest`) reported `skipped_robots` for all four Fandom sources using that same Bun client,
in the same cycle that nine game8 sources took the usual `202 CloudFront`. So a served address is a
precondition, not a detail: **a claim that these four now refresh on a schedule is a claim about the
address the runner has**, and it must be re-measured there rather than inherited from here. As of
writing, `refresh.yml` has just moved to `[self-hosted, safe-ip]` and has not yet run a cycle, so
their scheduled reachability is **untested**, not established. The next run's summary settles it.
address the runner has**, and it must be re-measured there rather than inherited from here.
**`[self-hosted, safe-ip]` was then measured, and Fandom challenges it too.** The first cycle after
that switch reported `403 (an interstitial challenge)` for all four Fandom sources — so the runner
move fixed this for game8's `202`, if it fixed anything, and not for Fandom. These four still only
move when a person refreshes them from an address Fandom serves, which is what
`--assume-robots-on-403` is for and why it is interactive-only. Two things that cycle did **not**
settle: game8, whose nine sources were all `skipped_interval` (not due until 23:46 UTC) and so were
never asked, and whether any address we control is served — this repository's own sandbox is, which
is where the `200`s above come from.
Three things worth keeping from the episode, because each one is a trap: