There's a particular kind of software that changes everything without anyone noticing at first. IRC is one of those. No launch event, no press release, no venture capital. Just a Finnish student, a Unix box, and the desire to make something better than what existed.
Before IRC: The State of Online Chat
By 1988, real-time text communication on the internet was not exactly new. Bitnet Relay had been around since 1985, letting users on the BITNET academic network send messages to each other in something resembling channels. Unix talk existed — a split-screen utility that let two users type at each other in real time. And of course, there was the venerable write command, which dates back to the earliest days of Unix multi-user systems.
But all of these had serious limitations. talk was point-to-point only — you couldn't have a group conversation. Bitnet Relay was restricted to BITNET nodes and had no concept of persistent channels or nicknames. MUDs (Multi-User Dungeons) offered multi-user text interaction, but they were games first and communication tools second. There was nothing that combined multi-user channels, real-time messaging, and the open architecture of the internet.
This was the gap that Jarkko Oikarinen saw. And in typical Finnish fashion, he didn't write a proposal about it. He just wrote the code.
The University of Oulu, Summer 1988
Jarkko Oikarinen — known online as "WiZ" — was a student at the University of Oulu, in northern Finland. He was working as a summer trainee at the university's Department of Information Processing Science. Part of his job involved maintaining the university's BBS (Bulletin Board System), and he'd been tinkering with extending it to support real-time chat.
The existing BBS at Oulu, called OuluBox, had a rudimentary chat feature. Oikarinen wanted something more. He was inspired partly by Bitnet Relay and partly by the concept of Usenet newsgroups — the idea that you could have named discussion spaces that anyone could join. What if you could have that, but in real time?
He started writing the server code in C on a Sun workstation. The first version was crude — it handled basic connections, message passing between users, and the concept of channels (which he initially called "channels" from the start, borrowing the metaphor from CB radio). The client was equally simple. But it worked.
The first test users were other students and staff at Oulu. Then Oikarinen connected his server to another machine at the University of Tampere. Then Helsinki. Within weeks, the Finnish academic network had a working multi-server chat system. By November 1988, IRC had spread beyond Finland — first to other Nordic countries, then to the rest of Europe, then to North America.
The First IRC Server and Early Architecture
The original IRC server — what we'd now call an "ircd" — was remarkably simple compared to modern implementations like UnrealIRCd or InspIRCd. But the core concepts were already there:
- Client-server model: Users connected to a server with a client program. The server handled message routing.
- Server-to-server linking: Multiple servers could connect to form a network, sharing state about users and channels.
- Channels: Named spaces (prefixed with #) that users could join and leave freely.
- Nicknames: Users chose a unique handle. First come, first served — no registration system.
- Text-based protocol: Everything was plain text over TCP. You could literally telnet to an IRC server and type raw commands.
That last point is worth emphasizing. The simplicity of the IRC protocol — human-readable text commands over a TCP socket — is one of the main reasons it spread so fast. Any programmer who could write a basic socket program could write an IRC client. Or a bot. Or a server. The barrier to entry was essentially zero for anyone with basic networking knowledge.
I've seen people connect to IRC servers using nothing but nc (netcat) and raw typing. It's not comfortable, but it works. Try doing that with Slack or Discord.
RFC 1459 and Protocol Standardization
As IRC grew through 1989 and into the early 1990s, the need for formal documentation became clear. Different server implementations were appearing, and without a specification, interoperability was a matter of reading source code and hoping for the best.
RFC 1459, authored by Jarkko Oikarinen and Darren Reed, was published in May 1993. It remains one of the most referenced RFCs in the history of internet chat. The document defined:
- The client-to-server and server-to-server protocols
- Message format:
:prefix COMMAND params :trailing - Core commands:
NICK,USER,JOIN,PART,PRIVMSG,QUIT,PING/PONG, and many more - Numeric reply codes (001 for welcome, 433 for nickname already in use, etc.)
- Channel modes and user modes
- The server linking model (spanning tree topology)
RFC 1459 was later supplemented by RFC 2810, 2811, 2812, and 2813 in April 2000, which attempted to update and split the specification into architecture, channel management, client protocol, and server protocol respectively. But in practice, RFC 1459 remains the baseline that virtually every IRC implementation targets first.
One thing RFC 1459 got wrong — or at least left underspecified — was character encoding. The protocol assumes ISO 8859-1 (Latin-1), but in practice, different networks and clients used different encodings for years. It wasn't until IRCv3 extensions that UTF-8 support became standardized. As someone whose surname has letters that don't exist in ASCII, I appreciate the irony that a communication tool spent decades struggling with character sets.
How IRC Spread Across the World
The growth of IRC between 1988 and 1995 was organic and chaotic. There was no central authority, no company behind it, no marketing budget. It spread the way good tools spread — someone showed it to someone else, who showed it to someone else.
A few key moments in IRC's expansion:
1989-1990: IRC reaches North America. Servers at MIT, Oregon State, and other universities link up. The first truly international IRC network emerges.
January 1991: During the first Gulf War, IRC becomes an unexpected news source. Users in the Middle East relay real-time reports to channels filled with hundreds of people. This is arguably the first time internet chat is used for live crisis reporting — years before CNN.com existed.
1992-1993: The first major network split. Disagreements over server linking policies and network governance lead to the formation of separate networks. EFnet (the original network) and the Undernet emerge as distinct entities. This pattern of schism and fork would repeat throughout IRC history.
1993-1996: IRC client software improves dramatically. mIRC for Windows (released in 1995) brings IRC to the masses of Windows users. Homer and Ircle serve Mac users. ircII remains the standard for Unix. The user base explodes from thousands to hundreds of thousands.
1996-2000: Peak IRC. Multiple networks with hundreds of thousands of simultaneous users. DALnet, QuakeNet, IRCnet join EFnet and Undernet as major networks. IRC is where the internet hangs out — for tech discussion, gaming coordination, warez distribution, and everything in between.
The Legacy That Still Runs
Thirty-eight years after Oikarinen's summer project, IRC is still here. It's not dominant like it was in 1999, but it's far from dead. Libera.Chat hosts the development channels for hundreds of open-source projects. OFTC serves Debian and other major Linux distributions. Private IRC networks run inside companies, hackerspaces, and communities worldwide.
The protocol has influenced virtually every chat system that came after it. Slack's channels? That's IRC. Discord's servers and channels? IRC with voice and a pretty UI. Even modern team chat features like @mentions, /commands, and topic-based channels — all of these existed in IRC first.
Oikarinen himself has remained relatively low-profile. He worked at various Finnish companies and hasn't been heavily involved in IRC development for years. But his creation — born in a Finnish summer when he was supposed to be maintaining a BBS — became one of the foundational communication protocols of the internet age.
That's the thing about IRC. It wasn't designed to be revolutionary. It was designed to let people talk to each other in real time, across networks, without barriers. Everything else followed from that simple premise.
Frequently Asked Questions
When was the first IRC message sent?
The first IRC messages were exchanged in August 1988 on the server tolsun.oulu.fi at the University of Oulu in Finland. The exact date isn't recorded — it was a gradual development process, not a single launch event.
Is IRC still used today?
Yes. While IRC's user numbers are far below their peak in the early 2000s, networks like Libera.Chat, OFTC, EFnet, and IRCnet remain active. IRC is particularly popular in open-source development communities, where it serves as the primary communication channel for many major projects.
What does RFC 1459 define?
RFC 1459, published in May 1993, defines the Internet Relay Chat protocol — including the client-server architecture, message format, core commands (JOIN, PART, PRIVMSG, etc.), channel and user modes, and the server linking model. It remains the foundational specification for IRC implementations.
Who invented IRC?
Jarkko Oikarinen (online handle "WiZ"), a Finnish student at the University of Oulu, created IRC in August 1988. The protocol was later co-documented in RFC 1459 with Darren Reed.
FAQ
Who invented IRC?
Jarkko Oikarinen created IRC in August 1988 at the University of Oulu, Finland. He wrote it as a replacement for a program called MUT (MultiUser Talk) on the university's Sun servers.
What was the first IRC server?
The first IRC server was tolsun.oulu.fi, running at the University of Oulu. It connected to other Finnish universities within weeks of launching.
When was RFC 1459 published?
RFC 1459, which formalized the IRC protocol, was published in May 1993 by Jarkko Oikarinen and Darren Reed. It remains the foundational document for IRC implementations.