When I connect with my client (mIRC) to ZNC I see that it outputs the NAMES for each channel in NAMESX-format. However, it does not output in UHNAMES-format eventhough the client supports it (I see it sending it in debug with PROTOCTL, it sends one for NAMESX and a new one for UHNAMES).
Once connected, however, if I /hop a channel or I am already connected while ZNC jumps servers, then I get the correct UHNAMES-formatted NAMES output.
This almost looks like some kind of race condition between the client sending its PROTOCTL capabilities upon initial connection and ZNC already sending its NAMES output to the client.
When I connect with my client (mIRC) to ZNC I see that it outputs the NAMES for each channel in NAMESX-format. However, it does not output in UHNAMES-format eventhough the client supports it (I see it sending it in debug with PROTOCTL, it sends one for NAMESX and a new one for UHNAMES).
Once connected, however, if I /hop a channel or I am already connected while ZNC jumps servers, then I get the correct UHNAMES-formatted NAMES output.
This almost looks like some kind of race condition between the client sending its PROTOCTL capabilities upon initial connection and ZNC already sending its NAMES output to the client.
<!-- github-sync-id:29022379 -->
The race is: mIRC sends the PROTOCOL command and at the same time, ZNC already sends the channel joins.
This is why this can be requested with CAP REQ userhost-in-names before login. That way, there is no race.
The race is: mIRC sends the PROTOCOL command and at the same time, ZNC already sends the channel joins.
This is why this can be requested with CAP REQ userhost-in-names before login. That way, there is no race.
<!-- github-comment-id:37098679 -->
Oh, thanks for the tip, a little pre-logon script is in order here then. But howcome it does send NAMESX-formatted output?
Edit: Nevermind, it seems that mIRC sends a CAP request for multi-prefix.
Oh, thanks for the tip, a little pre-logon script is in order here then. But howcome it does send NAMESX-formatted output?
Edit: Nevermind, it seems that mIRC sends a CAP request for multi-prefix.
<!-- github-comment-id:37099788 -->
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.
When I connect with my client (mIRC) to ZNC I see that it outputs the NAMES for each channel in NAMESX-format. However, it does not output in UHNAMES-format eventhough the client supports it (I see it sending it in debug with PROTOCTL, it sends one for NAMESX and a new one for UHNAMES).
Once connected, however, if I /hop a channel or I am already connected while ZNC jumps servers, then I get the correct UHNAMES-formatted NAMES output.
This almost looks like some kind of race condition between the client sending its PROTOCTL capabilities upon initial connection and ZNC already sending its NAMES output to the client.
The race is: mIRC sends the PROTOCOL command and at the same time, ZNC already sends the channel joins.
This is why this can be requested with CAP REQ userhost-in-names before login. That way, there is no race.
Oh, thanks for the tip, a little pre-logon script is in order here then. But howcome it does send NAMESX-formatted output?
Edit: Nevermind, it seems that mIRC sends a CAP request for multi-prefix.
I don't know, perhaps mIRC requests that one per CAP and doesn't to so for userhost-in-names / UHNAMES?
Yes, that was exactly it.