Post

not really what you're looking for but @wisp.place is a static site service that serves files from your PDS @iame.li I think you vaguely tinkered with this idea or said something about an "almost static" PDS on stream. I realize there's websocket stuf

yeah you basically need websocket support if you want relays to work. so "some files on S3" is no good but it is possible to, say, ship a Docker image that has all the data baked in ahead of time and then can handle WS requests. easiest if you just store the firehose as the canonical data

Idk if this would be a useful for anything, but what if you separate the web socket handling into a separate generic service that could be pointed at multiple different “static PDS servers”?

I'd really love to have a sync mechanism for public atproto repos that works with static file hosting. the main use-case would be blogs. I think roughly the way it would work is that you upload the files, then poke a ping of relays, which resolve your DID doc and do a small HTTP fetch