isupport.yaml

# isupport.yaml
#
# This file is Copyright (c) 2015-2019 Daniel Oaks
#  <daniel@danieloaks.net>
#
# This file is PUBLIC DOMAIN, to benefit the IRC developer community. If you
# modify this file, please state your name and modifications here in order
# for people to be able to distinguish between your version and this version.
#
# For more information or corrections, please contact the author.

file:
    type: "isupport"
    revision: "0.12"

# The following information is used to create pretty HTML page and tables

page:
    name: RPL_ISUPPORT Tokens
    extra: >
        <p>
            Red denotes a conflicting token definition, gray for deprecated
            (however quite possibly still in use), yellow for proposed, and
            blue for OK.
        </p>

table:
    row-id: name

    row-classes:
        - conflict
        - obsolete
        - proposed
        - repeated

    columns:
        -
            name: Name
            content: name
            classes: code
            link: information
        -
            name: Format
            content: format
            classes: code
            description: Format of the token
            examples: true
            xml_escape: true
        -
            name: Comments
            content: comment
            seealso: seealso
            description: "Additional comments, history and other details"
            markdown: true

# The following format is used through-out this file. The first field
# ('name') is mandatory, the others may or may not exist.

format:
    name: token name
    origin: where the numeric was found
    contact: point of contact associated with the numeric
    information: URL where to find more information
    format: the token format
    comment: "comments, history, etc."
    seealso: name
    conflict: true
    obsolete: true
    repeated: true

