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 then serves archived HTTP responses under a replay path - rewriting links so the browser keeps requesting resources from the archive instead of the live web.
This wacz replay server would be separate from the blossom archives, you just arrive at the server and tell it which wacz to load. it doesn't have to care who's serving the wacz, if it's from blossom or s3 or whatever, as long as the file is publicly-downloadable.
Driveway Situation ❋ (npub1656…j8up) you should do this in wayback.st once you finish whatever else you're doing 😆
vinney...axkl
npub19m…8axkl
2026-02-21 19:17:03 UTC
in reply to nevent1q…q6zl
Author Public Key
npub19ma2w9dmk3kat0nt0k5dwuqzvmg3va9ezwup0zkakhpwv0vcwvcsg8axklPublished at
2026-02-21 19:17:03 UTCEvent JSON
{
"id": "4e9443d5f5b8c3c809ad47393b79a64d024a53a1218fa29b43a4a039fa20c06c",
"pubkey": "2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331",
"created_at": 1771701423,
"kind": 1,
"tags": [
[
"e",
"8aa8af99429d3b7bd2d43f7d1bcdb41ad7b277f2da6dcb479708a50818b6308d",
"wss://chronicle.dtonon.com/",
"root",
"d53547a74ef91fdf2b1af5d1b7fe56daeb833df2c7b08e6767dd6ace04d22175"
],
[
"e",
"95408f212ab5402173fe740c22d18de4997894f5c848e45bdfd3a19059030d34",
"wss://relay.damus.io/",
"reply",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"d53547a74ef91fdf2b1af5d1b7fe56daeb833df2c7b08e6767dd6ace04d22175"
],
[
"p",
"c230edd34ca5c8318bf4592ac056cde37519d395c0904c37ea1c650b8ad4a712"
],
[
"p",
"41eae3d0d5b78e75455e4450bd1e4e46537ff2c19d4c3834289ed56ad2458e1d"
],
[
"p",
"434f97993627f1e61f14eeaf60caa8cfdcec10a592caff8250c825252d548c15"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
]
],
"content": "No this is actually the perfect solution.\nA ‘dumb’ WACZ replayer server that takes a querystring WACZ resource (like https://replay.example/?wacz=https://blossom.example/\u003cid\u003e.wacz#/?url=https://site.com/), downloads it to a cache, builds an in-memory URL -\u003e response index from the archive, and then serves archived HTTP responses under a replay path - rewriting links so the browser keeps requesting resources from the archive instead of the live web.\n\nThis wacz replay server would be separate from the blossom archives, you just arrive at the server and tell it which wacz to load. it doesn't have to care who's serving the wacz, if it's from blossom or s3 or whatever, as long as the file is publicly-downloadable.\n\nnostr:npub165650f6wly0a72c67hgm0ljkmt4cx00jc7cguem8m44vupxjy96s6vj8up you should do this in wayback.st once you finish whatever else you're doing 😆",
"sig": "3628be674dfb4c664102146ec9567f8b273a79d5778b0d77d636c22d99013b1faa07ffb237befafe8b929501e6237cf4831024df1d5148378120bccc85453273"
}