The CTCP support in irssi v0.7.98.4 seems incomplete.

Even though there isn't AFAIK any standardized CTCP specification, the
specification[1] written by Klaus Zeuge, Troy Rollo and Ben Mesander
defines the following extended data types:
- SED
- FINGER
- SOURCE
- USERINFO
- CLIENTINFO
- ERRMSG
- TIME

While I don't think that all of those need to be implemented (and the
specification doesn't even say which ones are mandatory and which ones
are optional), I think that CLIENTINFO is a pretty important one since
it advertizes the client's capabilities.

Actually, an Internet Draft[2] dated 2 February 1997 written by
Michael McLagan makes things more formal, and defines CLIENTINFO as
required and SED, FINGER, ERRMSG and SOURCE as deprecated.

Therefore, I think that it would be a good thing (tm) to support CTCP
CLIENTINFO.

Thanks.

Regards,

Hugo

  1. http://www.irchelp.org/irchelp/rfc/ctcpspec.html
  2. http://www.invlogic.com/irc/ctcp.html
-- 
Hugo Haas <[EMAIL PROTECTED]> - http://larve.net/people/hugo/
- I know you feel bad about the juice incident, but I'm sure you can
make up for it somehow. - That's it! Somehow! -- Homer Jay

Reply via email to