Bug 150074 - Re-authenticate with services after nick changes when necessary
Summary: Re-authenticate with services after nick changes when necessary
Status: CONFIRMED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.4
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-21 21:17 UTC by Douglas E. Warner
Modified: 2013-04-15 00:49 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Douglas E. Warner 2007-09-21 21:17:41 UTC 
Version:           1.0.1 (using KDE KDE 3.5.7)
Installed from:    Fedora RPMs

When returning from away where I have changed my nick I sometimes need to re-identify myself (Freenode so far, it seems).  It would be nice if konversation would re-identify when returning from away (maybe only if prompted by NickServ?).

example:
[07:41] [Away] You are now marked as being away.

[06:56] [Away] You are no longer marked as being away.
[06:57] [Notice] -NickServ- This nickname is owned by someone else
[06:57] [Notice] -NickServ- If this is your nickname, type /msg NickServ IDENTIFY <password>
Comment 1 Xavier Poirot 2011-09-02 08:43:30 UTC 
It would be also nice to be identified automatically only when NickServ prompts it (otherwise you get an error "this nick is not registered" on other random servers you're not in).

Away is not the only target for re-authentication, there's also after ghosting.