Open Bug 1082072 Opened 10 years ago Updated 2 years ago

Wait for irc identification services to identify, then join channels

Categories

(Chat Core :: IRC, defect)

defect

Tracking

(Not tracked)

People

(Reporter: hadirezaei, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; rv:11.0) like Gecko

Steps to reproduce:

On freenode, some channels require you to be registered and  identified on the server. Instantbird quickly joins the channel before identifying with nickserv.


Actual results:

This results in the channel blocking you out, because you joined it before  being identified by nickserv. so you have to manually join the channels again.


Expected results:

I think the solution is that Instantbird first waits for all the identifications to complete, (either fail or success), then after a delay atempt to join the channels that you have defined for it in autojoin.
Some more discussion about this: http://log.bezut.info/instantbird/141008/#m167
Status: UNCONFIRMED → NEW
Component: Account manager → IRC
Ever confirmed: true
Product: Instantbird → Chat Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.