Rooms, Not Broadcasts
Build-log entry this time — less thesis, more workbench.
Big social defaults to broadcast. One post, maximum reach, every audience at once. Your joke lands in front of your college friends, your coworkers, your aunt, and forty thousand strangers, and it's supposed to mean the same thing to all of them. Researchers call the resulting mess context collapse: when a sentence has to survive every possible audience, you stop writing sentences worth surviving. Everyone becomes their own press office.
The fix we're building around is old and boring, which is a compliment: rooms.
What a room is
A room is a small named context. The people in it know why it exists — the family room, the Tuesday hikers, the three friends who argue about guitars. When you post, you post into a room, and the sentence gets to mean what you meant, because everyone reading it shares the context you wrote it in.
Some design decisions that came out of this, and the reasoning behind them:
- A post belongs to one room. No cross-posting, no share button that lifts your words out of the context that made them make sense. If something's worth telling two rooms, you tell it twice — probably differently, the way you would in person. The retelling is the feature.
- Rooms are tabs, not algorithms. You pick which room you're in the way you pick which conversation to walk into. No model guesses which room "deserves" your attention or blends them into one optimized gruel. The unread state is a quiet dot, not a red number engineered to itch.
- No global firehose. At all. There is no main feed of everything on the site, which means there is no stage, which means there is nothing to perform on. The post you write for six people reads like it was written for six people. That tone — relaxed, specific, unguarded — is the entire product, and a firehose would kill it in a week.
What's genuinely unsolved
Being honest about the bench, because this is a rebuild and pretending otherwise would break our own rules:
- Discovery without virality. How does a good room find the two more people who belong in it, without building the share-and-amplify machinery we just swore off? Every mechanism we sketch either does too little or quietly reinvents a growth loop. Current best idea is plain human invitation — a person vouching for a person — but we haven't nailed how that should feel in the product yet.
- Moderation at dinner-table scale. Small groups mostly self-regulate, which is a gift. But "mostly" is carrying weight in that sentence. What happens when the problem is the host? When two people in a six-person room stop speaking? Platform-scale tools — report queues, strike systems — are absurd at this size, like calling security on your own dinner party. We think the answers look more like social conventions the software respects than enforcement the software performs. We are not confident yet, and we're saying so.
On the bench next
Quieter notification defaults (a room should be able to say "weekly digest is fine"), and the caught-up line for room feeds — the one from the last post — which is designed, half-wired, and not yet lit.
More when there's more.