Why online communities die
— and what we built instead.

Online communities don't die because people stop caring. They die because they were built on borrowed ground.

Building a community on a platform is like opening a guesthouse in a rented building. The guests come, the atmosphere builds, real relationships grow. But the building belongs to someone else. And when the owner raises the rent, changes the rules, or tears the place down, the community is gone — not because it was weak, but because its foundation was never theirs.

This isn't an edge case. It's the structural problem behind dozens of community collapses over the last ten years. Platform decisions — algorithm changes, API shutdowns, moderation rules, fee structures — have destroyed communities that took years to build. The members went elsewhere. The connections dissolved.

The structural problem has a name

There's a term for it in platform economics: dependency risk. You build on a platform, you know you're dependent, you hope it goes well.

Most of the time, it goes well for a while. Platforms are generous in the early phase — open APIs, favorable terms, active support for community-building. That changes when the growth phase ends and the pressure to monetize takes over.

That's not fraud. It's business-model logic. Platforms need revenue. Communities are the content they sell. Once you understand that, you understand why the conflict of interest is structural — not because of bad intent, but because of how the business model is built.

The question that follows: is there an architecture that avoids this conflict — not through better platform governance, but through a different underlying structure?

Heiner's first answer — and its end

Heiner Wolf asked this question for the first time in 2007. His answer was a browser plugin that turned webpages into rooms — not on a central platform, but as a layer on top of the existing web. Every page became a place where visitors could see and talk to each other. No platform as middleman. No central operator.

The project found an audience. Then it was acquired, absorbed, and eventually shut down. The idea didn't survive in infrastructure — but it survived in the question.

Seventeen years later, the question is the same. The conditions are different.

What's changed

In 2007, browser-extension technology was new, unstable, and limited to a small technical audience. The thought of building community infrastructure on a layer was radical and hard to communicate.

In 2026 it's different. Browser extensions are everyday tools. Open-source infrastructure is proven. And awareness of platform dependency has grown — through a series of community collapses, API shutdowns, and algorithm shocks that affected millions of users directly.

The idea is the same. The conditions are ready.

What we built

weblin is a layer on the web. A browser extension for Chrome, Edge, and Firefox — and a mobile app — that turns every webpage into a small, living community. Anyone visiting the same URL sees the others. No algorithm decides who sees whom. No platform owns the connection. No central operator can shut the community down.

The code is public. The project is funded by Kickstarter — community before investors. Whoever backs it, decides what gets built next.

The four principles we build on:

This isn't a counter-strategy to existing platforms. It's a different question: what if community didn't have to happen on borrowed ground? What if every webpage was the place itself — without a middleman, without dependency, without conflict of interest?

Communities die when the foundation falls away. We tried to build a foundation that belongs to no one — and so cannot be taken from anyone.

The extension is live. To take a look: weblin.io