Own Your Real Estate: Why I Stopped Renting My Audience
written by Stefan Christoph
- 7 minutes readYou Are a Tenant and You Don’t Know It
Picture pouring a year into renovating an apartment. You knock down walls, pick every fixture, build the kind of place people actually want to visit. Then one morning the landlord repaints the lobby, reshuffles the hallways, and decides your guests now walk past three billboards before they reach your door. You don’t get a vote. You never did. You were always a tenant.
That is what publishing on a platform you don’t control feels like, and most of us do it without noticing. You write a good post, the feed rewards it, and the dopamine says “this is working.” What you don’t see is the lease. The platform owns the address. It owns who sees your work, in what order, next to which ads. It can change the rules tomorrow, and your only recourse is to keep paying rent in the currency it accepts: more posts, more engagement, more of your time.
I publish on social platforms too. I am not against them. But I stopped treating them as home.
The Move: Own the Original, Send Out Copies
The fix is almost embarrassingly simple. Publish the real thing once, on a site you own. Then send copies out to every feed where your readers already are, each one linking back to the original.
This pattern has a name. The IndieWeb community calls it POSSE: Publish on your Own Site, Syndicate Elsewhere [1]. The order is the whole point. The canonical copy lives at an address you control. The social posts are billboards on someone else’s highway, and every billboard points home.
POSSE: the canonical copy lives on your site, and every syndicated copy points back to it.
Invert that, put the platform in the middle instead of your site, and you get the model most of us drift into by default: the platform holds the relationship with your readers, and your reach lives entirely at its mercy. Same content, opposite power structure.
To be clear about what “own” means here: it is not a server humming in your basement. My site runs on cloud infrastructure, and that is exactly the point. Owning the canonical copy is about owning the domain, the URL, and the relationship with the people who read you. Where the bytes physically live is a neutral, solved problem. Cloud hosting is what makes owning your home base cheap and easy: a domain costs a few dollars a year, and a managed host stands a site up in an afternoon with no servers to babysit. That is not an elite move anymore, and not something to apologize for.
How I Actually Do It
My rule is website first, social second. When I have something to say, it goes up as a full post on my own site. Only then do I write a short teaser for the feed, and that teaser exists to do one job: send people back to the original.
I keep a steady rhythm to it. Three posts a week, the long version on the site, the short version pointing to it. The teaser earns the click; the site keeps the asset. The teaser sometimes travels less far than a post that keeps people inside the feed, because a link pointing away can cost you reach. I take that trade on purpose: I would rather fewer people land on something I own than more people bounce off something I rent. None of this is heavy machinery. It is a habit and an order of operations, and the order is what makes it work.
The reframe took a while to sink in for me. For a long time I measured a piece by how the feed reacted to it that afternoon. Now I measure it by whether, a year from now, it still lives at a URL I can point someone to. Those are very different bets, and only one of them is mine to keep.
What Owning Actually Buys You
This is not principle for its own sake. Owning the home base pays off in concrete ways:
- A durable URL. The post has one permanent address. It does not vanish in an algorithm reshuffle or a platform’s pivot, and I can link to it for years.
- Full control of the format. No character ceiling, no banned link, no forced layout. A diagram renders the way I drew it. Code stays code. The work looks the way the work should look.
- An audience I can actually reach. A reader who joins my list is mine to reach directly, without bidding for permission to land in a feed I don’t run.
- My own numbers. I see what people read and how they got there, instead of squinting at whatever metrics a platform decides to show me this quarter.
None of these are dramatic on any single day. Compounded over years, they are the difference between owning an asset and renting attention.
Owning is a spectrum, not an absolute. A domain and an email list still lean on registrars and inbox providers, so nobody controls everything. The useful test is portability: if a provider turns hostile, can you leave with your address and your readers intact? With a domain and an exported list, largely yes. With a follower count locked inside a feed, no.
“This Is for Everyone”
There is an older idea underneath all of this. When Tim Berners-Lee was honored at the 2012 London Olympics opening ceremony, he sat at a computer in the middle of the stadium and sent four words across the world: “This is for everyone” [2]. The web he invented was meant to be open and owned by all of us, not parceled out as plots we rent from a handful of landlords.
Publishing on your own site is a small, practical way to live that out. You are not asking permission to exist online. You have an address. The open web still works exactly as designed: anyone can stand up a page, and anyone can link to it. The platforms are useful distribution, and I use them gladly. But they are roads, not real estate.
Build on Land You Own
So here is the honest version of the advice I keep giving myself. Keep posting to the feeds. They are genuinely good at putting work in front of strangers, and reaching them matters. Owning the home base does not replace that reach; it keeps the asset and the relationship after the feed has scrolled on. Just stop building your house on rented ground. Write the real thing where you own the address, then let the feeds carry copies of it home.
Your work is worth more than a lease you don’t control.
Where does the canonical copy of your best work live right now? On a domain that is yours, or on a platform that could change the locks tomorrow?
Sources
[1] POSSE — Publish on your Own Site, Syndicate Elsewhere (IndieWeb) — names the publish-canonical-then-syndicate pattern and the ownership case behind it.
[2] This is for Everyone: the Tweet Heard Around the World (W3C) — Tim Berners-Lee’s “This is for everyone” message at the 2012 London Olympics opening ceremony.
About the Author
Stefan Christoph is a Principal Solutions Architect at AWS, focused on agentic AI, media & entertainment, and helping builders move from demo to production. He writes about AI architecture, developer productivity, and the future of software.
This is a personal blog. Opinions expressed here are my own and do not represent the views or positions of my employer.
❤️ Created with the support of AI (Kiro)