The loose specification for the capabilities extension protocol was harder for me to follow than the RFC, and as a result, the CAP command is not specification compliant. Specifically, it doesn't match the server responses for the protocol. These look like so: :server CAP * ACK :multi-prefix.
The loose specification for the capabilities extension protocol was harder for me to follow than the RFC, and as a result, the CAP command is not specification compliant. Specifically, it doesn't match the server responses for the protocol. These look like so:
:server CAP * ACK :multi-prefix.