IRC Channels and the First Online Communities

01 The Room That Anyone Could Build

When Jarkko Oikarinen launched IRC from the University of Oulu in 1988, he built something deceptively simple: a system where any user could create a named space, prefix it with a hash symbol, and invite the world in. Channels like #unix, #hottub, and the legendary #warez had no product manager, no growth team, no algorithm deciding whose messages got seen. They had ops.

Operators — users granted the @ symbol beside their nickname — were the closest thing a channel had to a government. They could kick disruptive users, set modes that shaped the room's behavior (invite-only, moderated, no-external-messages), and hand the channel's entire fate to someone else with a single command. This was power without accountability structures, which produced outcomes ranging from tightly maintained scholarly communities to absolute fiefdoms run on personal grudge. Often both, depending on the hour.

The channel topic, that small strip of text at the top of every IRC client, did real social work. It announced rules, broadcast mood, marked grief — when a beloved regular died, their name would often sit in the topic for weeks. These small rituals accumulated into something real: a shared identity that outlasted any individual conversation.

02 Netsplits, Flood Wars, and Lag as a Social Condition

IRC ran on a network of servers, and the seams showed. A netsplit — when two parts of the server network lost contact with each other — would cleave a channel in two like a stage magician's trick, dozens of users vanishing from the participant list simultaneously, then reappearing minutes later in a cascade of join messages. Regulars learned to recognize the signature: a block of names gone at once, then the *** Rejoins. The channel would erupt in greetings, catching each other up on whatever had been said in the gap.

These weren't just technical hiccups; they were social events. Regulars who found themselves on the same side of a netsplit would form an impromptu sub-channel, often getting into trouble for things they assumed hadn't been witnessed. The structure of the network became part of the culture. Lag — the delay between sending a message and its arrival — was similarly social: a laggy user was half-present, their replies arriving late into a conversation that had already moved on, which generated its own comedy and frustration.

Then there was flooding: deliberately overwhelming a channel with a torrent of text, either as attack or obnoxious joke. Flood bots, ban lists, and K-line requests became part of the maintenance grammar of any serious channel. The people who knew how to manage these threats held real community standing, and their knowledge was passed down through direct mentorship rather than documentation.

These weren't just technical hiccups; they were social events.

03 What the Culture Made

IRC channels were the first place millions of people figured out how to be a community with strangers, and the lessons were learned the hard way. Handles weren't real names, which meant trust had to be earned through behavior across time — a username with years of history behind it meant something. The alt-account, the sock puppet, the drive-by troll: IRC users encountered these dynamics in the early 1990s and developed informal countermeasures that look prescient now.

The culture of +v (voiced users who could speak in a moderated channel), of channel bots that enforced rules automatically, of shared ban lists circulated between allied channels — all of this prefigures the moderation infrastructure of every platform that followed. Discord's roles and permissions, Slack's channel admins, Reddit's moderator toolkits: the logic is the same. The aesthetics are softer, the interfaces more forgiving, but the underlying social problem — how do you maintain a shared space when anyone can walk in — is identical.

Some channels lasted for years, developing in-jokes, hierarchies, enemies, and legends dense enough to fill novels. They hosted romances, feuds, and genuine intellectual work. The Undernet, EFnet, and later Freenode each developed distinct cultures, and within those networks, individual channels became genuine subcultures with their own norms, slang, and gatekeeping rituals. Freenode's #python and #ubuntu in particular became the de facto support infrastructure for major open-source projects — a function that was eventually institutionalized in newer tools, but that IRC performed, unglamourously, for decades.

What's striking, looking back, is how much was worked out by people with almost no precedent. Oikarinen's protocol gave them a room and a list of names. Everything else — how to welcome newcomers, how to handle harassment, how to mourn a regular who stopped appearing — was improvised into existence in real time, with no product guidelines, no community standards team, and no delete button. The first online communities built themselves from scratch, and the foundations, rough and ad hoc as they were, are still visible under everything that followed.

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

◆ A short timeline

1. 1988Jarkko Oikarinen launches IRC at the University of Oulu
2. Early 1990smajor networks EFnet and Undernet establish distinct channel cultures
3. 1990s–2000sFreenode becomes home to open-source project support channels (notably #python, #ubuntu)

◆ People & organisations