IRCv3
Points and comments are a snapshot, not live.
IRCv3 defines backwards-compatible protocol extensions to modernize IRC chat.
The IRCv3 Working Group develops backwards-compatible extensions for the IRC client protocol. Core specs include RFC1459 and RFC2812, with a modern core document at modern.ircdocs.horse. Extensions standardize SASL login, account tracking, message tags, away notifications, server-time stamps, and batch grouping. Work in progress includes account registration, chat history retrieval, secure connection upgrades (STS), Unicode nicknames, and client avatars. Discussion happens in #ircv3 on Libera.Chat.
What commenters are saying
Commenters split into those who miss IRC's simplicity and those who cite its practical limitations. Many note the need for bouncers or always-on clients to get offline messages and multi-device access, though IRCv3's chathistory extension and modern servers like Ergo aim to solve this. Several point out that IRC remains reliable during outages and is still used internally by tech companies. Comparisons to Discord, Matrix, and XMPP arise, with arguments over centralized vs. decentralized chat. Mobile clients like Goguma and Mango are mentioned as modern options.