like this: "CAP REQ :capability1 capability2 capability3" for example.
References:
- - <http://ircv3.atheme.org/specification/capability-negotiation-3.1>
+ - <http://ircv3.net/specs/core/capability-negotiation-3.1.html>
- <http://ngircd.barton.de/doc/Capabilities.txt>
- doc/Capabilities.txt
In addition, IRC Ops can use these two forms to specify the <target>:
.
- #<hostmask>
- - #<servermask>
+ - $<servermask>
.
The <mask> can contain the wildcard characters "*" and "?", but must
contain at least one dot (".") and no wildcard after the last one.
Please note that "all" IRC daemons even parse separate nicknames in
a single parameter (like ":nick1 nick2"), and therefore ngIRCd
- implements this behaviour, too.
+ implements this behavior, too.
References:
- RFC 2812, 4.9 "Ison message"