Most people do not really own their online identity. They rent it. They may have a username, a profile photo, a following, and years of posts. The address belongs to someone else. The rules belong to someone else. The archive sits in someone else’s database. If the company changes direction, sells itself, breaks search, locks an account, shuts down an API, or decides the old product no longer fits the business plan, the user gets to adapt.
That arrangement can work for a while. Platforms are convenient. They bring an audience, handle hosting, smooth over technical details, and make posting easy from whatever device is in your hand. There is a reason people use them. The mistake is treating a platform account as a permanent home.
The web already has a better answer: a domain name you control, a site you can move, and public formats that other tools can read. That does not require a huge operation. It can be a simple website, a blog, a static page, a small WordPress install, or any other setup that gives you a stable address and lets your work live somewhere under your own name.
A domain is not magic, and it is not ownership in the absolute sense. You still depend on registrars, DNS, hosting, certificate authorities, and the usual machinery of the Internet. You have to renew it, protect the account, and keep decent backups. Still, it gives you more control than a username on a commercial service. If a host becomes a problem, you can move. If a publishing tool stops fitting your needs, you can replace it. The address can stay the same.
That stable address matters more than people think. `example.com` can point to a blog today, a static archive tomorrow, and some future system years from now. Links can keep working. Feeds can keep working. Search engines can follow the move. Readers can bookmark the same place. The name becomes a durable handle for your work instead of a label inside a company town.
This is where RSS still earns its keep. A feed lets people subscribe to the site itself, not to a platform’s idea of what they should see. The reader chooses the software. The writer publishes at the source. There is no central feed ranking posts by whatever makes the service more money this quarter. It is plain plumbing, and plain plumbing is often what keeps a system useful.
Federation points in the same direction. ActivityPub, WebFinger, and related open-web tools let a site reach other spaces without making those spaces the center. A blog can have a Fediverse identity. A post can show up where people already read and reply. The important part is that the canonical copy remains on the author’s site. The platform becomes distribution, not possession.
Owning your online identity also changes how you think about archives. Platform posts tend to feel temporary even when they are technically public. They disappear into feeds, search gets worse, old links rot, exports are partial, and context gets lost. A personal site encourages a different habit. Posts can be revised, linked, grouped, tagged, backed up, and kept readable over time. The writing has a home instead of a shelf life.
There are tradeoffs. Running your own site takes work. You have to think about updates, spam, backups, certificates, hosting bills, accessibility, security, and the dull little maintenance tasks that platforms hide. You may get less built-in discovery. You may have to explain RSS to someone. You may spend an afternoon fixing something that a hosted service would have handled without asking.
That is the price of control. It should be admitted plainly, because pretending self-hosting is effortless helps no one. The goal is not to make every person run a server. The goal is to understand what is lost when every public identity lives inside accounts that can be renamed, rate-limited, hidden, sold, or closed.
There is a middle ground. You can own a domain and still use platforms. You can publish on your own site and syndicate elsewhere. You can keep a Mastodon account, a GitHub profile, a forum account, or a YouTube channel while making sure your real address points back to a place you control. Platforms are useful as outposts. They become dangerous when they are treated as the whole map.
The older Internet understood this more naturally. People had homepages, blogs, email addresses at domains they controlled, and links between independent sites. It was messier than today’s major platforms, and much of it was harder for new users. It was also more distributed. Your identity was less likely to be reduced to whatever one company allowed inside its profile template.
For a personal technology blog, this is not an abstract preference. The site itself is the point. RSS, federation, Webmentions, search, and social links are ways for other systems to find it and respond to it. They are not the source of identity. The source is the site, the domain, and the body of work gathered there.
Owning your online identity will not protect you from every failure. Domains lapse. Hosts close. Backups fail. People lose interest. Nothing on the Internet is permanent by default. But owning the address and keeping your work in portable forms gives you a fighting chance. It means your online life is not entirely bound to someone else’s product meeting.
That is the case for owning your online identity. Have a place that is yours in the practical, imperfect way the Internet allows. Publish there first. Let other systems subscribe, index, federate, and point back. Use platforms when they help, but do not let them become the only proof that you exist online.