wisp.place has a blog now
Somewhere to put release notes, architecture write-ups and the occasional postmortem — instead of burying them in commit messages.
wisp.place has been running for a while without anywhere to write things down. Release notes went into commit messages, design decisions went into my head, and outages went into whatever I typed on Bluesky at the time. None of that is findable six months later.
so: a blog.
what goes here
- release notes. when something ships that changes how you deploy or how your sites are served, it gets a post.
- architecture write-ups. how the firehose consumer, tiered storage and hosting service fit together, and why they were built the way they were.
- postmortems. when wisp.place breaks, what broke and what changed afterwards.
- protocol notes. things learned building on AT Protocol that aren't specific to wisp.place.
Wwat doesn't go here: marketing. wisp.place is a passion project, not a startup, so there is nothing to upsell you on.
the short version of what wisp.place is
if you found this post before you found the project: wisp.place is static hosting built on the AT Protocol. you upload your site's files to your own PDS as blobs, and a record lists every file and the site's name. the hosting service watches the network for those records and serves what it finds.
the practical consequence is that your site isn't locked in a hosting account. the files live in your PDS, under your identity. If wisp.place disappeared tomorrow, someone else could serve the exact same records. the CLI already does this, and so can you.
subscribing
There's an RSS feed. announcements will also go out on @wisp.place. there is no mailing list and there won't be one.
this blog is itself a wisp.place site. a folder of HTML, uploaded to a PDS, served by the same code that serves yours. if it goes down, that's informative too.