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

survive nick changes #123

Open
fauno opened this issue Nov 24, 2015 · 5 comments
Open

survive nick changes #123

fauno opened this issue Nov 24, 2015 · 5 comments

Comments

@fauno
Copy link
Contributor

fauno commented Nov 24, 2015

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).

@mmb
Copy link
Owner

mmb commented Nov 26, 2015

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?

@fauno
Copy link
Contributor Author

fauno commented Nov 26, 2015

"Matthew M. Boedicker" [email protected] writes:

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?

in my experience, no one sets the username (i just leave it empty on
weechat, no idea what pidgin decides to use as username) but you can
change your nick anytime for fun and profit. most people i talk with
don't even bother to register them... and you can always end with an
alternative nick if your connection isn't stable.

@tribut
Copy link
Collaborator

tribut commented Nov 26, 2015

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).
Nick change detection would be an interesting feature (for example using the full user@host while the conversation is active), but otherwise we should really stick with nicks.

@Mikaela
Copy link
Contributor

Mikaela commented Nov 26, 2015

2015-11-26 09:14:00+0200 < Mikaela> #123: WeeChat supports account-notify which makes the IRCd tell it when someone identifies or unidentifies. It also performs /who to everyone on all channels on join to het the accounts of people who joined the channel before.  Would it help here?
2015-11-26 09:14:32+0200  * Mikaela cannot GitHub at the moment
2015-11-26 09:17:32+0200  * nils_2 can github
2015-11-26 09:35:11+0200 < Mikaela> Feel free,  I am going to take a shower

Thanks a lot for GitHubbing @weechatter !

@mmb
Copy link
Owner

mmb commented Dec 3, 2015

I agree that nicks are still the best choice for the primary identifier. Automatic nick change detection may open up new attack vectors.

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

No branches or pull requests

4 participants