The Origin of IRC

01 A Student's Solution to a University Bulletin Board

In the summer of 1988, a Finnish student named Jarkko Oikarinen was working as a system administrator at the University of Oulu. He had some free time, a Unix workstation, and an itch to improve the MUT (MultiUser Talk) software running on the university's bulletin board system, OuluBox. What he built as a side project would become the structural template for nearly every group chat system that followed.

Oikarinen's creation was Internet Relay Chat — IRC. The concept was elegant and, in retrospect, obvious: instead of a two-person talk session or a static message board, why not route messages through a central server in real time, to a named channel that anyone could join? The "relay" in the name was quite literal. Messages hopped from client to server and back out to every connected client in the channel, nearly instantly. The server was the room; the channel name was the door.

He tested it first on OuluBox in August 1988. Within weeks, with help from friends at other Finnish universities and access to the wider academic internet, he was connecting servers together — a network of networks. By November 1988, IRC had spread across the Nordic countries and was beginning to appear on machines in the United States. The protocol was simple enough to implement that anyone running a Unix server could spin up a node and link it in.

02 Channels, Ops, and the Architecture of Conversation

What made IRC stick wasn't just the technology — it was the social architecture baked into the protocol. Channels were prefixed with a # symbol and were free to create. The person who first created a channel became its operator, or "op," inheriting the power to kick disruptive users, set a topic, and control who could speak. This wasn't just moderation; it was the first widely-used model of community governance in online spaces. The concept of the channel operator maps, in a direct line, to the admin roles of every forum, Discord server, and Slack workspace since.

The network model introduced something else: the netsplit. Because IRC servers linked together in a spanning tree, a dropped connection between two nodes could partition the network — users on either side of the split would briefly appear to vanish, then flood back when the link recovered. It was a visible, sometimes dramatic reminder that you were talking across a genuinely distributed system. IRC channels and the communities that formed around them developed their own cultures precisely because of these quirks — the netsplit, the flood, the bot — each one a feature that the community had to learn to live with and then eventually embrace.

RFC 1459, published in 1993, formalised the IRC protocol. By then IRC was already enormous. During the Gulf War in 1991, users had gathered in channels to share live updates, one of the earliest examples of real-time collective news-reading online. When a coup attempt unfolded in the Soviet Union that same year, people on IRC were parsing wire-service feeds and eyewitness reports together in channels — an experience with no real precedent. IRC wasn't just a chat tool; it had become, for the technically connected, a kind of distributed newsroom.

It was a visible, sometimes dramatic reminder that you were talking across a genuinely distributed system.

03 The Template That Outlasted the Tool

IRC's peak came in the mid-to-late 1990s. At its height, the main public networks — EFnet, IRCnet, Undernet, DALnet — together supported millions of simultaneous users. Then AOL Instant Messenger arrived in 1997, MSN Messenger in 1999, and the mass market chose the simpler, shinier thing. IRC didn't die; it retreated. Developers, open-source projects, and network administrators kept using it long after the mainstream moved on. Many still do — Libera.Chat, the network that formed when Freenode collapsed in 2021, hosts thousands of active channels today.

But the real legacy isn't the surviving user base. It's the vocabulary and the structure. Named channels. Persistent group rooms. User roles. Slash commands. The idea that a text-based room could have a culture, a history, a set of norms. Slack, Discord, and Microsoft Teams are all, at some level, IRC with a better font and a mobile app. The relay chat that Jarkko Oikarinen hacked together on a Finnish university server rippled outward through decades of design decisions by people who may never have typed a single IRC command themselves.

Thirty-seven years on, the architecture of that OuluBox experiment is still the skeleton inside almost every group chat you open.

These notes are part of an ongoing field guide — corrections and additions are welcome at the desk.

◆ A short timeline

1. August 1988first IRC test on OuluBox, University of Oulu
2. November 1988IRC spreads to Nordic countries and early US nodes
3. 1991Gulf War and Soviet coup attempt bring mass real-time IRC news-reading
4. 1993RFC 1459 published
5. Mid-to-late 1990sIRC peak on EFnet, IRCnet, Undernet, DALnet
6. 1997–1999AIM and MSN Messenger draw mass-market users away
7. 2021Libera.Chat replaces Freenode as major open-source IRC hub

◆ People & organisations