home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!ira.uka.de!uka!uka!news
- From: S_TITZ@iravcl.ira.uka.de (Olaf Titz)
- Newsgroups: alt.irc
- Subject: RTF[M,S] - Re: Top 50 Killers (12/7/92-19/7/92)
- Date: 24 Jul 1992 09:44:28 GMT
- Organization: Fachschaft Informatik, Uni Karlsruhe
- Lines: 32
- Distribution: world
- Message-ID: <14ojdsINNpjk@iraul1.ira.uka.de>
- References: <CKD.92Jul21121951@loiosh.eff.org> <1992Jul22.063803.19673@alf.uib.no> <CKD.92Jul22110054@loiosh.eff.org> <1992Jul23.181920.17926@constellation.ecn.uoknor.edu> <avalon.711947810@sorokin>
- NNTP-Posting-Host: irav1.ira.uka.de
- X-News-Reader: VMS NEWS 1.23
- In-Reply-To: avalon@sorokin.anu.edu.au's message of 24 Jul 92 03:16:50 GMT
-
- In <avalon.711947810@sorokin> avalon@sorokin.anu.edu.au writes:
-
- > Since the manual is rather brief, RTFS.
- > Thats how to learn the inner details of the IRC programs.
- > The reast of the knowledge on routing, etc, comes from being
- > 'net-aware' (having maps of networks, knowing where you are
- > in relation to everyone else, what is good/fast, what is slow/bad,
- > etc).
- >
- > Both take time.
- >
- > avalon
-
- All that is true (exists a *manual*?), but I can tell that life for
- client-coders (in this case) could be much easier if there were
- - a reasonably small, consistent IRC protocol and
- - *documentation* on this (not just comments in sources about
- 'hopefully having grasped all messages')
-
- I have heard that some folks are developing version 3 of irc, being
- incompatible with 2.7. Please, at least *consider* writing an RFC
- about it!
-
- MfG,
- Olaf
- --
- o
- Olaf Titz \ s_titz@iravcl.ira.uka.de \ _/\
- \ uknf@dkauni2.bitnet \ _//|_.
- y.a. comp.sc.student \ +49-721-60439@voice \ (_)`(_)
- Uni Karlsruhe, Germany \ praetoriu@irc \~~~~~~~~~~~~~
- He thinks too much, such men are dangerous. - Shakespeare, Caesar
-