Upon receiving either a CAP LS or CAP REQ command during connection registration, the server MUST not complete registration until the client sends a CAP END command to indicate that capability negotiation has ended. This allows clients to request their desired capabilities before completing registration.
It seems that ZNC 1.8.2 suspends registration after CAP LS but not after CAP REQ.
In the [Client Capability Negotiation spec](https://ircv3.net/specs/extensions/capability-negotiation) it says:
> Upon receiving either a `CAP LS` or `CAP REQ` command during connection registration, the server MUST not complete registration until the client sends a `CAP END` command to indicate that capability negotiation has ended. This allows clients to request their desired capabilities before completing registration.
It seems that ZNC 1.8.2 suspends registration after `CAP LS` but not after `CAP REQ`.
<!-- github-sync-id:1091830597 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In the Client Capability Negotiation spec it says:
It seems that ZNC 1.8.2 suspends registration after
CAP LSbut not afterCAP REQ.Something along the lines of the following should do it.