multi-prefix Extension

Description 🔗

When requested, the multi-prefix client capability will cause the IRC server to send all possible prefixes which apply to a user in NAMES, WHO and WHOIS output.

These prefixes MUST be in order of ‘rank’, from highest to lowest.

Example:

--> NAMES #tethys
:hades.arpa 353 guest = #tethys :~&@%+aji &@Attila @+alyx +KindOne Argure
:hades.arpa 366 guest #tethys :End of /NAMES list

--> WHO #test
:kenny.chatspike.net 352 guest #test grawity broken.symlink *.chatspike.net grawity H@%+ :0 Mantas M.
:kenny.chatspike.net 315 guest #test :End of /WHO list

--> WHOIS barmand
:irc.chat 311 guest barmand barmand cosani.jp * :Armand
:irc.chat 319 guest barmand :~&@%+#falco @+#raynor
:irc.chat 312 guest barmand irc.chat :Antibes
:irc.chat 318 guest barmand :End of /WHOIS list

Errata 🔗

Previous versions of this spec did not specify that all possible prefixes which apply to users be also sent in WHOIS output. This was added for consistency with other replies that contain user prefixes.

Software supporting multi-prefix: Ergo, IRCCloud Teams, ircd-hybrid, InspIRCd, Nefarious IRCu, Solanum, txircd, UnrealIRCd, AdiIRC, Ambassador, catgirl, Colloquy, glirc, Halloy, HexChat, IceChat, Irssi, Konversation, KVIrc, mIRC, Mozilla Thunderbird, Quassel, senpai, Swirc, Textual, WeeChat, gamja, IRCCloud, Kiwi IRC, The Lounge, PIRC.pl web client, IRC for Android, Colloquy, CoreIRC, Palaver, Quasseldroid, Goguma, IRCCloud (as Server), KiwiBNC (as Server), KiwiBNC (as Client), pounce (as Server), pounce (as Client), soju (as Server), soju (as Client), ZNC (as Server), ZNC (as Client), BitBot, Limnoria, Moon Moon, Sopel (ex Willie), ChatSharp, Communi, girc, irc-framework, ircrobots, Kitteh IRC Client Library, pydle, Rust irc, Warren, BitlBee, PyLink (clientbot mode)