On Thu, 2002-08-22 at 02:15, Thomas J. Stens=E5s wrote: > While there is not much use in bringing this up for certain individuals o= n=20 > this list which still think the aging RFC is worth anything to any of the= =20 > major networks, IRC is changing and belive it or not, its really not that= =20 > difficult to support the wide varity of channel modes or channel access m= odes=20 > out there. mIRC does it, and have done for some time.
Yes, but it's not fully standardized nor is it likley to gain support in amirc since most of amirc will have to be rewritten for it afair. > Undernet supports the 005 numeric in reporting both channel access prefix= es=20 > and channelmodes. And as all IRCd's it also reports the channelmodes the=20 > server supports and also tells the connecting client how to interpret the= =20 > various channel modes: Yes, They adopted DALnets "standard" and changed their /MAP numeric to something else. =20 [Snip: Much ircd info] Many do, but i doubt that *all* do. Forexample, Universal dosn't (old prefork undernet). =20 > Now, fine.. continue arguing that its in violation of the RFC which no on= e on=20 > this planet actually follow anymore. There are however users of AmIRC out= =20 > there which wouldnt mind seeing their client being able to handle how IRC= =20 > actually work today, and the major IRCd coding teams have worked out a wa= y to=20 > make easy to support for client authors. All im trying to point out here = is=20 > that its possible to do, the tool the client need to support this is ther= e.=20 > There wont be any updated RFC anytime soon, not to mention that the RFC i= n=20 > question isnt even a finalized protocol, its an experimental protocol so=20 > refering to it as a standard can be argued. Well they all follow the rfc right? else we wouldn't be able to connect to it, right? and, All this is is extensions to the rfc. =20 > Anyways, just a tired rant. I still have my AmIRC 3.0 key, although i was= =20 > driven away from AmIRC due to the lack of support for even outputting mod= e=20 > changes sent from the server properly, making it impossible to see when u= sers=20 > where given halfop status for example. AmIRC was made according to the rfc, some changes has been added by the authors during the years but they have always been minor. > Flames may be directed to /dev/null, the world isnt black and white.. and= the=20 > RFC some people hold to be the bible isnt being followed by a single majo= r=20 > IRC network apart from the most basic client <-> server protocol. yes, and the rfc COVERS the basic client <-> server protocol, Everything esle is extensions, right? //Ian Kumlien ___________________________________________________________________ AmIRC Mailing List - http://www.vapor.com/amirc/ AmIRC FAQ......: http://faq.vapor.com/amirc/ Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
