Workshop page: “maybe this, maybe that” belongs here. These are options and questions, not a disguised specification.
What seems stable
The author publishes from a site they control. Their own site remains authoritative for their content. Public output should be portable, linkable, and understandable as ordinary web content wherever practical.
What is still wide open
| Question | Possibilities worth preserving |
|---|---|
| Public representation | Static HTML archive, feed documents, structured JSON, or a combination. |
| Feed transport / format | Borrow from Twtxt/Yarn simplicity, existing web feeds, IndieWeb conventions, or a small purpose-built format if existing standards do not fit. |
| Cross-site notification | Webmention-like delivery, polling, signed messages, or another lightweight exchange. |
| Broader federation | Investigate ActivityPub, Nostr, Secure Scuttlebutt and related systems before deciding whether compatibility helps or distorts the project. |
| Authoring | Dynamic admin application producing durable public pages; possibly local authoring with remote/static publication later. |
| Hosting | Ordinary shared hosting first; later consider local computer + DDNS, IPv6, static export, or hybrid models. |
| Published-feed privacy | Possibly public-only; possibly a simple entire-feed public/private switch. Avoid friends lists and per-post audience ACL complexity. |
Static-first is a bias, not a religion
Static output is attractive because it is cheap to serve, portable, cacheable, and likely to survive removal of the application. Dynamic behavior is still useful for authoring, authentication, editing, following, moderation, and remote interaction.
Identity, content, availability
A future architecture should avoid assuming that publishing identity, authoritative storage, and the publicly reachable copy must always be co-located.
Protocols we should study before inventing one
TwtxtYarn.socialIndieWebWebmentionActivityPubNostrSecure Scuttlebuttmicroblog.pub
Presence on this list is not an endorsement or roadmap commitment.
← Back to the landing page