The ownership argument made operational

POSSE — Publish on your Own Site, Syndicate Elsewhere — is an IndieWeb practice that treats a personal domain as the canonical record of everything a writer produces. Platform posts are copies; the originals live on infrastructure the publisher controls. The acronym was coined within the IndieWeb community, a loose network of developers and writers who have argued since roughly 2011 that social platforms should be recipients of content, not its custodians.

The workflow is straightforward in principle. A post appears first at a URL the author owns, then a copy — sometimes truncated, sometimes full — flows to Twitter, Mastodon, LinkedIn, or wherever an audience has gathered. Links in the syndicated copies point back to the original. If the platform disappears or changes its terms, the canonical content survives intact.

Small self-hosted server on a home-office shelf with ethernet cables routed neatly, indicator lights lit
Miniflux and FreshRSS will run on hardware of this order. That is the whole argument for hosting a reader yourself.Photo: panumas nikhomkhai / Pexels
Terminal window on a dark monitor showing a raw Atom feed in XML, angle brackets and namespaces visible, person's hands on keyboard
A feed is a text file sitting on a server. Between the publisher and the reader there is a fetch, and nothing else.Photo: Tima Miroshnichenko / Pexels

What makes POSSE technically coherent rather than merely aspirational is the combination of RSS and webmentions. An RSS or Atom feed at the source domain lets aggregators, readers, and other tools discover new posts the moment they publish. Webmentions, the W3C-standardised protocol that allows one site to notify another when it has linked to it, close the feedback loop: responses on other sites can be pulled back to the origin, so the conversation is not stranded on a third-party server. Together, these two standards give POSSE publishers both outbound reach and inbound signal without surrendering the canonical post.

Developers who have publicly adopted POSSE as a daily practice include Tantek Çelik, one of the IndieWeb's most vocal architects, whose site at tantek.com has operated on this principle for years. Brent Simmons, the developer behind NetNewsWire, runs inessential.com on the same model. Manton Reece built Micro.blog explicitly to lower the friction of POSSE-style posting for non-technical users, offering built-in RSS and cross-posting to the Fediverse and other platforms as first-class features.

From the record

Key concepts

  • POSSEPublish on your Own Site, Syndicate Elsewhere; IndieWeb practice making personal domains the canonical content source
  • WebmentionW3C protocol pulling cross-site responses back to the originating post
  • Canonical URLthe authoritative, owner-controlled address a syndicated copy points back to

Practitioners named

  • Tantek ÇelikIndieWeb architect; tantek.com is a long-running POSSE example
  • Brent SimmonsNetNewsWire developer; inessential.com
  • Manton ReeceMicro.blog founder; built POSSE-friendly cross-posting into the platform

The argument POSSE makes is not purely technical. Platform lock-in — the loss of follower graphs, post archives, and URLs that occurred when services like Google Reader, Vine, or App.net shut down — is the cautionary backdrop. Publishing to a domain you control means that the open web's syndication infrastructure carries copies of your work outward, but nothing about your content's existence depends on any single platform staying alive or staying friendly.

For publishers already running RSS feeds, POSSE requires no new infrastructure. The feed is already there; it simply becomes the source of record rather than an afterthought.