The web used to be a place.
We turned it into a channel.

There's a moment many of us have forgotten. You visited a website — a fan page, a forum, a blog — and you knew there were other people there right now. Not as an abstract number. As a presence.

Maybe someone was typing while you were reading. Maybe someone had found the same page as you, at the same hour, from the same impulse.

That wasn't a feature. That was architecture.

The early web thought in spaces. Websites were places you entered. You went into a forum, you didn't scroll through it. You were in a chat, you didn't consume content. These metaphors weren't arbitrary — they reflected the structure the web actually had: you were somewhere, and others were there too.

How a place became a channel

At some point, this shifted. Not by decision, not overnight. More like a geological movement — imperceptible, irreversible, and only visible in hindsight.

Platforms didn't replace the web. They layered themselves on top of it. They replaced the logic of place with the logic of a channel: no more where, only a when. Not a space you move through, but a stream that flows past you. The subject shifted — no longer the user navigating, but the feed arriving.

This isn't a complaint about the past. It's an observation about architecture.

Replacing places with channels changes what's possible inside them. In a place, encounter can happen — unplanned, situational, between people who just happen to be at the same spot. In a channel, there is no encounter. There is reach. There is engagement rate. There is the algorithmic funnel that decides who sees whom — and why.

The question isn't whether platforms are bad. The question is what we lost when we stopped thinking of the web as a space.

What architecture does to behavior

Spaces produce different behavior than channels. That's not speculation; that's design theory. A space has boundaries — it begins and ends somewhere. It has a locality. It isn't open to everyone all at once; it has a capacity, an atmosphere, a history.

A channel has no history. It has only currency. What was there yesterday is gone — archived at best, invisible most of the time. What's happening now is everything.

Spaces allow return: you come back, you meet the same people again, you have context. Channels reward novelty: new is good, old is dead, attention is fleeting.

That explains part of what many people experience as a thinning-out of digital life — without quite being able to name it. It isn't the noise. It's the absence of place.

The blind spot of platform critique

When people talk about the problem with social platforms, they usually talk about content: misinformation, polarization, addictive design. These are real problems. But they're symptoms of a deeper decision.

The deeper decision was: build channels, not spaces.

Channels scale. Spaces don't — at least not the way growth logic understands scaling. A space that gets too big stops being a space. A channel can grow indefinitely; it just gets louder, not broken.

For platforms, place-logic was never interesting. It's too local, too slow, too hard to monetize. So it was quietly abandoned — in favor of an architecture optimized for global reach that systematically excludes encounter.

What if the web were a place again?

Not nostalgically. The early web had its own problems. Access barriers, technical exclusion, lack of accessibility. None of that is desirable.

But the underlying question is. What if a website — any website you're reading right now — could know there are other people there too? Without a platform as middleman. Without an algorithm as gatekeeper. Just: you're here, others are also here, you're at the same place.

It changes nothing about the content. It changes the architecture. And that — slowly, not spectacularly — changes what's possible.

The question isn't: do we want the early web back? The question is: why did we stop asking why the web stopped being a place?