IRC services and tools worth knowing: the ecosystem around the chat

The chat window is the part everyone sees, but IRC has always come with a supporting cast: the services that run on the network itself, and the tools built around it by everyone else. Some you'll use every day without thinking about them; others solve a specific problem brilliantly the moment you hit it. This is a tour of the ones worth knowing.

Network services: the robots that aren't bots #

On most networks, a handful of special pseudo-users run as part of the network — not channel bots someone added, but core infrastructure. You message them like any user, and they manage the things that make IRC feel less anarchic.

• NickServ — owns the concept of owning a nick. Register with it and your nickname is protected by a password (or, better, by SASL) so nobody else can wear your identity. Invented on DALnet in 1994 and now near-universal. /msg NickServ HELP.
• ChanServ — lets a registered account own a channel: persistent settings, an access list of who gets ops, topic protection, and auto-recovery so your channel survives everyone leaving. The reason a channel can have the same owners for fifteen years.
• MemoServ — leave a message for a registered user who's offline; they get it when they next identify. IRC's answer to "they weren't around when I needed them."
• HostServ — hands out vhosts (vanity hostmasks / cloaks), so instead of exposing your IP you appear as something like user/yourname. Part identity, part privacy.
• OperServ / BotServ — operator tooling and, on some networks, a way to assign a managed bot to your channel.

Two big caveats. First, the software behind these varies — most networks run Atheme or Anope, Ergo builds them in — but the user-facing commands are mostly the same. Second, not every network has them at all: EFnet and IRCnet famously run without services, which is the whole personality of those networks. And some networks rename them entirely — on QuakeNet it's Q, on Undernet it's X.

ChanFix: the service for networks that have none #

A clever special case. On services-free EFnet, what happens if a channel's ops all disappear in a netsplit and someone grabs the empty channel? ChanFix quietly tracks which users have historically held ops in a channel, and can restore them after a takeover — order, but only the minimum, on a network that rejects everything else. The exception that proves the no-services rule.

Finding things: search engines and directories #

IRC has no central directory, which is exactly why third-party ones are so useful. The big problem — "what channel do I actually want, and on which network?" — is solved by tools that crawl hundreds of networks at once:

• netsplit.de — the statistics and search workhorse. Crawls 500-plus networks, tracks user and channel counts over time (it's the source of most of the numbers on this site), and lets you search channels across all of them. The place to go to answer "how big is this network, really?"
• IRC Driven — a channel and network discovery platform with a searchable index, good for finding active channels on a topic.
• KiwiIRC's search — indexes a few hundred networks' channel lists.
• The LIST command — the built-in option. /list asks the server for its channel list, though on big networks that's a firehose; many networks instead run ALIS (/msg alis LIST *keyword*) for filtered channel search. More in how to find channels.

Bridges: connecting IRC to everything else #

You don't have to choose between IRC and the platform your other community uses — you can bridge them, mirroring messages both ways.

• Matterbridge — the standard answer. A single Go binary that relays messages between IRC and Discord, Matrix, Slack, Telegram, Mattermost, XMPP and more. The usual way an open-source project keeps an IRC channel and a Discord without splitting its community.
• Matrix bridges — Matrix has long maintained IRC bridges, letting Matrix users appear in IRC channels and vice versa. The relationship is sometimes fraught (bridged users, spam handling), but for IRC-vs-Matrix communities it's a real option.
• biboumi — an XMPP-to-IRC gateway: use an XMPP/Jabber client to talk on IRC channels, with IRC channels appearing as XMPP rooms.

A bridge is also the gentlest bot etiquette test: it joins a channel and relays, so get operator permission first.

History and persistence #

IRC's original sin — it forgets everything when you disconnect — has a whole tool category devoted to fixing it:

• Bouncers (ZNC, soju) stay connected for you and replay what you missed. The classic fix.
• IRCCloud — the hosted, zero-maintenance version: a always-on connection plus apps, as a paid service.
• Server-side history — modern networks running Ergo, or any network implementing the IRCv3 chathistory extension, store history on the server so a capable client can just scroll up. The bouncer-free future, where it's available.

The small tools that make IRC pleasant #

The cultural glue — small utilities, mostly delivered by channel bots, that have been part of IRC for decades:

• Pastebins. IRC lines are short and flooding is rude, so you never paste code into a channel — you paste it to ix.io, 0x0.st, bpa.st, paste.debian.net or similar, and drop the link. Knowing this is half of channel etiquette.
• URL-title bots fetch and announce the title of links people post, so a bare URL gets context.
• Factoid bots answer canned questions — !faq install, !rules — and are how busy support channels avoid answering the same thing forty times a day.
• Logging services like the public channel logs many projects publish to the web, so conversations are searchable later (run with the channel's consent, and announced in the topic).
• Quote bots, seen bots, trivia bots, dice rollers — the toys that give a channel personality and, in the case of trivia, have kept some channels populated for twenty years.

Most of these are bots someone runs, not network services — which means in any channel, the available commands are whatever that channel's operators chose to add. When in doubt, the channel topic or a polite !help usually reveals what's on offer.

Where to go deeper #

The services above are the user's-eye view. If you want to run them — stand up NickServ and ChanServ on your own network — that's the server software and run-your-own-server territory. And the single best curated index of the entire tooling ecosystem is the community- maintained awesome-irc list, which tracks clients, servers, services, bots and bridges as they come and go.