~?~

~?~

~?~

Toggle navigation IRCv3 Home IRCv3 WG Charter FAQs Specs Support Networks Clients Servers Libraries SASL Mechanisms GitHub Contact We make a best effort to keep this list up to date. Please help us keep this updated by contributing a pull request . These networks are intended to test new IRCds and can also be used to test new client implementations of IRCv3 specifications. Feature InspIRCd Testnet InspIRCd-3.0 testnet.inspircd.org IRCCloud Teams irccloud-prattle team-irc.irccloud.com Invite required. PM jwheare for access. CAP v3.1 Yes InspIRCd Testnet CAP v3.1 Yes IRCCloud Teams CAP v3.1 CAP v3.2 Yes InspIRCd Testnet CAP v3.2 Yes IRCCloud Teams CAP v3.2 cap-notify Yes InspIRCd Testnet cap-notify Yes IRCCloud Teams cap-notify account-notify Yes InspIRCd Testnet account-notify No IRCCloud T...

Toggle navigation IRCv3 Home IRCv3 WG Charter FAQs Specs Support Networks Clients Servers Libraries SASL Mechanisms GitHub Contact This software is compliant natively; other software may be compliant with extensions. We make a best effort to keep this list up to date but it may deviate from recent releases. Please help us keep this updated by contributing a pull request . Feature BitlBee Charybdis ChatIRCd Elemental IRCd IRCCloud Teams ircd-hybrid InspIRCd mammon-ircd Nefarious IRCu Oragono CAP v3.1 3.4.2 BitlBee CAP v3.1 Yes Charybdis CAP v3.1 Yes ChatIRCd CAP v3.1 Yes Elemental IRCd CAP v3.1 Yes IRCCloud Teams CAP v3.1 7.2.1+ ircd-hybrid CAP v3.1 1.2.0+ InspIRCd CAP v3.1 Yes mammon-ircd CAP v3.1 Yes Nefarious IRCu CAP v3.1 0.1.0+ Oragono CAP v3.1 CAP v3.2 3.4.2 ...

Toggle navigation IRCv3 <ul class="nav navbar-nav navbar-right"> <li><a href="http://ircv3.org/"><span class="fa fw-fw fa-external-link-square"></span> IRCv3</a></li> </ul> Home IRCv3 WG Charter FAQs Specs Docs SASL Mechanisms Batch Types Support Networks Clients Servers Libraries GitHub Contact We're a group of IRC client and server software authors working to enhance, maintain and standardize the IRC protocol. Stakeholders in IRC such as IRC networks and network operators are invited to participate. Participation The IRCv3 Working Group contains participants from many top IRC networks and development teams, and welcomes new participants. View Specifications We have been releasing IRCv3 specifications with exciting, useful new features for networks, and client / server authors. View <div class="col-md-4 marketing-text"> <...

Toggle navigation IRCv3 <ul class="nav navbar-nav navbar-right"> <li><a href="http://ircv3.org/"><span class="fa fw-fw fa-external-link-square"></span> IRCv3</a></li> </ul> Home IRCv3 WG Charter Specs Docs SASL Mechanisms Batch Types Software Clients Servers Libraries GitHub Contact IRC is a networked protocol for group chat, tested and proven for over 20 years. The IRCv3 Working Group is a collection of IRC client and server software authors working to enhance, maintain and standardize the IRC protocol using backwards-compatible extensions. Working Group This is the main hub of our work, containing links to the features provided by IRCv3, our specifications, and our participants. View Specifications We have been releasing IRCv3 specifications with exciting, useful new features for networks, and client / server authors. View Chart...

Toggle navigation IRCv3 <ul class="nav navbar-nav navbar-right"> <li><a href="http://ircv3.org/"><span class="fa fw-fw fa-external-link-square"></span> IRCv3</a></li> </ul> Home Charter Specs Docs SASL Mechanisms Batch Types Software Clients Servers Libraries GitHub Contact IRCv3.2 userhost-in-names Extension Copyright © 2013 Mantas Mikulėnas <grawity@gmail.com> Unlimited redistribution and modification of this document is allowed provided that the above copyright notice and this permission notice remains intact. The userhost-in-names capability extends the NAMES reply messages ( RPL_NAMREPLY ) to contain the full hostmask (nick!user@host) of every user listed. Example: --> NAMES #atheme :irc.bnc.im 353 guest = #atheme :Rylee!rylai@localhost somasonic!andrew@somasonic.org :irc.bnc.im 366 guest #atheme :End of /NAMES list. Historical note:...

~?~