Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

!nick has unexpected behaviour when the target is already in use (!nick NickInUse ==> Nick changed from OldNick to NickInUse[m]1) #751

Open
Mikaela opened this issue May 11, 2019 · 0 comments
Labels
T-Defect Bugs, crashes, hangs, vulnerabilities, or other reported problems.

Comments

@Mikaela
Copy link
Contributor

Mikaela commented May 11, 2019

When user attempts to change their nickname with !nick to something that is already in use in the IRC network, there is no error message from the appservice, but instead my nick is changed weirdly.

For example:

  1. I am @mikaela:privacytools.io or mikaela[m] at IRCnet.
  2. I change my nick with !nick Mikaela
  3. @ircnet:irc.snt.utwente.nl responds Nick changed from 'Mikaela[m]' to 'mikaela[m]1'.

In this case I happen to know that nick Mikaela is used by my ZNC, but I would still expect the appservice to tell me something like "The nickname Mikaela is already in use on irc.snt.utwente.nl" instead of changing my nickname to a third nick that I didn't ask it to do.

I have understood this issue to frequently cause confusion especially to users who don't have previous experience with IRC (which would tell Mikaela[m]10: Nickname is already in use. by the way) as the user would attempt to run the command again ("Nick changed from 'mikaela[m]1' to 'mikaela[m]2'." as now there is helpfully a fourth nick).

@jaller94 jaller94 added the T-Defect Bugs, crashes, hangs, vulnerabilities, or other reported problems. label May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect Bugs, crashes, hangs, vulnerabilities, or other reported problems.
Projects
None yet
Development

No branches or pull requests

2 participants