> Just been looking on amsterdam.nl.eu.undernet.org, and noticed the new
> ACCOUNT reply in the /whois, but it seems to be backwards. For
> example:
The reply is actually technically:
:Amsterdam.NL.EU.undernet.org 330 Valcor Valcor Valcor :is logged in as
(Assuming you did the /whois on yourself, which should be the only way
you can get the type of response you saw.)
Now the first "Valcor" is simply the requestor's nickname. The second
one is the target of the /whois. The third is the account name. The
last argument is where it is intentionally. This order makes it easier
to parse the reply message for the username. This is also consistent
with other elements of the /whois reply: 313 ("is an IRC Operator")
and 317 (idle time and sign-on time). This allows another network
(say) to change the "is logged in as" portion of the reply without
messing up scripts.
Until the clients incorporate support for this numeric, it'll either
look a little funny, or you'll have to use a script to reorder the
reply for human ordering. I'm personally against reordering the reply
in the server code because of the benefits I've already mentioned...
--
Kevin L. Mitchell <[EMAIL PROTECTED]>
