Discord has 200 million monthly active users. IRC has perhaps 200,000 daily users across all networks. By any market metric, Discord won and IRC lost. But metrics measure adoption, not value. And the properties that make IRC matter in 2024 are precisely the properties that adoption metrics don't capture.
This Is Not a Nostalgia Piece
I need to say this upfront because every "IRC matters" article gets dismissed as nostalgia. I'm not arguing that IRC is better than Discord for most users. It isn't. Discord has voice chat, screen sharing, rich embeds, a mobile app that doesn't require SSH, and an onboarding experience that doesn't involve learning what /msg NickServ IDENTIFY means. For a gaming community, a school study group, or a casual social server, Discord is the obviously correct choice.
What I'm arguing is that IRC provides properties that Discord structurally cannot provide, and that those properties matter for specific communities and use cases. Not everyone needs them. But the people who do have no alternative.
The Ownership Question
Discord is owned by Discord Inc. They set the rules. They can change those rules at any time. They have, repeatedly. Terms of service updates, API changes, bot verification requirements, Nitro pricing adjustments — every Discord user and community is subject to decisions made by a private company optimizing for revenue.
IRC is owned by nobody. The protocol is documented in public RFCs. The server software is open source. Anyone can run a server. Anyone can run a network. Anyone can write a client. No company can shut down IRC because there is no company to shut it down. Individual networks can die (RIP Freenode), but the protocol and the ecosystem persist.
This isn't an abstract philosophical point. It has concrete consequences:
- Content moderation: On Discord, content policy is set by Discord Inc., shaped by advertiser requirements and regulatory pressure. On IRC, content policy is set by each network and each channel, independently. Some channels are heavily moderated. Some are unmoderated. The choice belongs to the community, not a platform.
- Data access: Discord stores all messages on their servers. They can access, analyze, and share this data according to their privacy policy and legal obligations. On IRC, messages aren't stored by default. If you run your own server, you control what's logged. If you use a public network, messages transit the server but aren't retained.
- Platform risk: If Discord shuts down, every community on Discord loses their home simultaneously. If an IRC network shuts down, affected communities move to another network. The client, the configuration, the bots — they all work on any IRC network. There is no lock-in.
Data Sovereignty
When you type a message in Discord, that message is stored on Discord's servers. It's indexed, searchable, and subject to Discord's data processing policies. Discord's privacy policy allows them to collect usage data, device information, and message content for service improvement and safety purposes.
When you type a message on IRC, the message is relayed to the recipients and then it's gone. The server doesn't store it. There is no search index. There is no analytics pipeline. The message existed for the fraction of a second it took to relay it, and then it existed only in the memories (and log files) of the clients that received it.
This is a feature, not a limitation. For discussions involving sensitive technical information — security vulnerabilities, internal tooling, pre-announcement coordination — the absence of server-side storage is actively desirable. You can't subpoena data that doesn't exist. You can't breach a database that was never created.
Scriptability and Integration
IRC's text-based protocol makes it trivially scriptable. Sending a message to an IRC channel requires a TCP connection and a few lines of text:
#!/bin/bash
exec 3<>/dev/tcp/irc.libera.chat/6667
echo "NICK buildbot" >&3
echo "USER buildbot 0 * :Build Bot" >&3
sleep 2
echo "JOIN #myproject-builds" >&3
echo "PRIVMSG #myproject-builds :Build #4271 passed. 0 warnings." >&3
echo "QUIT :Done" >&3
exec 3<&-That's a complete IRC notification script in 8 lines of bash. No API keys. No OAuth tokens. No rate limit management. No JSON parsing. No HTTP library. Just TCP and text.
Compare the equivalent Discord integration: register an application, create a webhook or bot account, obtain a token, manage token security, construct JSON payloads, handle HTTP status codes and rate limits, deal with Discord's gateway for anything beyond webhooks. It works. It's also 10-100x more complex.
For development teams that want to pipe build results, monitoring alerts, deployment notifications, and git activity into a chat channel, IRC's simplicity is a genuine advantage. The integration takes minutes, not hours. It breaks less. When it does break, it's obvious why.
Resource Minimalism
The Discord desktop client is an Electron application. It uses 300-800 MB of RAM depending on how many servers you're in. The mobile client is a standard resource-hungry chat app. Running Discord on older hardware or low-powered devices is an exercise in patience.
WeeChat, a full-featured IRC client, uses 30-50 MB of RAM while connected to multiple networks with dozens of active channels. Irssi uses even less. On a Raspberry Pi, an IRC client runs comfortably alongside other services. On a VPS with 512 MB of RAM, you can run a WeeChat instance in tmux that stays connected 24/7 — your permanent presence on IRC for a few dollars a month.
The server side is similarly lean. An IRC server for a small community runs on hardware from 2010. A Matrix homeserver for the same community needs modern hardware with SSDs and multiple gigabytes of RAM. This isn't a criticism of Matrix — it does more. But for communities that only need text chat, the resource overhead of "more" is waste.
Protocol Longevity
IRC has been running continuously since 1988. Thirty-seven years. It predates the World Wide Web. It has survived every communication platform that was supposed to replace it: ICQ, AIM, MSN Messenger, Google Talk, Slack, and now Discord.
The reason is architectural. IRC is a simple protocol implemented by many independent servers and clients. There is no single point of failure. No company needs to remain profitable for IRC to continue operating. No investor needs to see returns. The protocol exists in RFCs, the code exists in public repositories, and the knowledge to run an IRC network exists in thousands of administrators worldwide.
Discord has existed since 2015. Ten years. It depends on Discord Inc. remaining solvent and committed to the platform. If Discord is acquired, pivots, or shuts down, every community on Discord migrates or dies. This isn't speculation — it's exactly what happened to every previous centralized communication platform. AIM shut down in 2017. Google Talk became Hangouts became Chat. Yahoo Messenger closed in 2018. Centralized platforms have a lifespan. Open protocols don't.
For communities that plan to exist for decades — open-source projects, academic groups, technical communities — building on a protocol that has already survived three decades is a more defensible choice than building on a platform that might not exist in ten years. IRC isn't going anywhere. It can't. There's nobody with the power to turn it off.
Accessibility in Constrained Environments
There is a class of user for whom IRC isn't a preference — it's a necessity. In environments with limited bandwidth, restricted internet access, or aging hardware, IRC works where modern platforms don't.
A researcher at a remote field station with a satellite internet link measured in kilobits per second can use IRC. Discord's web client won't load. Matrix's initial sync will time out. IRC, with its text-only protocol and sub-kilobyte messages, works on connections that modern web applications consider unusable.
University students in countries with expensive mobile data use IRC because it costs almost nothing in bandwidth. A full day of active IRC usage consumes less data than loading Discord's landing page once. For communities that span economic boundaries — and open-source communities very much do — this accessibility matters.
IRC also works on hardware that modern Electron applications refuse to run on. A 2008 laptop running Debian with WeeChat in a terminal is a fully functional IRC workstation. Try running Discord on the same hardware. The client will either refuse to install or consume all available RAM trying to render a channel list.
This isn't about romanticizing constraints. It's about recognizing that communication tools should not require 8 GB of RAM and a broadband connection. IRC's minimal resource requirements are not a legacy limitation — they're an accessibility feature that no modern platform replicates.
FAQ
Can IRC and Discord coexist?
Yes, and they do. Many communities maintain both an IRC channel and a Discord server, sometimes bridged together. The IRC channel serves the technical core; the Discord serves the broader community. This is pragmatic, not contradictory.
What does IRC offer that Matrix doesn't?
Simplicity and minimal resource usage. Matrix is also an open protocol with federation, but it's significantly heavier to run and more complex to administer. IRC is the right choice when you need text chat and nothing else. Matrix is the right choice when you need history, encryption, and rich media on an open protocol.
Isn't IRC too hard for non-technical users?
For most non-technical users, yes. IRC's lack of a default GUI client, the need to register nicknames manually, and the absence of built-in features like image previews create a barrier. This is a real limitation. IRC's remaining user base is primarily technical, and that's partly because the onboarding experience filters out everyone else.