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

Server-forced nickname on connect is not detected #86

Open
jhartikainen opened this issue Feb 9, 2019 · 0 comments
Open

Server-forced nickname on connect is not detected #86

jhartikainen opened this issue Feb 9, 2019 · 0 comments

Comments

@jhartikainen
Copy link

Some servers force a specific nickname on your client as you connect - regardless of what you ask for. In such cases, exirc does not send certain events correctly.

For example, if we use Client.logon and ask for the nickname example, but the server gives us another nickname, the {:joined, channel} message is not sent when joining channels because exirc thinks our nick is example when it's actually something different.

This type of "forced nickname" can be detected from the RPL_YOURHOST / 002 message or some of the other "greeting" type messages that arrive when connecting, since those messages contain your actual nickname at that point.

I wonder if this is something exirc should support? I don't know whether this behavior is fully spec-compliant, so not sure if it's something that should be handled by this library. In case it's useful, this is happening with Twitch's IRC server which is already not entirely compliant from what I can tell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant