From 051567670f59b914f5d2d5059f28afebad8edb29 Mon Sep 17 00:00:00 2001 From: Graham Barber Date: Sun, 28 Sep 2025 18:48:48 +0000 Subject: [PATCH] update README with postmortem --- README.md | 31 ++++++++++++++++++++++++++----- 1 file changed, 26 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 3e41934..ed77005 100644 --- a/README.md +++ b/README.md @@ -5,17 +5,19 @@ Space is an attempt at building an IndieWeb-capable personal site, before I started looking into AT Protocol. It uses [Chi](https://go-chi.io/#/), [Templ](https://templ.guide/), and [TailwindCSS](https://tailwindcss.com). +Data is stored using SQLite, and your DB is continuously backed up to S3 via +[Litestream](https://litestream.io/). -Media files are stored in an S3 backend of your choice, and any unrecognized -or unsupported [post types](https://indieweb.org/posts) are be rendered as raw -JSON until support was added. +Any unrecognized or unsupported [post types](https://indieweb.org/posts) are +rendered as raw JSON until they are explicitly supported. Media files are +stored in the same S3 backend that Litestream uses, so all your data is +replicated off-machine. Notably, the Tailwind pipeline is not checked into the project, as this was built before Go Tool support. If you want to take it for a test-drive, you can check the `.env.example` file -for all required configuration values. At the time, I was quite pleased with -how this turned out. +for all required configuration values. ## Supported Specs @@ -24,3 +26,22 @@ how this turned out. - [ ] [h-card](https://microformats.org/wiki/h-card) - [ ] [Webmentions](https://www.w3.org/TR/webmention/) - [ ] [Microsub](https://indieweb.org/Microsub-spec) + +## What happened? + +At the time, I was quite pleased with how this turned out. I think I nailed the +aesthetics, and I hit my requirement for data durability and replication. I was +targeting Fly.io for deployment, and Fly+Tigris was an excellent combo. + +Day-to-day, though, I couldn't make a habit of using this. IndieWeb is a lonely +place when you don't have any connections and you're not a social creature by +default. Implementing support for different post types over time felt like it +was going to be a drag, and my heart just wasn't in it. + +I have my hopes up with AT Protocol, however. AppViews remove the need for +implementing display logic for each "post type" manually, and Lexicons allow +for myriad post types contributed by different services. It's an easier place +to live for a lurker such as myself. + +Maybe at some point, I'll take a stab at implementing my own PDS, but until +then--here's the thing I already built. -- 2.51.2