▌ Phosphor

The Internet You Visit on Purpose

August 2, 2026

There’s a feeling people have about the old internet that they can’t quite name. They remember it — or feel like they should remember it — as a place you went. You connected to something. You arrived somewhere. You were there on purpose, and when you were done, you left.

The modern internet doesn’t work like that. It comes to you. It’s in your pocket, on your wrist, in your glasses. It pushes notifications, feeds, stories, reels, alerts. You don’t visit it. It visits you — constantly, relentlessly, whether you asked it to or not.

People are tired of that. They’re tired of algorithms deciding what they see. Tired of platforms that change the rules when they go public. Tired of their communities being rented from companies that can sell them out at any moment. They want something that feels like a place again.

That thing existed. We called it a BBS.

What we had

In the 1980s and 90s, you’d dial into a Bulletin Board System — a computer someone ran in their house, their office, their school. You’d connect to a specific place, at a specific phone number, and arrive in a community. There were message boards, chat, games, file downloads. There was a sysop — the person who ran the BBS — who was often in the chat themselves. It was small, personal, and intentional.

You went there on purpose. You didn’t scroll past it. You chose to be there.

The BBS was the original digital third place. Before that term existed, before social media, before “engagement metrics” — there was a room you connected to, with people you knew, where conversation was the main activity and the person who ran it was a regular, not a corporation.

Then the web happened, and BBSes faded. Not because they were bad — because dial-up was slow, phone bills were expensive, and the web was bigger and easier. The technology moved on. But the need that BBSes served — community, conversation, a place that was yours — didn’t go anywhere. It just went unmet.

What we lost

The modern internet solved the technology problem. It created a new one.

Social media turned community into content. Discord turned community into a product. Slack turned community into a workplace tool. Each one is a third place that someone else owns. You build your community on their platform, under their rules, and they can change the deal whenever they want — ship ads, go public, raise the price, shut it down, sell your data.

The pattern is always the same:

  1. Platform launches, free and open
  2. People build communities on it
  3. Platform grows, takes investment, goes public
  4. Shareholders need growth, so the platform monetizes the communities people built
  5. The community becomes ad inventory. The third place becomes a store.

This happened to AIM. It happened to early Reddit. It’s happening to Discord right now — they went public in January 2026, shipped ads, had a data breach, and introduced age verification. The community you built there isn’t yours. It’s theirs, and they’re letting you use it until the quarterly numbers need a boost.

We didn’t just lose BBSes. We lost the idea that a community could be yours.

What changed

Here’s what’s different now: the technology to run a real community server is available to anyone. You don’t need a data center. You don’t need Big Tech. You don’t need AWS or Google Cloud or a venture capital round.

A BBS used to require a dedicated phone line, a modem, and a computer running 24/7 in someone’s house. Now it requires a $5/month VPS or a Raspberry Pi in your closet. The barrier to entry didn’t just drop — it disappeared.

The tools got better too. Modern Java, real-time WebSockets, reactive UIs, federation protocols. A BBS in 2026 isn’t a static page of text files. It’s a living, reactive space — screens update in real time, chat is instant, mail is delivered the moment it’s sent, and you can customize everything without recompiling or restarting.

What we kept from the BBS era: the design pattern. A place you connect to. A community you belong to. A server you own. Boards, not feeds. Regulars, not followers. Conversation, not content.

What we added: the modern stack. Real-time reactivity. A scripting language. Federation. Web access alongside terminal. Any screen size, any device.

Same need. Better tools.

Intentional community

The word that captures all of this is intentional.

A BBS is intentional in every direction:

You connect on purpose. You SSH in, or point your browser at a URL. You don’t get a push notification. You don’t scroll past it in a feed. You go there because you want to be there, the way you’d go to a pub or a café. It’s a place you visit, not a stream that comes to you.

The community is intentional. It’s not an algorithmic feed of strangers. It’s boards and channels with regulars who know each other. People who notice when you’re gone. Conversations that build over time, not posts that disappear in 24 hours.

The server is intentional. Someone chose to run it. Someone configured it. Someone is the sysop. It’s not a SaaS product — it’s a place that a person made. The community shapes the space, because the person who runs it is in the room.

The boundaries are intentional. This is where federation changes everything.

Local and global at the same time

The tension every community feels: you want to be part of something bigger, but you also want your own space. You want the reach of a global network, but you want to keep things local.

Discord makes you choose: one platform, one set of rules, everything public to anyone who joins your server. Mastodon makes you choose: one instance, one admin, everything visible to the fediverse.

Phosphor doesn’t make you choose. Federation lets you have both.

Every board, every channel, every resource has a federated flag. Set it to true, and that board syncs across every node you’re peered with — a post on your server appears on servers across the internet in real time. Set it to false, and it stays on your server. Forever. It never leaves. It’s not replicated, not exported, not visible to anyone outside your node.

board "General Discussion" {
    description = "Open to everyone"
    federated = true
}

board "Family Office" {
    description = "Local only — not federated"
    federated = false
}

Two boards. One global, one local. Same server, same community, same sysop. You decide what crosses the wire and what stays home.

This is the BBS pattern, updated for a connected world. In the 90s, your BBS was an island — everything was local because there was no network. FidoNet let you exchange messages with other BBSes, but it was slow and limited. Phosphor makes federation real-time, automatic, and granular. You’re connected to a larger community, but your local space stays yours.

The sysop controls the boundary. Not a platform. Not a company. The person who runs the server — who is in the chat, who knows the regulars, who built the place.

Anyone can run one

This is the part that matters most.

You don’t need to be a developer. You don’t need to know Java. You don’t need a cloud account or a credit card with a tech company. You need a computer and an internet connection.

Run it on a $5 VPS. Run it on a Raspberry Pi. Run it on the machine in your closet. Phosphor runs on Postgres or H2 (embedded, zero-setup, auto-detected). The entire BBS is configured in a readable language — you write .phos files, save, and the BBS updates instantly. No recompile, no restart, no DevOps pipeline.

Connect via SSH for the terminal experience. Connect via web browser for the same BBS without a client. Connect via Telnet if you’re running vintage hardware. Same users, same data, same real-time everything.

Your data stays on your server. Not sold. Not harvested. Not analyzed. Not sent to an ad network. Not stored in a data center owned by a company that went public last quarter.

This is what self-hosting means when it’s done right: not a hobby for Linux nerds, but a practical way to own your community the way you own your home. You don’t rent your third place from a public company. You build it.

The same need, served properly

People aren’t looking for a BBS. They don’t know what a BBS is. They’re looking for what a BBS was: a place to belong that they control, a community that’s theirs, a space that doesn’t get sold out from under them.

For thirty years, the technology wasn’t there to deliver that at scale. The tools were too hard, the infrastructure too expensive, the interfaces too primitive. So we settled for Discord and Reddit and Facebook — rented third places that felt close enough.

The tools are here now. The infrastructure is cheap. The interfaces are modern. The need hasn’t changed.

A BBS was never about modems and phone lines. It was about intentional community — a place you visited on purpose, run by someone you knew, where the conversation was the point and the data was yours.

That’s what we’re building. Not a nostalgia project. The same need, served properly, with forty years of hindsight and modern tools.

Connect. Build one. Make it yours.

ssh phosphorbbs.net -p 2222

This is part of our series on digital third places. Read the first piece: What Is a Digital Third Place?

Tags: #digitalthirdplace #socialterminal #communityserver #federation #selfhosted