values:
    -
        name: ACCEPT
        format: "ACCEPT=<number>"
        origin: ircd-ratbox
        comment: >
            Indicates the maximum number of online nicknames a user may have
            in their accept list. First introduced in ircd-ratbox-3.0.9(r28737).

        examples:
            - "ACCEPT=20"

    -
        name: AWAYLEN
        format: "AWAYLEN=[number]"
        comment: >
            Indicates the maximum length of an away message. If `"number"` is not
            defined, there is no limit.

        examples:
            - "AWAYLEN=8"
            - "AWAYLEN="

    -
        name: BOT
        format: "BOT=<letter>"
        comment: >
            Indicates the character to be used as a user mode to let clients
            mark themselves as bots by setting it

        examples:
            - "BOT=B"
            - "BOT=b"

    -
        name: CALLERID
        format: "CALLERID[=letter]"
        information: "https://github.com/ircd-hybrid/ircd-hybrid/blob/master/doc/modeg.txt"
        comment: >
            Indicates that the `"caller-id"` user mode is supported, which
            rejects messages from unauthorized users. `"letter"` defines the
            mode character, which is used for this feature. If the value is not
            given, it defaults to the mode `"g"`.

        examples:
            - "CALLERID"
            - "CALLERID=g"

    -
        name: CASEMAPPING
        format: "CASEMAPPING=<string>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the method that's used to compare equality of
            case-insensitive strings (such as nick/channel names).
            Typical values include `"ascii"` and `"rfc1459"`. `"rfc3454"` is a
            proposed value that refers to the stringprep method described in
            [RFC3454](http://tools.ietf.org/html/rfc3454) (typically used for
            UTF-8 casefolding).

        examples:
            - "CASEMAPPING=rfc1459"

    -
        name: CHANLIMIT
        format: "CHANLIMIT=<prefix:[number[,prefix:number[,...]]]>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the maximum number of channels a client may join. Though
            a client shouldn't assume that other clients are limited to what
            they receive here. If `"number"` is empty, there is no limit.

        examples:
            - "CHANLIMIT=#+:25,&:"
            - "CHANLIMIT=&#:50"

    -
        name: CHANMODES
        format: "CHANMODES=<A,B,C,D>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the channel modes available and which types of arguments
            they do or do not take. See the linked Hardy draft for specifics.

        examples:
            - "CHANMODES=b,k,l,imnpst"
            - "CHANMODES=beI,k,l,BCMNORScimnpstz"

    -
        name: CHANNELLEN
        format: "CHANNELLEN=<number>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Specifies the maximum length of a channel name that clients may
            join.

        examples:
            - "CHANNELLEN=50"

    -
        name: CHANTYPES
        format: "CHANTYPES=[string]"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the types of channels supported on this server. These are
            channel type prefixes as specified in the RFC and as described by
            the ["Channel Type Prefixes"](chantypes.html) list on this site.

        examples:
            - "CHANTYPES=&#"

    -
        name: CHARSET
        format: "CHARSET=<string>"
        information: "https://tools.ietf.org/html/draft-brocklesby-irc-isupport-03"
        comment:
            Originally meant to specify the character encoding of messages sent
            by the server, but removed in a later version of the draft. It is
            meaningless nowadays and should be ignored.

            [`draft-brocklesby-irc-isupport-03`](https://tools.ietf.org/html/draft-brocklesby-irc-isupport-03)
            (2004) says, "The traditional CHARSET parameter has been entirely
            removed. It was found to be unworkable; a correct specification
            could not be devised to represent its meaning across
            implementations".

            [`draft-hardy-irc-isupport-00`](https://tools.ietf.org/html/draft-hardy-irc-isupport-00)
            (2005) removed it completely.

        examples:
            - "CHARSET=ascii"

        obsolete: true

    -
        name: CLIENTVER
        format: "CLIENTVER=<number>"
        origin: ircd-charybdis
        comment: >
            Indicates presence of given IRC protocol version core capabilities.
            First introduced in ircd-charybdis-3.2(bde6442).

        examples:
            - "CLIENTVER=3.0"

        obsolete: true

    -
        name: CNOTICE
        format: "CNOTICE"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates that the server supports the `"CNOTICE"` command. This is
            an extension to the `"NOTICE"` command.

        examples:
            - "CNOTICE"

    -
        name: CPRIVMSG
        format: "CPRIVMSG"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates that the server supports the `"CPRIVMSG"` command. This
            is an extension to the `"PRIVMSG"` command.

        examples:
            - "CPRIVMSG"

    -
        name: DEAF
        format: "DEAF=<letter>"
        comment: >
            Indicates that the server supports the [`"DEAF"`](usermodes.html#DEAF)
            user mode and the given character is used to represent that mode.

        examples:
            - "DEAF=D"

    -
        name: ELIST
        format: "ELIST=<string>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates that the server supports search extensions to the `"LIST"`
            command. For specific extension characters, read the linked Hardy
            draft and various IRC software.

        examples:
            - "ELIST=CMNTU"

    -
        name: ESILENCE
        format: "ESILENCE=[flags]"
        information: "https://docs.inspircd.org/3/modules/silence/#commands"
        comment: >
            Indicates that the server supports filtering extensions to the `"SILENCE"` command.
            If a value is specified then it contains the supported filter flags.

        examples:
            - "ESILENCE"
            - "ESILENCE=CcdiNnPpTtx"

    -
        name: ETRACE
        format: "ETRACE"
        origin: ircd-ratbox
        comment: >
            Indicates that the server supports the `"ETRACE"` command (IRC
            operators-only), which is similar to `"TRACE"`, but only works on
            nicknames and has a few different options. First introduced in
            ircd-ratbox-2.0beta2(r13975); mentioned in a [footnote of Hardy draft](https://tools.ietf.org/html/draft-hardy-irc-isupport-00#page-25)
            without defining anything about it.

        examples:
            - "ETRACE"

    -
        name: EXCEPTS
        format: "EXCEPTS[=letter]"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates that the server supports "ban exemptions". The letter is
            OPTIONAL and defines the mode character which is used for this.
            When no letter is provided, it defaults to `"e"`.

        examples:
            - "EXCEPTS"
            - "EXCEPTS=e"

    -
        name: EXTBAN
        format: "EXTBAN=<[prefix],types>"
        information:
        comment: >
            Indicates the types of "extended bans" that the server supports.
            `"prefix"` defines the character that indicates an extban to the
            server and `"types"` is a list of characters indicating which
            types of extended bans the server supports. If `"prefix"` does not
            exist, then the server does not require a prefix for extended bans
            and they should be sent with no prefix.

            Extended bans may allow clients to issue bans based on account
            name, SSL certificate fingerprints and other attributes, based on
            what the server software supports. They may also be used in ban
            exemption and invite exemption masks, depending on server software.

        examples:
            - "EXTBAN=~,cqnr"
            - "EXTBAN=~,qjncrRa"
            - "EXTBAN=,ABCNOQRSTUcjmprsz"

    -
        name: FNC
        format: "FNC"
        comment: >
            "Forced Nick Change". Indicates that the server may change a user's
            nickname without the user sending the server a `"NICK"` message.
            Note that servers may do this even if they don't send this token.
            Clients MUST be able to handle this correctly regardless of whether
            this token is presented or not.

        examples:
            - "FNC"

        obsolete: true

    -
        name: INVEX
        format: "INVEX[=letter]"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates that the server supports "invite exemptions". The letter
            is OPTIONAL and defines the mode character, which is used for this.
            When no letter is provided, it defaults to `"I"`.

        examples:
            - "INVEX"
            - "INVEX=I"

    -
        name: KEYLEN
        format: "KEYLEN=<number>"
        origin: ircd-ratbox
        comment: >
            Indicates the maximum length of a channel key. First introduced in
            ircd-ratbox-3.1beta(r28741).

        examples:
            - "KEYLEN=23"

    -
        name: KICKLEN
        format: "KICKLEN=[number]"
        comment: >
            Indicates the maximum length of a kick message. If `"number"` is
            not defined, there is no limit.

        examples:
            - "KICKLEN=180"
            - "KICKLEN="

    -
        name: KNOCK
        format: "KNOCK"
        comment: >
            Indicates support for the `"KNOCK"` command, which is used to
            request an invite to a channel.

        examples:
            - "KNOCK"

    -
        name: LINELEN
        format: "LINELEN=<number>"
        information: "http://rabbit.dereferenced.org/~nenolod/ircv3-harmony/id-wpitcock-ircv3-core.html#rfc.section.3.8.2.1.17"
        comment: >
            Indicates the maximum allowed length of a single IRC message (line)
            in octets. The `"LINELEN"` token defaults to 512. There is no upper
            limit for `"LINELEN"`.

            An alternative to this token is the [oragono.io/maxline-2 capability](https://oragono.io/maxline-2),
            though that has now been deprecated.

        examples:
            - "LINELEN=512"
            - "LINELEN=2048"

        proposed: true

    -
        name: MAP
        format: "MAP"
        comment: >
            Indicates support for the `"MAP"` command, which is used to
            show a representation of how the servers are linked to each other.

            In practice this is command is supported by most networks (but
            may be disallowed for non-IRC operators), even if they don't
            advertise this token. Used by InspIRCd up to 2.0, removed in 3.0.

        examples:
            - "MAP"

        obsolete: true

    -
        name: MAXBANS
        format: "MAXBANS=<number>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the maximum number of bans that may be set on a channel.

            `"MAXBANS"` was obsoleted by `"MAXLIST"`, as that token allows servers
            to specify which limits apply to which channel modes explicitly.

        examples:
            - "MAXBANS=100"

        seealso: "MAXLIST"
        obsolete: true

    -
        name: MAXCHANNELS
        format: "MAXCHANNELS=<number>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the maximum number of channels a client may join. Which
            types of channels this limit does or doesn't apply to is not made
            clear by the token. This limit may only apply to standard (`"#"`)
            channels.

            The `"CHANLIMIT"` token was created to explicitly specify the limits
            that apply to each channel type. `"CHANLIMIT"` should be used instead
            of this token, but this token is still widely-defined by servers.

        examples:
            - "MAXCHANNELS=25"

        obsolete: true
        seealso: "CHANLIMIT"

    -
        name: MAXLIST
        format: "MAXLIST=<mode:number[,mode:number[,...]]>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates how many "variable" modes of `"type A"` that have been
            defined in the `"CHANMODES"` token a client may set in total on a
            channel. The value MUST be specified and is a set of `"mode:number"`
            pairs, where `"mode"` is a number of `"type A"` modes that have been
            defined in `"CHANMODES"` and `"number"` is how many of this mode may
            be set. For more details, read the linked Hardy draft.

        examples:
            - "MAXLIST=beI:25"
            - "MAXLIST=b:25,eI:50"

        seealso: "CHANMODES"

    -
        name: MAXNICKLEN
        format: "MAXNICKLEN=<number>"
        comment: >
            Indicates the maximum length of a nickname that a client may use.
            Other clients on the network may have nicknames longer than this.

        examples:
            - "MAXNICKLEN=9"
            - "MAXNICKLEN=32"

    -
        name: MAXPARA
        format: "MAXPARA=<number>"
        comment: >
            Indicates the maximum number of parameters to any command.

            Used by InspIRCd only, where the default is 32, above the RFC
            specified limit of 15. Other servers may have different limits
            without advertising this token.

        examples:
            - "MAXPARA=32"

        obsolete: true

    -
        name: MAXTARGETS
        format: "MAXTARGETS=<number>"
        comment: >
            Indicates the maximum number of targets for the `"PRIVMSG"` &
            `"NOTICE"` commands.

        examples:
            - "MAXTARGETS=8"

        seealso: "TARGMAX"

    -
        name: METADATA
        format: "METADATA[=number]"
        information: "http://ircv3.net/specs/core/metadata-3.2.html"
        comment: >
            Indicates the maximum number of keys a user may have in their
            metadata. If `"number"` is not specified, there is no limit.

        examples:
            - "METADATA=30"
            - "METADATA"

    -
        name: MODES
        format: "MODES=[number]"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates how many "variable" modes may be set on a channel by a
            single `"MODE"` command from a client. A "variable" mode is defined
            as being a `"type A/B/C"` mode as defined in the `"CHANMODES"` token.
            The value is optional and when not specified indicates that there
            is NO limit places on "variable" modes.

        examples:
            - "MODES=3"
            - "MODES="

        seealso: "CHANMODES"

    -
        name: MONITOR
        format: "MONITOR=[number]"
        information: "http://ircv3.net/specs/core/monitor-3.2.html"
        comment: >
            Indicates the maximum number of targets a user may have in their
            monitor list. If `"number"` is not specified, there is no limit.

        examples:
            - "MONITOR=6"
            - "MONITOR="

        seealso: "WATCH"

    -
        name: NAMESX
        format: "NAMESX"
        comment: >
            Indicates that the `"NAMES"` reply message may be extended to contain
            all possible prefixes, which apply to a user.

            The IRCv3 Working Group recommends that the [`"multi-prefix"`](http://ircv3.net/specs/extensions/multi-prefix-3.1.html)
            client capability is used instead of this token.

        examples:
            - "NAMESX"

        obsolete: true

    -
        name: NETWORK
        format: "NETWORK=<string>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            For INFORMATIONAL PURPOSES ONLY and indicates the name of the IRC
            network that the client is connected to. A client SHOULD NOT use
            this value to make assumptions about supported features on the
            server.

        examples:
            - "NETWORK=EFNet"
            - "NETWORK=Rizon"

    -
        name: NICKLEN
        format: "NICKLEN=<number>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the maximum length of a nickname that a client may use.
            Other clients on the network may have nicknames longer than this.

        examples:
            - "NICKLEN=9"
            - "NICKLEN=32"

    -
        name: OVERRIDE
        format: "OVERRIDE"
        comment: >
            Indicates that IRC operators may override modes and channel
            security. Used by InspIRCd only.

        examples:
            - "OVERRIDE"

    -
        name: PREFIX
        format: "PREFIX=[(modes)prefixes]"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the channel membership prefixes available on this server
            and their order in terms of channel privileges they represent,
            from highest to lowest. If the value is not specified, then NO
            channel membership prefixes are supported by this server. Various
            prefixes used in production are contained in the ["Channel
            Membership Prefixes"](chanmembers.html) list.

        examples:
            - "PREFIX=(ov)@+"
            - "PREFIX=(qaohv)~&@%+"
            - "PREFIX="

    -
        name: SAFELIST
        format: "SAFELIST"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates that the client may request a `"LIST"` command from the
            server without being disconnected due to the large amount of data.
            This token MUST NOT have a value.

        examples:
            - "SAFELIST"

    -
        name: SECURELIST
        format: "SECURELIST"
        comment: >
            Indicates that "secure listing" is enabled and that your initial
            request for a channel list on connect may be denied until you have
            been connected for a certain amount of time. Used by InspIRCd only.

        examples:
            - "SECURELIST"

    -
        name: SILENCE
        format: "SILENCE=[number]"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the maximum number of entries a user may have in their
            silence list. The value is OPTIONAL and if not specified
            indicates that there is no limit. The `"SILENCE"` command seems to
            vary quite a lot between implementations. Most clients include
            client-side filter/ignore commands and servers have the
            `"CALLERID"` client mode as alternatives to this command.

        examples:
            - "SILENCE=15"
            - "SILENCE="

    -
        name: SSL
        format: "SSL=<ip:port[;ip:port[;...]]>"
        comment: >
            Indicates the ports and IP addresses SSL may be found on. Each ip
            and port pair are separated by a colon (:) character and multiple
            port/ip pairs are separated by semicolons (;). Used by InspIRCd up
            to 2.0, removed in 3.0.

        examples:
            - "SSL=1.2.3.4:6668;4.3.2.1:6669;*:6660;"

        obsolete: true

    -
        name: STARTTLS
        format: "STARTTLS"
        comment: >
            Indicates that the server supports upgrading plaintext connections
            to encrypted ones through `"STARTTLS"`. This token must **not** be used
            to detect STARTTLS support, since that means leaking the initial
            connection registration process. The ircv3.1
            [`"tls"`](http://ircv3.net/specs/extensions/tls-3.1.html)
            extension should be used instead. Removed in InspIRCd 3.0.

        examples:
            - "STARTTLS"

        obsolete: true

    -
        name: STATUSMSG
        format: "STATUSMSG=<string>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates that the server supports a method for the client to send
            a message via the `"NOTICE"` command to those people on a channel
            with the specified channel membership prefixes. The value MUST be
            specified and MUST be a list of prefixes as specified in the
            `"PREFIX"` token.

        examples:
            - "STATUSMSG=@+"

        seealso: "PREFIX"

    -
        name: STD
        format: "STD=<string>"
        information: "https://tools.ietf.org/html/draft-brocklesby-irc-isupport-03"
        comment: >
            Attempts to indicate the standard to which the ISUPPORT
            implementation is written. Whether this means tokens or simply
            syntax is not specified. This doesn't seem to be that useful, given
            the age of all these specifications and how it is not officially
            specified nor used all that much.

        examples:
            - "STD=i-d"

        obsolete: true

    -
        name: TARGMAX
        format: "TARGMAX=[cmd:[number][,cmd:[number][,...]]]"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Certain commands from a client MAY contain multiple targets. This
            token defines the maximum number of targets may be specified on
            each of these commands. The value is OPTIONAL and is a set of
            `"cmd:number"` pairs, where `"cmd"` refers to the specific command
            and `"number"` refers to the limit for this command.

            If the number is not specified for a particular command, then that
            command does not have a limit on the maximum number of targets.

            If the `"TARGMAX"` parameter is not advertised or a value is not sent
            then a client SHOULD assume that no commands except the `"JOIN"` and
            `"PART"` commands accept multiple parameters.

        examples:
            - "TARGMAX=PRIVMSG:3,WHOIS:1,JOIN:"
            - "TARGMAX="

        seealso: "MAXTARGETS"

    -
        name: TOPICLEN
        format: "TOPICLEN=<number>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the maximum length of a topic that a client may set on a
            channel. Channels on the network MAY have topics with longer
            lengths than this.

        examples:
            - "TOPICLEN=120"

    -
        name: UHNAMES
        format: "UHNAMES"
        comment: >
            Indicates that the `"NAMES"` reply message may be extended to contain
            the full hostmask of every user listed. Must NOT have a value.

            The IRCv3 Working Group recommends that the [`"userhost-in-names"`](http://ircv3.net/specs/extensions/userhost-in-names-3.2.html)
            client capability is used instead of this token.

        examples:
            - "UHNAMES"

        obsolete: true

    -
        name: USERIP
        format: "USERIP"
        comment: >
            Indicates support for the `"USERIP"` command, which is used to
            request the direct IP address of the user with the specified
            nickname.

            This might be supported by networks that don't advertise this
            token.

        examples:
            - "USERIP"

    -
        name: USERLEN
        format: "USERLEN=[number]"
        information: "http://rabbit.dereferenced.org/~nenolod/ircv3-harmony/id-wpitcock-ircv3-core.html#rfc.section.3.8.2.1.16"
        comment: >
            Indicates the maximum length of an username in octets. If
            `"number"` is not specified, there is no limit.

        examples:
            - "USERLEN=12"
            - "USERLEN="

        proposed: true

    -
        name: VBANLIST
        format: "VBANLIST"
        comment: >
            Indicates that list mode sizes may vary from channel to channel.
            Used by InspIRCd only, always present before v3.4.0, removed in v4.

        examples:
            - "VBANLIST"

        obsolete: true

    -
        name: VLIST
        format: "VLIST=<modes>"
        comment: >
            Indicates that the specified list modes may be larger than the value specified in MAXLIST.
            Used by InspIRCd v3.4.0+.

        examples:
            - "VLIST=be"

    -
        name: WALLCHOPS
        format: "WALLCHOPS"
        comment: >
            Indicates that the server supports messaging channel operators,
            either through a command like `"WALLCHOPS #channel"` or a
            `"STATUSMSG"`-like notice like `"NOTICE @#channel"`, with most
            implementations only handling the latter.

            This command has been obsoleted by the `"STATUSMSG"` token and the
            `"STATUSMSG"` token seems to be more widely used.

        examples:
            - "WALLCHOPS"

        seealso: "STATUSMSG"
        obsolete: true

    -
        name: WALLVOICES
        format: "WALLVOICES"
        comment: >
            Indicates that the server supports messaging channel voiced users,
            either through a command like `"WALLVOICES #channel"` or a
            `"STATUSMSG"`-like notice like `"NOTICE +#channel"`, with most
            implementations only handling the latter.

            This command has been obsoleted by the `"STATUSMSG"` token and the
            `"STATUSMSG"` token seems to be more widely used.

            Unlike `"WALLCHOPS"`, this wasn't included in any of the original
            drafts and it's much less common.

        examples:
            - "WALLVOICES"

        seealso: "STATUSMSG"
        obsolete: true

    -
        name: WATCH
        format: "WATCH=<number>"
        information: "https://tools.ietf.org/html/draft-hardy-irc-isupport-00"
        comment: >
            Indicates the maximum number of nicknames a user may have in their
            watch list.

            The `"MONITOR"` command is aimed at being a more consistent
            alternative to this command and documentation for it may be found
            on the [IRCv3 website](http://ircv3.net/specs/core/monitor-3.2.html).

        examples:
            - "WATCH=100"

        seealso: "MONITOR"

    -
        name: WHOX
        format: "WHOX"
        comment: >
            Indicates that the server supports extended syntax of the `"WHO"` command.