modern-irc
modern-irc copied to clipboard
ircdocs
A useful overview and reference to the IRC client protocol as it is implemented today.
If a client receives a message whose source does not contain either `!` or `@`, are there any rules that could be included in this spec for determining whether the...
Currently, the only requirements for valid usernames in this spec are given at , where minimum & maximum lengths are discussed, but information on what characters are allowed in usernames...
## Overview It seems that RPL_LINKS is a bit more complex than what explained in the docs. > ` * : ` From tests I've been running, the command is...
Sadly, both are in common use: * ERR_INVALIDUSERNAME is used by Ergo, InspIRCd, and ircu2/Nefarious/snircd * ERR_ONLYSERVERSCANCHANGE is used by Bahamut, Plexus4, and UnrealIRCd I'll discuss this with server devs...
Fix broken links for missing commands: KLINE, MAP and SILENCE See also #4
the [spec for `LIST`](https://modern.ircdocs.horse/#list-message) writes: ``` Parameters: [{,}] [{,}] ``` But this seems to be wrong in practice, in several ways. In the following tests, `#chan1` has 1 user, `#chan2`...
The [current grammar](https://modern.ircdocs.horse/#parameters) for the parameters in a message coming from the client says that everything following a colon is treated as a single parameter, since `trailing` has no further...
Recommend servers to reject nicknames such as `/quit`, in the section about nickname string restrictions. The protocol doesn't require it, but accepting nicknames starting with a `/` would be dangerous...
RFCs 1459 and 2812 *require* this space to be present, and some servers do send it (irc2, ircu2, charybdis, unrealircd). I am keeping it out of the grammar because it...