ActivityPub, Mastodon, Bluesky and AT Protocol, POSSE, IndieWeb, webmentions, static site generators, and the blogroll's return.
Section 5 of 6 · 5 pieces
Start here
An argument that ActivityPub (the W3C standard underlying Mastodon and the Fediverse) and RSS address the same underlying problem — platform dependency — from different directions: one is push and social, the other is pull and archival.
Leaving the Platform
How the AT Protocol differs from ActivityPub in its approach to identity and data portability — the DID method, the personal data server, and what Bluesky's architecture means for users who want to move between hosts.
Leaving the Platform
The IndieWeb's POSSE practice — Publish on your Own Site, Syndicate Elsewhere — as a workflow and an argument about where content should live.
Leaving the Platform
The W3C Webmention specification as the IndieWeb's answer to cross-site conversation — how it works, where it is supported, and how it compares with the earlier Pingback standard it effectively replaced.
Leaving the Platform
How the major static site generators handle RSS and Atom output — Hugo's built-in template, Jekyll's feed plugin, Eleventy's approach — and why the shift toward static generation has quietly expanded the feed-publishing base without anyone announcing it.