No this is actually the perfect solution.
A ‘dumb’ WACZ replayer server that takes a querystring WACZ resource (like https://replay.example/?wacz=https://blossom.example/<id>.wacz#/?url=https://site.com/), downloads it to a cache, builds an in-memory URL -> response index from the archive, and t...