At some point I started thinking: where does my content actually live? A post in Telegram lives on Telegram’s servers. An article on Habr lives on Habr’s servers. A thread on X lives with Elon. If tomorrow any of these platforms decides to change the rules, ban my account, or simply shuts down — I’ll be left with nothing.
That’s when I came across a principle that the IndieWeb community has been promoting for many years. It’s called POSSE. It sounds simple, but it completely changes how you think about publishing content.
What is POSSE
POSSE stands for Publish (on your) Own Site, Syndicate Elsewhere.
In plain terms: publish on your own site first, then spread it to other platforms.
The idea is straightforward:
- You write a post and publish it on your own website — this becomes the canonical version.
- Then you distribute copies or links to third-party platforms — Habr, Telegram, X, Medium, whatever.
- Every copy links back to the original on your domain.
That’s it. That’s the whole principle.
Why you need it
Ownership of your content
When you publish on someone else’s platform, the canonical URL belongs to them. Your content lives on their domain, under their rules and their Terms of Service. POSSE flips this around: the canonical URL lives on your domain. You own the entire publishing chain from start to finish.
Independence from third parties
A platform can go down, ban your account, or change its algorithms. If your content only exists there, you’re completely dependent on them. With your own site, you can always publish, even if everything else is unavailable.
Better search visibility
Finding your public content through any search engine is much easier and more reliable when it lives on your own domain. Anyone who has tried to find their old tweet via X search knows how painful that can be.
Links to the original strengthen it
When copies on other platforms link back to your original, several good things happen:
- Discovery. People on any platform can click through to the original and interact with it directly.
- Protection against copying. If someone mindlessly copies your post, the link to the original travels with it. This works like “internet aikido” — other people’s copying actually promotes your original.
- SEO. Search engines see that multiple copies point to one source and rank the original higher.
Friends are more important than architecture
Your readers are scattered across different places. Some are in Telegram, some on Habr, some use RSS. POSSE doesn’t force them to go anywhere — they can keep reading where they’re comfortable. But the canonical version is always on your site.
The IndieWeb community puts it this way: “Friends are more important than federation.” You don’t have to wait for everyone to move to the perfect platform. Publish on your site and syndicate where your audience already is.
How POSSE is different from “just having a blog”
POSSE is not just “start a blog.” Creating a blog and waiting for people to come doesn’t work. POSSE is active syndication: you publish on your site first, then deliberately bring the content to where the people are.
And it’s not “install WordPress and you’re done.” The approach isn’t tied to any specific technology. You can use a static site built with Astro, Hugo, Next.js — anything. The important things are your own domain and canonical URLs.
The opposite approach: PESOS
The opposite is called PESOS — Publish Elsewhere, Syndicate (to your) Own Site. This is when you publish first on a third-party platform and only then copy it to your own site.
The problem with PESOS: if the platform is down, you can’t publish. Your content first appears under someone else’s Terms of Service, and only later (maybe) ends up with you. The ownership chain is broken.
POSSE solves this: the original is always with you, and the copies are wherever they need to be.
How it looks in practice
Let’s say I’m writing an article. My POSSE workflow looks like this:
- I write and publish the article on my own website — it gets a canonical URL on my domain.
- I publish a version on Habr — with a link to the original.
- I make a post in my Telegram channel — with a link.
- I publish a thread or link on X — with a link.
- If there’s engagement on the platforms, I can pull reactions back to my site (this is called backfeed).
There’s one canonical version. There can be as many copies as you want. All of them point to the original.
My experience
I created my own website specifically with this idea in mind. I wanted everything I write to have a permanent home — a place that doesn’t depend on decisions made by any platform. Articles, notes, projects — everything lives on my domain. Habr, Telegram, and other platforms become distribution channels that link back to the original.
This doesn’t mean the platforms aren’t important. Habr is the community and discussions. Telegram is direct contact with readers. But if something changes tomorrow, my content isn’t going anywhere.
This material is based on the IndieWeb documentation: IndieWeb POSSE.
Support
If you want to support the author — subscribe to my Telegram channel. It’s shorter, more frequent, and doesn’t require registration.