[Pidgin] #9490: +a IRC Not reconized.

[Pidgin]

#9490: +a IRC Not reconized.
----------------------+-----------------------------------------------------
 Reporter:  dbdii407  |        Owner:  elb
     Type:  defect    |       Status:  new
Milestone:            |    Component:  IRC
  Version:  2.5.7     |   Resolution:     
 Keywords:            |  
----------------------+-----------------------------------------------------

Comment(by N00D135):

 I felt I must contribute to this thread, so here goes.

 I run an IRC network myself, which has the full modeset
 PREFIX=(qaohv)~&@%+  this is sent on connect to any irc client connecting,
 so thusly Pigdin can read this information and then set the correct modes
 on usernames, if the PREFIX=(qaohv)~&@%+ line is _always_ read in and
 interpreted, any new irc modes which pop up (such as !y as inspircd has
 with the operprefix module) this simply means your IRC Client can deal
 with and cope with any modesets sent.

 The server support section is sent via Numeric 005, thusly:
 20:13:45  -> {irc_server_name} {005} { [usernickname] [MODES=12]
 [CHANTYPES=#]  [PREFIX=(qaohv)~&@%+]
 [CHANMODES=beI,kfL,lj,psmntirRcOAQKVCuzNSMTG]   CASEMAPPING=ascii]
 [EXTBAN=~,cqnr]  [ELIST=MNUCT]  [are supported by this server] }

 Provided you write your client to read in numeric 005 and then parse the
 details specified after PREFIX= into any usermodes as above, youre IRC
 client will then support any usermodes the server sends out, plus they are
 always sent in Highest>Lowest order, ~ being highest operator, in this
 case.

 For instance if you download mschat, that only supports @%+ out of the
 box, so ~& users appear below the rest, and you cannot use menus on the
 names, as it gives a ~user: not found message, because they wrote thier
 client based entirely from the RFC's which only actually state @+ as
 specific channel usermodes, ~&% modes were added more recently, but when
 the RFC's were written only @+ existed.

 Please feel free to contact me if you need further explanation, I'd be
 happy to help you, But if you do read in the 005 numerics and act upon the
 PREFIX= part, Your IRC Client will then be 100% compatible with any IRC
 server in existance, of course if you do not get a 005 reply (I've not
 seen many which do not send this info across) but for those which do not
 send the information to pigdin, I'd assume PREFIX=(qaohv)~&@%+ in all
 cases and then you know you are protected against non-existant modes.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9490#comment:8>
Pidgin <http://pidgin.im>
Pidgin