From the source code The assumption is that the client got this nick from the 001 reply. I have tested this on a few clients I have locally they seem to cope fine.
ZNC expects the client to take the nickname from the 001 on both connecting to ZNC and JumpNetwork. I wonder if the client J0rd4n is using is broken when it tries to connect to ZNC with one nick, and ZNC gives it another nick from buffer in 001. Otherwise perhaps it ignores a 001 if we are already registered, in which case we should send a NICK change.
Which client is J0rd4n using?
From the source code `The assumption is that the client got this nick from the 001 reply`. I have tested this on a few clients I have locally they seem to cope fine.
ZNC expects the client to take the nickname from the 001 on both connecting to ZNC and JumpNetwork. I wonder if the client `J0rd4n` is using is broken when it tries to connect to ZNC with one nick, and ZNC gives it another nick from buffer in 001. Otherwise perhaps it ignores a 001 if we are already registered, in which case we should send a NICK change.
Which client is `J0rd4n` using?
<!-- github-comment-id:5698925 -->
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.
J0rd4n` reported this.
From the source code
The assumption is that the client got this nick from the 001 reply. I have tested this on a few clients I have locally they seem to cope fine.ZNC expects the client to take the nickname from the 001 on both connecting to ZNC and JumpNetwork. I wonder if the client
J0rd4nis using is broken when it tries to connect to ZNC with one nick, and ZNC gives it another nick from buffer in 001. Otherwise perhaps it ignores a 001 if we are already registered, in which case we should send a NICK change.Which client is
J0rd4nusing?