One Platform for Three Things You're Doing in Three Places

August 2, 2026

You use three different tools for three different kinds of communication. You probably don’t think about it this way, but you do.

Slack or Discord for chat. Real-time, instant, conversational. You’re talking with people right now. Messages flow, responses come in seconds, the conversation moves fast. It’s great for “what are we doing right now” and terrible for “what did we decide last month.”

X or Mastodon for broadcasting. One-to-many, short-form, public. You’re talking at people. A post goes out, it reaches followers, replies trickle in. It’s great for “look at this” and terrible for “let’s discuss this in depth.”

Reddit or a forum for discussion. Threaded, persistent, slow-paced. You’re talking with people over time. A post today gets replies tomorrow, next week, next month. It’s great for “let’s think about this” and terrible for “who’s here right now.”

Three tools. Three accounts. Three silos. Three companies that own your data, control your experience, and can change the deal whenever they want.

What if one platform did all three?

The three modes

Every online community needs three communication modes. Not one mode done three ways — three genuinely different modes, each serving a different need.

1. Real-time chat

Instant, ephemeral, conversational. You’re present, other people are present, and you’re talking together right now. The value is immediacy — “who’s here,” “what’s happening,” “let’s figure this out together.”

Slack does this well. Discord does this well. But that’s all they do. Their “threads” are a bolted-on attempt at discussion that doesn’t work because the medium fights the message — chat scrolls away, threads get lost, and by tomorrow nobody can find what was said today.

2. Broadcast

Short-form, public, one-to-many. You post something, it reaches an audience. The value is reach — “look at this,” “here’s what I’m thinking,” “this just happened.”

X does this well (sort of). Mastodon does this well. But that’s all they do. Their “replies” aren’t discussion — they’re noise. There’s no threading, no depth, no room for a real conversation to develop over time. And the engagement metrics (likes, retweets, follower counts) gamify every interaction, turning communication into a competition for attention.

3. Topic discussion

Threaded, persistent, in-depth, slow-paced. You post something, people reply over days or weeks. The value is depth — “let’s think about this,” “here’s my analysis,” “what does everyone think about this idea.”

Reddit does this well. Old forums did this well. BBS message boards did this well. But that’s all they do. Reddit’s “chat” is terrible. Forums have no real-time presence. You post and walk away — there’s no “who’s online right now.”

What every platform gets wrong

Each platform does one mode well and bolts the others on badly:

• Discord added threads (bad discussion) and announcements (bad broadcast). The core is chat. Everything else is an afterthought.
• Slack added channels for discussion, but they’re just chat with a name. No threading, no persistence, no depth.
• Reddit added Chat (terrible) and keeps trying to make the platform feel real-time. The core is discussion. Chat is an afterthought.
• X added Communities (bad discussion) and Spaces (audio chat). The core is broadcast. Discussion is an afterthought.
• Mastodon is broadcast only. No real-time chat. No threaded discussion. It’s a one-mode platform.

The pattern is always the same: start with one mode, bolt on the others, and pretend you’re a complete platform. The bolts always show.

What a BBS gets right

A BBS was never one mode. It was always three:

• Chat — real-time channels, wall messages, multi-user chat. You knew who was online.
• Broadcast — the wall. Short public posts visible to everyone on the node. One-to-many, fast, public.
• Discussion — message boards. Threaded, persistent, deep. Post today, reply tomorrow, the conversation builds over weeks.

The BBS did all three because it was designed as a community platform, not a communication tool. A community needs all three modes. A tool only needs one.

Phosphor inherits this. Real-time chat channels, message boards for discussion, and a broadcast wall for short-form public posts. Three modes, one platform, one server.

The broadcast wall

The wall is the piece that’s been missing — the X/Mastodon mode, done the BBS way.

A wall is a chronological feed of short posts visible to everyone on your node. You post, it appears, everyone sees it. But it’s different from X in the ways that matter:

• No algorithm. Chronological. What you see is what was posted, in the order it was posted. No engagement-optimized feed deciding what you should see.
• No metrics. No like counts, no follower counts, no retweet counts. A post stands on its content, not its numbers. The absence of metrics is the point — it removes the gamification that makes social media toxic.
• No ads. No promoted posts. No sponsored content. Your wall is yours.
• ANSI art as media. A wall post can include colored text, ASCII art, figlet banners. The “media” of a terminal is text art — expressive in a way images can’t be in a 80×24 grid.
• Federated. Your wall syncs with peer nodes. A post on your node appears on federated nodes in real time. But you control what federates — local walls stay local, public walls go global.

wall "Public" {
    description = "Node-wide broadcast feed"
    federated = true
    max_length = 500
}

The sysop decides what federates. Not a platform. Not an algorithm. The person who runs the server.

Integrated search: the thing nobody has

Here’s the part that sounds boring but is actually the killer feature.

When you use three tools for three modes, you can never find anything. The conversation you had in Slack? Gone — it scrolled past weeks ago. The thread on Reddit? You’ll never find it again. The post on X? Buried by the algorithm. Each tool has its own search, and each search is bad.

Discord’s search is notoriously slow and incomplete. Slack’s search only works within one workspace. X’s search is limited and algorithmic. Reddit’s search misses older content. Every platform’s search is bad because every platform’s data is a silo — they can only search their own mode.

A BBS has a natural advantage: everything is in one database. Board posts, chat messages, wall posts, mail, file descriptions — all structured, all indexed, all on the same server. One search query, results from everywhere.

/search "federation"

📋 BOARDS (3 results)
  1. "Federated BBS: Multi-Node Sync" — General / joe
  2. "Re: Federation testing" — Dev / najee
  3. "Federation protocol question" — Tech / amelie

💬 CHAT (7 results)
  4. #dev 2:15 PM — joe: "federation to Ohio is live!"
  5. #general 1:45 PM — najee: "how does federation handle conflicts?"

📢 WALL (2 results)
  6. @joe 2:15 PM — "Just deployed federation to the Ohio node..."
  7. @najee 2:18 PM — "Nice! Seeing posts from Bronxville..."

📁 FILES (1 result)
  8. federation-protocol.pdf — Dev docs / sysop

One search. Every mode. Results ranked by relevance, grouped by type. Click through to the original — the board post, the chat message, the wall post. All in one place.

This is what happens when your community platform is actually a platform, not a chat app with delusions of grandeur. The data isn’t scattered across three products owned by three companies. It’s in one database on one server that you own.

The pitch

Chat like Slack. Broadcast like X. Discuss like Reddit. Search across all of it. All in one place. All yours.

No competitor can make this claim because no competitor does all three:

The reason is structural. Discord, Slack, X, Reddit, Mastodon — each started as one mode and tried to add the others later. The architecture fights the addition. You can’t add real discussion to a chat app without redesigning the data model. You can’t add real-time presence to a broadcast platform without rebuilding the backend.

A BBS was designed as a community platform from the start. Three modes were always part of the architecture. The database schema supports all three natively. The UI surfaces all three. The federation protocol carries all three.

That’s the difference between a communication tool and a community platform. A tool does one thing. A platform serves a community — and a community needs all three.

ssh phosphorbbs.net -p 2222

Part of our series on digital third places. Read the hub: What Is a Digital Third Place? | Previous: The Third Place Problem With Discord

Tags: #digitalthirdplace #socialterminal #communityserver #enshittification