According to this page (which, according to Havvy on the #rust IRC channel, "should be considered for all intents and purposes the living IRC specification"), 005 is RPL_ISUPPORT.
This crate incorrectly interprets 005 as RPL_BOUNCE. 005was formerly RPL_BOUNCE, but that has been moved to 010.
To fix this issue:
irc::client::data::response::Response needs a RPL_ISUPPORT variant added, as it does not currently have one
A response with a numeric of 005 should be interpreted as RPL_ISUPPORT
A response with a numeric of 010 should be interpreted as RPL_BOUNCE
For reference, here are the two ISUPPORT messages I received from Rizon's IRC server when connecting to it:
:solenoid.rizon.net 5 ircfs CALLERID CASEMAPPING=rfc1459 DEAF=D KICKLEN=180 MODES=4 PREFIX=(qaohv)~&@%+ STATUSMSG=~&@%+ EXCEPTS=e INVEX=I NICKLEN=30 NETWORK=Rizon MAXLIST=beI:250 MAXTARGETS=4 :are supported by this server
:solenoid.rizon.net 5 ircfs CHANTYPES=# CHANLIMIT=#:500 CHANNELLEN=50 TOPICLEN=390 CHANMODES=beI,k,l,BCMNORScimnpstz WATCH=60 NAMESX UHNAMES AWAYLEN=180 ELIST=CMNTU SAFELIST KNOCK :are supported by this server
aatxe
commented
7 years ago
According to this page (which, according to Havvy on the #rust IRC channel, "should be considered for all intents and purposes the living IRC specification"),
005isRPL_ISUPPORT.This crate incorrectly interprets
005asRPL_BOUNCE.005was formerlyRPL_BOUNCE, but that has been moved to010.To fix this issue:
irc::client::data::response::Responseneeds aRPL_ISUPPORTvariant added, as it does not currently have one005should be interpreted asRPL_ISUPPORT010should be interpreted asRPL_BOUNCEFor reference, here are the two
ISUPPORTmessages I received from Rizon's IRC server when connecting to it: