Client joins channel before nickserv responds to IDENTIFY command.

[zenwhen]

Issue: Client joins channel before nickserv responds to IDENTIFY command.

Description: On some networks, freenode being one of them, your IP is displayed as part of your join message to all users in a channel upon your entrance. This happens to everyone unless you request or are assigned a hostmask which blocks this info from view by the public.

It has been pointed out to me that my identification to nickserv is happening after I join channels, thus the added security of having a hostmask is being wasted. Apparently a few other clients such as IRSSI wait until a response is received from nickserv on the IDENTIFY command before joining channels.

If you could change this ordering, it would make me much less likely get get ddos'd by a user. I am an op in a couple Ubuntu project channels and there is a high risk of that due to rowdy users in channels seeking retribution from bands and such.

[jane]

Hmm, this is a dupe of a couple tickets and related to another: #192, #88, #1022

Personally, I've noticed that I may be sending the command to identify with nickserv but nickserv doesn't acknowledge it until after I've joined my channels (which gets me joined to #register-with-nickserv instead of #rubyonrails or whatever channel requires you be registered to join, etc.). Perhaps a /timer command (#1022) might help...waiting for a response from services may not work because not all services are the same.

[akempgen]

[4164] might improve things if using the nickname/password settings. related to #1380.

[akempgen]

Fixed in [4242].