Re: bug ?

[Perry Lorier <perry@coders.net>]

> > Yes.  But until they do, couldn't xchat treat them as different
> > nicks?  If two of them can never be online at once, treating them as
> > different nicks surely won't harm efnet, ircnet, etc...
> 
> Not easily. Someone would have to put in a server dependant string
> comparision function. Too much work to fix something that's not broken in
> xchat.
> 

Well, consider what happens when you have someone online as "|foo|", and
you /query \foo\, and they reply back, but the "source" is now "|foo|",
should xchat open a new query window? no.

On Undernet, many moons ago, you would send:
 "JOIN #|foo|"
and the server would send back
 ":nick!user@host JOIN #\Foo\"
(since it sent back what it's internal name was).  This confused clients
that weren't smart enough to realise that these were the same channel,
causing Undernet no end of problems, so in the next version it was
changed back to send back what the client sent it on the Join to stop
these clients effectively hanging.  However the server doesn't store
what each client thinks a channel is called, so when you recieve a
message from a server, it will have the case of whoever created the
channel gave it. (in 2.10.11 at least)

Undernet states "CHARSET=rfc1459" in the 005 to say that it follows the RFC, 
I dunno if DALnet does CHARSET=latin1 or ascii or whatever.  Although,
interestingly enough the RFC even gets it wrong.  In section 2.2 it
states:

   Because of IRC's scandanavian origin, the characters {}| are
   considered to be the lower case equivalents of the characters []\,
   respectively. This is a critical issue when determining the
   equivalence of two nicknames.

This misses the fact that IRC also treats "^" and "~" to be the same
charactors (although usually "~" is disallowed in nicknames, go figure)

-- 
Don't feed the bats tonight.
--
XChat-discuss: mailing list for XChat users
Archive:       http://mail.nl.linux.org/xchat-discuss/