[13:23:24] <Sho_> JontheEchidna: Already implemented for ~seven years
[13:24:10] <JontheEchidna> Sho_: the reporter is using 1.2, so maybe it's
broken?
[13:25:02] <Sho_> JontheEchidna: no, it's more likely the reporter doesn't know
how IRC works (not the reporter's fault necessarily)
[13:25:22] <Sho_> JontheEchidna: IRC is stateless, the server has no notion of
queries, it just sees messages from A to B and from B to A
[13:25:43] <Sho_> JontheEchidna: Since the server doesn't know there's a query,
it has no reason to inform the participants of nickchanges
[13:26:02] <Sho_> JontheEchidna: Konvi's only source for nickchange info are
channels the participants are both in
[13:26:58] <Sho_> JontheEchidna: So if we were to have a query now, and you'd
change your nick to TheMostAwesomeJonOfAll, Konversation would rename the
query, since the IRC server tells it JontheEchidna renamed himself to
TheMostAwesomeJonOfAll because we're both in #konversation
[13:27:17] <JontheEchidna> right
[13:27:18] <Sho_> JontheEchidna: If we're not on any channels together, Konvi
has no way of knowing you renamed yourself to TheMostAwesomeJonOfAll though
[13:27:30] <JontheEchidna> mind if I paste this log in the bug report?
[13:28:16] <Sho_> hold on a sec before pasting the log
[13:28:27] <Sho_> Konversation could do one other thing
[13:28:54] <Sho_> IRC users have a "mask" that comprises their identity on the
network, in the form of nickname!id...@host
[13:29:25] <Sho_> for example, you're
jontheechidna!~jonat...@ubuntu/member/jontheechidna right now
[13:29:50] <Sho_> so let's say we have a query open, and you rename yourself to
TheMostAwesomeJonOfAll and send me another message
[13:30:18] <JontheEchidna> ah, the mask would be the same as long as I was
registered
[13:30:33] <Sho_> this time you're
themostawesomejonofall!~jonat...@ubuntu/member/jontheechidna (assuming the
nickchange doesn't cause your identification with services to be voided and
your host cloak to be dropped, that could happen on some networks)
[13:30:51] *** gentoo is now known as Ebashorg.
[13:31:00] <Sho_> so it could compare the part after the nick and decide you're
the same and rename the "JontheEchidna" query
[13:31:15] <Sho_> i.e. it would rename the query when it gets a new message,
not when the nickchange actually occurs
[13:31:21] <Sho_> however, this would be potentially insecure
[13:32:09] <Sho_> you have a nick nickserv-account-specific cloak, but a normal
user hostmask is more like "~<default ident set by irc client>@<current
dynamically assigned ip>.<ISP>.<tdl>"
[13:32:57] <Sho_> so thanks to ISPs handing out dynamic IPs etc. there's a slim
chance that it's not actually the same person sending the message as the person
with the old nick
[13:33:27] <Sho_> some IRC clients do this anyway, but the majority - like
Konversation - don't, since it's in principle not secure
[13:33:35] <Sho_> the only reliable nickchange info is via shared channels
[13:34:21] <Sho_> so, that covers things
[13:34:34] <Sho_> ready for pasting
[13:34:57] <JontheEchidna> final verdict == wontfix?
[13:35:44] <Sho_> JontheEchidna: more like "WORKSFORME" I guess, it's not like
it doesn't have the feature to automatically rename queries, it's just that
there are constraints to when it can do so
[13:36:08] <Sho_> actually it's INVALID even
** Changed in: konversation (Ubuntu)
Status: New => Invalid
--
open query windows should follow nick changes
https://bugs.launchpad.net/bugs/498996
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to konversation in ubuntu.
--
kubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
