modern-irc
modern-irc copied to clipboard
ircdocs
A useful overview and reference to the IRC client protocol as it is implemented today.
This documents a widely implemented practice. This allows clients to discover when this field is set to a meaningful value, and when it's not.
Clients may want to strip that prefix to improve their UI.
Addresses https://github.com/ircdocs/modern-irc/pull/154#issuecomment-1000911641 Though I am not sure this is correct in the presence of a bouncer. Bouncers would reply to `PING` with their own time, while `TIME` would be forwarded...
Hi there, I noticed that RFC2812 specifies that the `host` portion of the `source` (formerly `prefix`) should be hostname, ipv4 address, or ipv6 address, I've copied the relevant parts here...
We should document all widespread modes that can be used unambiguously across servers (eg. no `+q` unless `PREFIX` is reliable to tell whether it's used for quiets vs owner). Starting...
After discussion in #78, it looks like RFC2812-style service commands are still use, either for actual RFC2812-style services (eg. IRCnet), or for Anope/Atheme. (I also think they are a good...
It's useful to know as a client dev that, for instance, a `WHO` command shouldn't be sent while another one is still in progress. It would be nice to add...
Ref https://github.com/ircdocs/modern-irc/pull/114#issuecomment-908125331 In a client, it's useful to know whether the user has set an explicit realname, or whether it's unset. If it's unset, it doesn't provide any useful information,...