The cross-origin fetch part is what stands out most to me here -- the browser reads another repo's .keep-the-why, then fetches that repo's state.json directly, no server in between. GitHub Pages happens to serve everything with permissive CORS by default, which is probably why this works smoothly for the examples here, but the post calls out "GitHub Pages or another static host." For a host that doesn't set Access-Control-Allow-Origin -- a bare S3 bucket without CORS configured, a plain nginx box serving static files -- does the Globe just silently drop that wave, or is there a visible failure state distinguishing "nothing there" from "blocked by CORS"? That seems like exactly the kind of thing that would be invisible until someone hits it.