| Summary: | Automatically attempt to switch to primary nickname | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | kdebugs |
| Component: | general | Assignee: | Konversation Developers <konversation-devel> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | cfeck, diego.ml, email.xenophon, hein, oliver.henshaw |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | recover nick and identify | ||
|
Description
kdebugs
2005-06-18 17:37:28 UTC
It might be interesting to combine this feature with the "Auto identify" thing, so that konversation issues a "/nickserv recover" command to get the nick back... It's a good and useful feature request, but as Felix' comment indicates you'd want to be able to accomodate a variety of network services. Therefore, this would best be realized as a plug-in or script - for which we currently lack the required facilities. As it stands, it will probably be a while before we turn our attention back on this one. Created attachment 21021 [details] recover nick and identify The attached program sort of does what is requested. It is assumed that the nick defined first in each identity is the primary nick you want to set. (->[0] means "first" in the program.) The program looks at each connected server's current nick. If it is equal to one of the identities' primary nick, no action is taken. Else it looks at each identity's other nicks to find out which identity the current nick could come from. This is very hackish and can pick an unexpected primary nick if you reuse nicks across identities. I did it this way because currently there is no DCOP interface to determine the identity associated with a connected server, only the nicks. If it cannot determine a suitable identity, no action is taken. This is the case if you manually change your nick to something that is not in any identity's nicks. Then the current nick is changed to the primary nick and the program starts over for the next connected server. You have to edit the source to edit passwords for Services. I would have attempted to make integration with kwalletmanager, but the assignee in bug 94311 can't get his arse off the ground. The Services passwords are associated with regular expressions describing the server name. Again, this is due to a shortcoming in the DCOP interface, I am unable to query the server names associated with the identities. By choosing regexp instead of strings for server names, I give you more flexibility. But also it lies in your own responsibility to make sure the expressions do not match several connected server names and accidently pick the wrong one, since the matches are done in an undetermined order. We are still lacking the hooks to calls programs on reconnect events, or schedule events regularly, as this bug's submitter suggests. There's also a related trick on the Wiki: http://konversation.kde.org/wiki/Ghosttrick I was filing a similar request when found this, although with topic: "Reclaim primary nick(s) after temporary connection loss" which might describe it better. Anyway, plugins, scripts whatever, users need this feature. *** Bug 205609 has been marked as a duplicate of this bug. *** Still present in Konversation 1.5. Would be really useful for weak connections. (In reply to comment #4) > There's also a related trick on the Wiki: > http://konversation.kde.org/wiki/Ghosttrick The trick page has moved here: http://userbase.kde.org/Konversation/Scripts/Ghosttrick *** Bug 214338 has been marked as a duplicate of this bug. *** |