Internet Relay Chat

In 1988, in the premises of the University of Oulu, a Finnish student named Jarkko Oikarinen was working on a problem that frustrated him: how to enable multiple people to converse simultaneously on BBS systems, those electronic bulletin boards that preceded the Web? Existing tools like talk or rmsg under UNIX were limited to two-person conversations. Oikarinen then imagined something different—discussion rooms where anyone could enter and participate in the general conversation.

This idea gave birth to Internet Relay Chat, better known by the acronym IRC. For the first time, dozens of people could exchange messages in real time in a virtual space. Oikarinen called these spaces "channels," identified by the hash symbol that would later become famous on other platforms.

IRC's first months remained confidential. The network was confined to Scandinavia, constrained by the fledgling international connections of the era. The situation changed when Mike Jacobs, from MIT, managed to connect to Oikarinen's system. This transatlantic contact opened the floodgates: the code circulated, new servers were added, the network grew.

In January 1991, during the Gulf War, IRC experienced its first massive use during a global event. Users gathered to relay war information in real time, reaching over 300 simultaneous users for the first time. The logs of these exchanges are preserved in the ibiblio archives.

In August 1991, during the attempted coup against Mikhail Gorbachev, IRC played its part. During the media blackout imposed by the putschists (August 19-21), users in Moscow used IRC to transmit information in real time to the rest of the world, thus circumventing censorship. The logs of these exchanges are also preserved in the archives. Sources sometimes mention IRC use during the Russian constitutional crisis of September-October 1993, but this information remains to be confirmed by primary sources.

Success attracted ambitions and disagreements. Quarrels erupted over the management of IRC's single network. Who could create new servers? According to what criteria? Tensions mounted until the breaking point. Some users broke away to create Undernet, leaving Oikarinen's original server to form the basis of EFnet. These two rival networks continued to exist, joined by hundreds of others born from the same divisions.

For IRC fragmented. Each network developed its own rules, its own servers, its own code. Programmers experimented, modified, adapted. From this ferment emerged three major technical families: Undernet's P10 protocol, hybrid for EFnet, bahamut for Dalnet. The technical diversity reflected IRC's decentralized philosophy, where no one controlled the whole.

This decentralization came at a price. IRC networks regularly suffered from netsplits, those temporary disruptions that divided a network into several pieces. When two servers lost contact, their users found themselves separated until the connection was reestablished. These incidents, initially perceived as annoying failures, gradually became an accepted characteristic of the system.

IRC's architecture remained strikingly simple. Messages traveled in plain text, without encryption or persistent storage. This technical lightness partly explained the protocol's robustness, which also worked on sluggish connections with servers of limited resources. Where other systems demanded powerful servers and fast connections, IRC made do with little.

Users compensated for the protocol's limitations through their creativity. They developed chat bots, conversation logging systems, sophisticated graphical interfaces. The software ecosystem around IRC flourished. Everyone programmed their own tools, shared their scripts, improved those of others.

This culture of tinkering marked IRC. The protocol influenced the platforms that would succeed it. The @ of channel operators, the # of room names—these conventions born in the 1980s would reappear much later on Twitter and other social networks. IRC invented a symbolic language that the mainstream Web would eventually adopt.

Designed for a few hundred users at most, IRC exceeded its theoretical limits. At the height of its success, the four largest networks brought together over 500,000 simultaneously connected people. The servers held firm, the technology adapted, communities prospered.

Far more than a simple discussion tool, entire communities developed with IRC, with their codes, their habits, their rituals. Free software developers found a place for technical exchange. Computing enthusiasts gathered there to debate the latest innovations. Friendships were formed, projects were launched, collaborations were organized.

IRC survives discreetly in the shadow of the Web social giants. Younger generations often ignore it, preferring more colorful interfaces and richer features. But technical communities remain faithful to it. On thousands of channels, conversations continue, projects are developed, knowledge is transmitted. IRC embodies a certain idea of the Internet: decentralized, open, controllable by its users.