Project

General

Profile

Feature #652

Move auto-identify before reconnect

Added by yofel about 15 years ago. Updated over 14 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/31/2009
Due date:
% Done:

0%

Estimated time:
OS:
Any

Description

I'm havin an annoying problem with the auto-identify behaviour here. When my connection gets resetted the core reconnects to all channels what takes more than 1 minute here. But some nickservs don't wait more then a minute for the identify command and change my nick to Guestxxxx. Can the identify commands please be sent before rejoining the channels?

History

#1 Updated by mcuelenaere almost 15 years ago

I'm having a similar issue: when connecting to Freenode, Quassel joins the channels before I'm identified; so my IRC cloak isn't activated yet and my IP address etc is seen by others.

#2 Updated by Sputnick over 14 years ago

  • Status changed from New to Confirmed

Well, the actual problem is that NickServ's reply arrives too late. There is no portable way to avoid this currently (as the various nick services are network-dependent, we don't feel like hardcoding a wait for a certain reply etc). Maybe I find a nice way to allow a configurable delay though.

For the time being, Freenode supports setting your nickserv password as server password, in which case you'll be already identified when you go online. That's at least a workaround for now.

#3 Updated by mcuelenaere over 14 years ago

Sputnick wrote:

For the time being, Freenode supports setting your nickserv password as server password, in which case you'll be already identified when you go online. That's at least a workaround for now.

Ok, thanks; the workaround works.

Also available in: Atom PDF