Summary: | konversation disregards "Follow nick changes" when DCC chat conversations take place | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | Niek Beernink <n.beernink> |
Component: | general | Assignee: | Konversation Developers <konversation-devel> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Niek Beernink
2006-08-06 17:14:03 UTC
IMO, this is a WONTFIX. In a technical sense, a DCC Chat once started is decoupled from a specific server connection, i.e. when you start a DCC chat with someone and on the IRC server that someone leaves and is replaced with a different person who happens to occupy the same nick, the DCC Chat is entirely unaffected. It's not a query. And shouldn't track nick changes that don't affect it. Addendum: We've pretty much reached a consensus now that tracking nick changes for DCC chats doesn't make sense. However, this report also confuses the issue, which makes it a bit messy to deal with. Following nick changes to reuse the same logfile presently only happens for the duration of a query being open, i.e. a new query will be started with the then-current nickname and a logfile with that nickname be created. Close this as WONTFIX as pertaining to the report title. |