Every few months someone on a forum asks what happened to IRC, and the answers split the same way: half explain that it never left, half explain why it had to. Both halves are right, which is why the question keeps coming back. (Bias note: this essay ends at a chat app we built. The first six sections are honest anyway.)
01 / THE ROOMWhat IRC actually was
Strip the nostalgia and the mechanics were austere: a nickname, a channel, a scrolling wall of monospace text, and slash commands for everything. No avatars. No profiles worth the name. No history — if you weren't there, you missed it, and that was fine.
The austerity was the design. A nickname instead of an identity meant you were exactly as interesting as your last message. Ephemerality meant presence — the channel was a place you were, not a feed you caught up on. And text-only meant the ambient hum of a hundred people typing never once asked you to look at anything. It ran for decades on hardware that would embarrass a doorbell.
02 / THE EXODUSWhy it emptied out — the half the eulogies get right
The essays arguing IRC can't come back have a point, and pretending otherwise is how you end up writing manifestos instead of software. The protocol shipped no persistent history: log off and the conversation never happened. No offline delivery. Identity was literally whoever held the nickname. Multi-device sync meant running a bouncer on a VPS — a system administration fee, paid monthly, for the privilege of chatting.
Normal people were never going to pay it. When Slack and Discord offered the same rooms with history, sync, and search included, the crowds moved for reasons that were simply correct. What the eulogies miss is what got charged on the way in.
03 / THE HOLDOUTSStaying: Libera, IRCCloud, and the bouncer tax
IRC still works, and for one demographic it works well. Libera.Chat carries thousands of channels, dense with open-source projects; the culture there is intact. IRCCloud turned the bouncer into a subscription — history and sync as a service, the single biggest usability hole patched with a credit card. Terminal clients are quietly excellent (Senpai on the desktop; Goguma even brings a real client to your phone), and web gateways like Kiwi cover the drive-by case.
If your channels still exist, this path is real. The honest catch: it solves IRC for people who already have somewhere to go. It doesn't answer where the new rooms are, because a protocol can't mint a crowd.
04 / THE HEIRSDiscord, Slack, and the attention tax
Discord kept the channels and fixed everything the eulogies list — then billed you in attention. Read receipts, typing indicators, reaction emoji, nitro nags, notification badges engineered to be cleared: a hundred small hooks that turn a chat room into a demand. IRC never once pinged you into anxiety. Its heirs made it the business model.
There's a second charge on the bill: ownership. You can't self-host Discord, can't fork it, can't export your community out of it in any meaningful way — the room belongs to the landlord now, and the rules change when the landlord's regulators do. The recent age-verification backlash sent a visible wave of users asking, in so many words, whether IRC was still an option. The impulse wasn't nostalgia. It was the sudden memory of what it felt like when the room was yours.
05 / THE COMPROMISEMatrix, federation, and the weight of everything
Matrix is the serious attempt to rebuild the open version: federated servers, bridges into IRC and elsewhere, encryption, history — the whole feature matrix, as it were. For communities that need sovereignty and modern chat, it's the credible answer, and it deserves its steady growth.
But spend an evening in it and you notice what federation costs: the heaviness of clients, the identity ceremony, the sense of operating infrastructure rather than hanging out. Matrix solved what IRC lacked. The thing IRC had — the weightlessness — wasn't on the roadmap.
06 / THE POINTWhat we actually wanted all along
Line the survivors up and the pattern inverts: every successor treated text as the limitation to engineer past — add voice, add video, add embeds, add presence, add everything. IRC's actual lesson was the opposite. Text was the feature. The constraint was what made a stranger's words land with full weight, made lurking comfortable, made the room accessible to a screen reader and a 2400-baud modem alike, made your identity weigh exactly as much as your last sentence.
What we wanted was never the protocol. It was: show up as a nickname, type, be judged on nothing else, leave without a trace. That's a culture, and cultures can be rebuilt anywhere.
07 / TODAYThe parts you can still have
This is where the disclosure cashes out. We built stdout.chat because we wanted that culture on the device that's actually in everyone's pocket: a terminal-style, text-only chat — monospace, dark, cursor blinking — where you exist as a nickname, run your life through slash commands, and every conversation is ephemeral by design. Matching is one-on-one by shared interests rather than channel topics (with one global channel, #void, for the ambient-hum crowd), there's no sign-up, and nothing survives the session. It is not IRC, and doesn't pretend to be: no federation, no self-hosting, iOS only. What it keeps is the part this essay is about — text as the feature, identity as a nickname, presence over permanence.
The honest routing table, then: your old channels → Libera.Chat, with IRCCloud if you value your evenings. Community infrastructure you control → Matrix. The feeling of the room, one stranger at a time, on your phone → that's ours. And if you just miss reading conversation instead of watching it, the case for text-only chat stands on its own.
08 / TRY IT/join from your pocket
No account, no camera, no notification hooks engineered against you — just a prompt, a stranger who shares an interest, and words on a dark screen. The room, rebuilt small.