-
Notifications
You must be signed in to change notification settings - Fork 16
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
survive nick changes #123
Comments
Nicks are registered with a nickserv and authenticated on most networks. Usernames are arbitrary strings that the client can set to whatever it wants. Is there a use case where users frequently change nicks? |
"Matthew M. Boedicker" [email protected] writes:
in my experience, no one sets the username (i just leave it empty on |
Nicks are potentially long-lived (if properly registered) and unique, while usernames are neither unique nor long-lived (because hardly anybody cares, so if someone switches clients they won't bother changing it for example). |
Thanks a lot for GitHubbing @weechatter ! |
I agree that nicks are still the best choice for the primary identifier. Automatic nick change detection may open up new attack vectors. |
if any end of the conversation changes nickname, the session is dropped and authentication status is lost. wouldn't it be better to identify people by something more stable, like usernames? maybe use the host mask if available (not an ip address i mean).
The text was updated successfully, but these errors were encountered: