IRC turned 36 this year and refuses to die. The IRCv3 Working Group, a volunteer standards body hosted on Libera.Chat, is methodically extending the original RFC1459/RFC2812 client protocol with features that closed-source chat platforms treat as proprietary selling points: standardized account login via SASL, message history playback, metadata tagging, instant away notifications, and message grouping for display. The approach is deliberately conservative. Every extension is backwards-compatible with older IRC clients and servers. No one has to upgrade anything to keep working. The specifications move through a public GitHub repository and an open discussion channel (#ircv3 on Libera.Chat), and the roadmap is published. This is how internet protocols used to get built — incrementally, by the people who run the infrastructure. What is actually being standardized matters. SASL authentication (versions 3.1 and 3.2) replaces the fragile NickServ registration dance that has confused new users for decades. Account information sharing across clients enables richer identity features without a central identity provider. The server-time extension lets bouncers replay history with accurate timestamps — a feature Slack charges enterprise money for. The pipeline is more ambitious. Standardized account registration and verification would give IRC clients a first-run experience that doesn't feel like 1998. Chat history access via a standard protocol means bouncers and servers can serve scrollback without proprietary APIs. Automatic secure-connection detection addresses a real security gap. Unicode nickname and channel name support — still in progress — acknowledges that most of the world doesn't type in ASCII. The structural contrast with dominant platforms is stark. Discord, Slack, and Teams each built these features as proprietary lock-in. Message history is a premium upsell. Identity is platform-controlled. API access is gated and revocable. IRCv3 produces the same capabilities as open specifications anyone can implement. The participating organizations include client and server developers who compete with each other on implementation while sharing the protocol. The limitation is adoption friction. IRC's user base has contracted dramatically since the mid-2000s. Building better specifications does not automatically rebuild the network effects that Discord captured. The Working Group is solving a protocol problem, not a growth problem, and those are different challenges. Whether the specifications attract new client developers — particularly mobile-first ones — will determine whether this is preservation or revival. Still, this is genuine generative infrastructure work. No one extracts rent from an open specification. The value created is non-rivalrous: every implementation benefits from every other implementation's compatibility. In a decade where chat platforms have consolidated around three or four proprietary stacks, a functioning open alternative has option value even if it never recaptures mainstream scale.
