The Pendulum Swings Back

For over a decade, the internet consolidated into a handful of walled gardens. Publishers shuttered their blogs to write on social platforms. Developers abandoned personal domains for repository hosting. Communities migrated from forums to messaging servers they didn't control. The trade-off seemed worth it: reach, convenience, free infrastructure. But the pendulum is swinging back — hard.

The conversation dominating technology circles right now isn't about which new platform to adopt. It's about how to own your digital presence again. The open web revival isn't nostalgia; it's a structural response to platform risk that every creator and developer has now experienced firsthand.

What Triggered the Exodus

Three shifts happened in rapid succession that broke the social contract between platforms and their users:

• Enshittification went from theory to lived reality. The term, coined by Cory Doctorow, describes the predictable lifecycle of platforms: first they serve users, then they exploit users to serve advertisers, then they exploit advertisers to serve shareholders. Every major platform is now in the exploitation phase.
• Algorithmic feeds destroyed predictable reach. Creators who built audiences of hundreds of thousands discovered their content could be silently suppressed overnight. When distribution is rented, it can be revoked without explanation.
• API lockouts killed developer trust. Multiple major platforms restricted or eliminated third-party API access within months of each other. Developers who built ecosystems around these platforms were left with broken integrations and stranded users.

The pattern is the same every time: platforms subsidize growth with openness, then wall off the garden once the network effect is locked in. The open web revival is the collective decision to stop falling for it.

The Architecture of Independence

This isn't about deleting accounts and going off-grid. It's about changing the primary node. Instead of a platform profile being your home and a personal site being a link in your bio, the personal site becomes the home and the platform becomes a distribution channel you can switch off without losing everything.

Personal Websites as the New Minimum

The personal website is back, but it looks different from the geocities era. Modern personal sites are:

1. Dynamic content hubs — not static resumes, but living documents with notes, essays, project logs, and reading lists that evolve continuously.
2. IndieAuth endpoints — using your domain as your identity across the web, replacing platform-specific logins.
3. Webmention receivers — aggregating conversations and responses from across the decentralized web, not just within one platform's notification system.
4. Microsub readers — pulling content from RSS and Atom feeds into a personal reading environment, bypassing algorithmic curation entirely.

RSS as the Unexpected Comeback

RSS never died, but it's experiencing a renaissance that surprises even its longest advocates. Newsletter platforms now auto-generate feeds. Blog engines ship with feed support by default. The infrastructure that made RSS feel obsolete — social platforms aggregating content — is the same infrastructure that's now unreliable, pushing people back to direct subscriptions.

The feed isn't just a format. It's a contract between publisher and reader that no algorithm can rewrite.

Self-Hosted Infrastructure Goes Mainstream

Five years ago, self-hosting meant spending weekends configuring servers and babysitting daemons. Today, containerization and one-click deployment tools have lowered the barrier dramatically. Developers are running their own Git instances, analytics platforms, bookmark services, note-taking tools, and media servers — all on hardware or VPS instances they control.

The motivation isn't just ideology. It's pragmatism:

• Data portability. When your notes, bookmarks, and code live in your own database, you can migrate, back up, or export at will. No export limits, no format lock-in, no terms of service preventing bulk downloads.
• Longevity. Self-hosted tools don't get sunset when a startup runs out of funding. If the maintainer stops updating, you can fork, patch, or migrate on your own timeline.
• Privacy by architecture. Not trusting a platform with your data isn't paranoia — it's pattern recognition. Self-hosting eliminates the data-harvesting business model by removing the intermediary entirely.

The IndieWeb Protocol Stack

Beneath the cultural movement is a growing technical stack designed for decentralization:

• Webmention — enables cross-site conversations, replacing platform-specific comments and replies with an open standard.
• Microformats — structured data in HTML that machines can parse, making personal sites machine-readable without proprietary APIs.
• IndieAuth — uses your domain as your identity provider, letting you authenticate across services without relying on a corporate identity layer.
• Microsub — a standardized way to consume feeds, separating the reader client from the feed source.

These protocols share a design philosophy: your site is your primary representation on the web, and everything else flows from it. No single protocol is revolutionary on its own, but together they form a viable alternative to platform dependency.

The Economics of Owning Your Stack

The cost argument against independence has collapsed. A domain costs roughly ten dollars per year. Static hosting on edge networks is free for most personal traffic levels. A VPS capable of running dozens of self-hosted services costs five dollars per month. The total cost of owning your entire digital presence is less than a single month of most premium platform subscriptions.

The real cost isn't money — it's time and skill. You need to understand DNS, basic server administration, and web fundamentals. But for the developer audience already fluent in these skills, the barrier is essentially zero. And the return on that small time investment compounds: every piece of content you publish, every connection you make, every project you ship adds permanent value to a domain you own.

What This Means for Developer Culture

The open web revival is more than a trend — it's a values clarification. The developers building this movement are explicitly choosing ownership over convenience, longevity over virality, and interoperability over ecosystem lock-in.

This has practical implications for how teams build products:

• Shipping RSS feeds and open APIs isn't an afterthought — it's a feature that signals respect for your users' autonomy.
• Choosing protocols over platforms means your integration strategy prioritizes long-term stability over short-term growth hacks.
• Building with data portability in mind means your users stay because your product is good, not because leaving is painful.

The developers investing in the open web today are building the infrastructure the next generation will depend on. The platforms will continue to enshittify. The question is whether the alternatives will be ready when users reach their breaking point.

The Path Forward

You don't need to abandon platforms entirely. The smart strategy is post-and-syndicate: publish on your own site first, then distribute to platforms for reach. Your domain is the canonical source. Everything else is a read-only mirror you can redirect or shut off at will.

Start small. Register a domain if you don't have one. Set up a minimal site — even a single page with your name, links, and an RSS feed. That's enough to be part of the open web. From there, add incrementally: a blog, a note feed, Webmention support, self-hosted analytics. Each addition reduces your dependency on platforms that don't have your interests at heart.

The open web isn't a destination. It's a practice. And the best time to start practicing was twenty years ago. The second best time is now.