IRCv3
A collection of modern extensions to the IRC protocol, maintained by an open working group. It adds capabilities such as message tags, history playback, and SASL authentication through incremental specifications, while preserving backward compatibility with legacy IRC clients.
Timeline (last 90 days)
IRCv3 is a collection of protocol extensions that bring modern capabilities to the classic IRC protocol while maintaining backward compatibility with legacy clients.
IRCv3 is maintained by an open working group that gradually adds new features to IRC through a series of specifications, adopting an incremental evolution approach rather than starting from scratch.
Message tags are a foundational capability of IRCv3, allowing metadata to be attached to messages; advanced features such as server timestamps, message IDs, message receipts, and emoji reactions are all implemented using tags as the carrier.
The classic IRC message format is `:prefix command parameters`; IRCv3 introduces a key-value pair block at the beginning of the line using the `@` character to carry metadata.
Old clients that do not understand tags only need to skip the part starting with `@`, achieving a minimally invasive extension of the message format.
IRCv3's SASL authentication is completed during the connection establishment phase through a standardized challenge-response process, replacing the traditional NickServ approach of sending passwords in plaintext to a channel.
IRCv3's capability negotiation is implemented through the CAP subsystem: the client sends CAP LS to obtain a list of features, uses CAP REQ to request enabling capabilities, and the server responds with CAP ACK or CAP NAK.
The CAP capability negotiation process occurs before the formal login; legacy clients that do not support the CAP command will ignore these interactions, and the server falls back to compatibility mode, allowing new and old clients to coexist in the same channel.
IRCv3 introduces features such as server timestamps (server-time), message history playback (chat history), account authentication (SASL), and message receipts and editing.
All Facts (9)
IRCv3 is a collection of protocol extensions that bring modern capabilities to the classic IRC protocol while maintaining backward compatibility with legacy clients.
50%UnverifiedIRCv3 is maintained by an open working group that gradually adds new features to IRC through a series of specifications, adopting an incremental evolution approach rather than starting from scratch.
50%UnverifiedMessage tags are a foundational capability of IRCv3, allowing metadata to be attached to messages; advanced features such as server timestamps, message IDs, message receipts, and emoji reactions are all implemented using tags as the carrier.
50%UnverifiedThe classic IRC message format is `:prefix command parameters`; IRCv3 introduces a key-value pair block at the beginning of the line using the `@` character to carry metadata.
50%UnverifiedOld clients that do not understand tags only need to skip the part starting with `@`, achieving a minimally invasive extension of the message format.
50%UnverifiedIRCv3's SASL authentication is completed during the connection establishment phase through a standardized challenge-response process, replacing the traditional NickServ approach of sending passwords in plaintext to a channel.
50%UnverifiedIRCv3's capability negotiation is implemented through the CAP subsystem: the client sends CAP LS to obtain a list of features, uses CAP REQ to request enabling capabilities, and the server responds with CAP ACK or CAP NAK.
50%UnverifiedThe CAP capability negotiation process occurs before the formal login; legacy clients that do not support the CAP command will ignore these interactions, and the server falls back to compatibility mode, allowing new and old clients to coexist in the same channel.
50%UnverifiedIRCv3 introduces features such as server timestamps (server-time), message history playback (chat history), account authentication (SASL), and message receipts and editing.
50%