JumpNetwork is broken when using different nicks #100

Closed
opened 2026-10-05 03:58:59 +02:00 by adam · 1 comment
Owner

J0rd4n` reported this.

J0rd4n` reported this. <!-- github-sync-id:4238728 -->
adam closed this issue 2026-10-05 03:58:59 +02:00
Author
Owner

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 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#100