From b947e089ea1ffb2bad5537314628a11912d91a70 Mon Sep 17 00:00:00 2001 From: Steve Youngs Date: Sun, 12 Jun 2016 20:28:35 +1000 Subject: [PATCH] Remove old and crusty zenirc pkg Signed-off-by: Steve Youngs --- package-compile.el | 3 - xemacs-packages/Makefile | 2 +- xemacs-packages/zenirc/BUGS | 49 - xemacs-packages/zenirc/COPYING | 339 -- xemacs-packages/zenirc/ChangeLog | 102 - xemacs-packages/zenirc/INSTALL | 21 - xemacs-packages/zenirc/Makefile | 54 - xemacs-packages/zenirc/Makefile.in | 209 - xemacs-packages/zenirc/NEWS | 304 -- xemacs-packages/zenirc/README | 34 - xemacs-packages/zenirc/TODO | 148 - xemacs-packages/zenirc/configure | 648 --- xemacs-packages/zenirc/configure.in | 5 - xemacs-packages/zenirc/doc/666.conspiracy | 70 - xemacs-packages/zenirc/doc/FAQ | 1994 --------- xemacs-packages/zenirc/doc/README-OLD | 192 - xemacs-packages/zenirc/doc/RFC1459 | 3643 ----------------- xemacs-packages/zenirc/doc/ctcp.doc | 917 ----- xemacs-packages/zenirc/doc/irc-operators | 177 - xemacs-packages/zenirc/doc/server-list | 251 -- xemacs-packages/zenirc/doc/tao-of-irc | 271 -- xemacs-packages/zenirc/doc/tour.of.irc | 441 -- xemacs-packages/zenirc/doc/undernet | 785 ---- xemacs-packages/zenirc/doc/zenirc.ascii | 420 -- xemacs-packages/zenirc/doc/zenirc.texi | 676 --- xemacs-packages/zenirc/install-sh | 238 -- xemacs-packages/zenirc/mkinstalldirs | 32 - xemacs-packages/zenirc/package-info.in | 19 - xemacs-packages/zenirc/src/ChangeLog | 2368 ----------- xemacs-packages/zenirc/src/zenirc-18.el | 160 - xemacs-packages/zenirc/src/zenirc-8ball.el | 55 - xemacs-packages/zenirc/src/zenirc-away.el | 74 - xemacs-packages/zenirc/src/zenirc-bork.el | 211 - xemacs-packages/zenirc/src/zenirc-color.el | 190 - .../zenirc/src/zenirc-command-queue.el | 105 - xemacs-packages/zenirc/src/zenirc-complete.el | 451 -- .../zenirc/src/zenirc-ctcp-flood.el | 41 - xemacs-packages/zenirc/src/zenirc-dcc.el | 524 --- xemacs-packages/zenirc/src/zenirc-doto.el | 221 - xemacs-packages/zenirc/src/zenirc-eval.el | 65 - xemacs-packages/zenirc/src/zenirc-example.el | 276 -- xemacs-packages/zenirc/src/zenirc-fill.el | 332 -- xemacs-packages/zenirc/src/zenirc-finnish.el | 214 - xemacs-packages/zenirc/src/zenirc-format.el | 95 - xemacs-packages/zenirc/src/zenirc-fortran.el | 301 -- xemacs-packages/zenirc/src/zenirc-french.el | 179 - xemacs-packages/zenirc/src/zenirc-history.el | 102 - xemacs-packages/zenirc/src/zenirc-ignore.el | 159 - xemacs-packages/zenirc/src/zenirc-iwantop.el | 98 - xemacs-packages/zenirc/src/zenirc-klingon.el | 261 -- xemacs-packages/zenirc/src/zenirc-latin.el | 197 - xemacs-packages/zenirc/src/zenirc-make.el | 31 - xemacs-packages/zenirc/src/zenirc-meditate.el | 56 - xemacs-packages/zenirc/src/zenirc-netsplit.el | 151 - xemacs-packages/zenirc/src/zenirc-notify.el | 188 - xemacs-packages/zenirc/src/zenirc-oink.el | 54 - xemacs-packages/zenirc/src/zenirc-ojnk.el | 55 - xemacs-packages/zenirc/src/zenirc-pjg.el | 50 - xemacs-packages/zenirc/src/zenirc-popup.el | 293 -- xemacs-packages/zenirc/src/zenirc-prime-p.el | 102 - .../zenirc/src/zenirc-random-away.el | 53 - .../zenirc/src/zenirc-random-nick.el | 103 - xemacs-packages/zenirc/src/zenirc-signal.el | 52 - xemacs-packages/zenirc/src/zenirc-stamp.el | 58 - xemacs-packages/zenirc/src/zenirc-swedish.el | 229 -- xemacs-packages/zenirc/src/zenirc-trigger.el | 276 -- .../zenirc/src/zenirc-yow-filter.el | 90 - xemacs-packages/zenirc/src/zenirc-yow.el | 65 - xemacs-packages/zenirc/src/zenirc.el | 3403 --------------- 69 files changed, 1 insertion(+), 24031 deletions(-) delete mode 100644 xemacs-packages/zenirc/BUGS delete mode 100644 xemacs-packages/zenirc/COPYING delete mode 100644 xemacs-packages/zenirc/ChangeLog delete mode 100644 xemacs-packages/zenirc/INSTALL delete mode 100644 xemacs-packages/zenirc/Makefile delete mode 100644 xemacs-packages/zenirc/Makefile.in delete mode 100644 xemacs-packages/zenirc/NEWS delete mode 100644 xemacs-packages/zenirc/README delete mode 100644 xemacs-packages/zenirc/TODO delete mode 100755 xemacs-packages/zenirc/configure delete mode 100644 xemacs-packages/zenirc/configure.in delete mode 100644 xemacs-packages/zenirc/doc/666.conspiracy delete mode 100644 xemacs-packages/zenirc/doc/FAQ delete mode 100644 xemacs-packages/zenirc/doc/README-OLD delete mode 100644 xemacs-packages/zenirc/doc/RFC1459 delete mode 100644 xemacs-packages/zenirc/doc/ctcp.doc delete mode 100644 xemacs-packages/zenirc/doc/irc-operators delete mode 100644 xemacs-packages/zenirc/doc/server-list delete mode 100644 xemacs-packages/zenirc/doc/tao-of-irc delete mode 100644 xemacs-packages/zenirc/doc/tour.of.irc delete mode 100644 xemacs-packages/zenirc/doc/undernet delete mode 100644 xemacs-packages/zenirc/doc/zenirc.ascii delete mode 100644 xemacs-packages/zenirc/doc/zenirc.texi delete mode 100755 xemacs-packages/zenirc/install-sh delete mode 100755 xemacs-packages/zenirc/mkinstalldirs delete mode 100644 xemacs-packages/zenirc/package-info.in delete mode 100644 xemacs-packages/zenirc/src/ChangeLog delete mode 100644 xemacs-packages/zenirc/src/zenirc-18.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-8ball.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-away.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-bork.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-color.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-command-queue.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-complete.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-ctcp-flood.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-dcc.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-doto.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-eval.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-example.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-fill.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-finnish.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-format.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-fortran.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-french.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-history.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-ignore.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-iwantop.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-klingon.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-latin.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-make.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-meditate.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-netsplit.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-notify.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-oink.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-ojnk.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-pjg.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-popup.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-prime-p.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-random-away.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-random-nick.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-signal.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-stamp.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-swedish.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-trigger.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-yow-filter.el delete mode 100644 xemacs-packages/zenirc/src/zenirc-yow.el delete mode 100644 xemacs-packages/zenirc/src/zenirc.el diff --git a/package-compile.el b/package-compile.el index d32ede0b..c16c3bfb 100644 --- a/package-compile.el +++ b/package-compile.el @@ -203,7 +203,6 @@ ("xslide" . "xemacs-packages") ("xslt-process" . "xemacs-packages") ("xwem" . "xemacs-packages") - ("zenirc" . "xemacs-packages") ;; mule-packages ("edict" . "mule-packages") ("egg-its" . "mule-packages") @@ -245,8 +244,6 @@ (list (expand-file-name "lisp" (file-name-as-directory dir)))) ((equal package "mew") (list (expand-file-name "mew" (file-name-as-directory dir)))) - ((equal package "zenirc") - (list (expand-file-name "src" (file-name-as-directory dir)))) ((equal package "semantic") (list dir (expand-file-name "bovine" (file-name-as-directory dir)) diff --git a/xemacs-packages/Makefile b/xemacs-packages/Makefile index da1e9fc1..40880b7f 100644 --- a/xemacs-packages/Makefile +++ b/xemacs-packages/Makefile @@ -57,7 +57,7 @@ PACKAGES := xemacs-base fsf-compat mail-lib \ sieve slider sml-mode sounds-au sounds-wav strokes \ supercite textools time tm tpu tramp \ vc vhdl view-process viper vm w3 x-symbol \ - xslide xslt-process xwem zenirc + xslide xslt-process xwem else PACKAGES := $(NONMULE_PACKAGES) endif diff --git a/xemacs-packages/zenirc/BUGS b/xemacs-packages/zenirc/BUGS deleted file mode 100644 index 4b1ccb96..00000000 --- a/xemacs-packages/zenirc/BUGS +++ /dev/null @@ -1,49 +0,0 @@ -ZenIRC BUGS list -- Last updated 1996-04-25 - -* The server parsing code does strange things when it gets lots of - action at the same time. - - Noah Friedman's comments to this 'bug'; - - No, it's probably because the process filter isn't reentrant, and it - wasn't intended to be. (It uses a global vector to reduce memory - consumption). I've never observed that behavior, and I don't know - how it can happen---the only time the server parser can be called - recursively is if you are in the debugger or you send back a - response through a process that has a pty. But that's only - significant it is gets run from a server hook, since only those get - called from within the process filter. - - You could fix that at the expense of considerably greater consing. - -* ISON is limited to 512 characters, make sure ZenIRC groks that. - -* ZenIRC doesn't parse the following numerics at all, some of them aren't - used by either 2.8 nor 2.9. Some other ugly servers use other numerics - for other stuff as well. - - 416 ERR_TOOMANYMATCHES, "%s %s :Output too long (try locally)", - 434 ERR_SERVICENAMEINUSE, (char *)NULL, - 435 ERR_SERVICECONFUSED, (char *)NULL, - 438 ERR_QUOTAEXCEEDED, "%s :Quota exceeded, try again later.", - 466 ERR_YOUWILLBEBANNED, (char *)NULL, - 476 ERR_BADCHANMASK, "%s :Bad Channel Mask", - 484 ERR_RESTRICTED, ":Your connection is restricted!", - 492 ERR_NOSERVICEHOST, (char *)NULL, - 304 RPL_TEXT, (char *)NULL, - 316 RPL_WHOISCHANOP, (char *)NULL, - 361 RPL_KILLDONE, (char *)NULL, - 362 RPL_CLOSING, "%s :Closed. Status = %d", - 363 RPL_CLOSEEND, "%d: Connections Closed", - 373 RPL_INFOSTART, ":Server INFO", - 383 RPL_YOURESERVICE, (char *)NULL, - 384 RPL_MYPORTIS, "%d :Port to local server is\r\n", - 385 RPL_NOTOPERANYMORE, (char *)NULL, - 207 RPL_TRACESERVICE, "Service %d %s", - 231 RPL_SERVICEINFO, (char *)NULL, - 232 RPL_ENDOFSERVICES, (char *)NULL, - 233 RPL_SERVICE, (char *)NULL, - 234 RPL_SERVLIST, "%s %s %s %d %d :%s", - 235 RPL_SERVLISTEND, "%s %d :End of service listing", - 245 RPL_STATSSLINE, "%c %s * %s %d %d", - 246 RPL_STATSPING, "%s %d %d %d %d", diff --git a/xemacs-packages/zenirc/COPYING b/xemacs-packages/zenirc/COPYING deleted file mode 100644 index e77696ae..00000000 --- a/xemacs-packages/zenirc/COPYING +++ /dev/null @@ -1,339 +0,0 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 - - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 675 Mass Ave, Cambridge, MA 02139, USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - The precise terms and conditions for copying, distribution and -modification follow. - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. - -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - - 2. You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any change. - - b) You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. - - c) If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. - -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: - - a) Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, - - b) Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, - - c) Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) - -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. - - 4. You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. - - 5. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. - - 6. Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. - - 7. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. - -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 8. If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. - - 9. The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. - - 10. If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. - - NO WARRANTY - - 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. - - 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) 19yy - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. - -Also add information on how to contact you by electronic and paper mail. - -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - - Gnomovision version 69, Copyright (C) 19yy name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. - - , 1 April 1989 - Ty Coon, President of Vice - -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. diff --git a/xemacs-packages/zenirc/ChangeLog b/xemacs-packages/zenirc/ChangeLog deleted file mode 100644 index c313970c..00000000 --- a/xemacs-packages/zenirc/ChangeLog +++ /dev/null @@ -1,102 +0,0 @@ -2014-05-15 Norbert Koch - - * Makefile (VERSION): XEmacs package 1.18 released. - -2014-05-15 Norbert Koch - - * Makefile (VERSION): XEmacs package 1.17 released. - -2014-05-13 Jerry James - - * .cvsignore: Remove. - * doc/.cvsignore: Remove. - * src/.cvsignore: Remove. - * .hgignore: New file. - * src/zenirc-klingon.el: Restore CVS keyword expansions. - * src/zenirc-yow-filter.el: Ditto. - * configure.in: Ditto. - * doc/zenirc.texi: Update for texinfo 5.x. - -2005-05-10 Norbert Koch - - * Makefile (VERSION): XEmacs package 1.16 released. - -2004-01-20 Norbert Koch - - * Makefile (VERSION): XEmacs package 1.15 released. - -2004-01-15 Jerry James - - * Makefile (PRELOADS): Define x-color-defined-p to something harmless. - -2003-10-31 Norbert Koch - - * Makefile (VERSION): XEmacs package 1.14 released. - -2003-03-30 Steve Youngs - - * Makefile (EARLY_GENERATED_LISP): Revert previous change. - -2003-03-22 Steve Youngs - - * Makefile (EARLY_GENERATED_LISP): Explicitly set so we don't try - to build custom-loads, this package doesn't have any. - -2003-03-09 Ben Wing - - * Makefile (GENERATED): Removed. - Delete explicit compile:: and binkit: rules. - Use EXPLICIT_DOCS instead of explicitly giving the targets - and dependencies. - Move the include of XEmacs.rules to the end of the file. - Remove MAKEINFO_FLAGS for directory, not needed. - -2002-11-29 Ben Wing - - * .cvsignore: Remove files now handled automatically by CVS. - * Makefile: Use `compile' instead of hard-coded `all'. - -2002-10-15 Ville Skyttä - - * Makefile (srckit): Remove. - -2002-10-14 Ville Skyttä - - * Makefile (MANUAL): Removed (unused). - -2002-07-15 Adrian Aichner - - * doc/zenirc.ascii: It's XEmacs, not Xemacs. - -2002-01-07 Adrian Aichner - - * Makefile (HTML_FILES): New. - * Makefile (HTML_DEP): New. - -2002-01-02 Steve Youngs - - * package-info.in (provides): Update to include all provides. - -2001-12-30 Adrian Aichner - - * doc/zenirc.texi: Add missing direntry. - -2001-06-16 Simon Josefsson - - * zenirc.el (zenirc-font-lock-keywords): Some font-lock defaults. - (toplevel): Put font-lock-defaults on mode. - (zenirc-mode): Allow font-lock initialization. - -2000-10-05 Martin Buchholz - - * *: Mega typo fix. - -2000-08-22 Steve Youngs - - * Makefile: Remove target 'clean' because it's covered in XEmacs.rules. - -1998-08-15 SL Baur - - * Initial integration with XEmacs 21. - * Makefile: New file. - diff --git a/xemacs-packages/zenirc/INSTALL b/xemacs-packages/zenirc/INSTALL deleted file mode 100644 index 9abf7fd3..00000000 --- a/xemacs-packages/zenirc/INSTALL +++ /dev/null @@ -1,21 +0,0 @@ -1) Run `./configure' in the same directory as this file. - -2) Check Makefile in the same directory as this file to make sure it - says what you want. - -3) Run `make install' in the same directory as this file. - -4) If you don't install ZenIRC in the system directories you need to add - an entry to your "load-path", preferably in your ~/.emacs file; - - (setq load-path (cons - (expand-file-name "/full/path/to/zenirc/directory") - load-path)) - -5) Read src/zenirc-example.el for instructions on how to set up ZenIRC - for daily abuse. - -To try it out--run `emacs', M-x load-library zenirc, M-x zenirc, Waste Time. -If this doesn't work, e-mail your problems to `zenirc-bug@splode.com'. - -Per Persson 1996-04-26. \ No newline at end of file diff --git a/xemacs-packages/zenirc/Makefile b/xemacs-packages/zenirc/Makefile deleted file mode 100644 index 699cedc7..00000000 --- a/xemacs-packages/zenirc/Makefile +++ /dev/null @@ -1,54 +0,0 @@ -# Makefile for zenirc lisp code - -# This file is part of XEmacs. - -# XEmacs is free software; you can redistribute it and/or modify it -# under the terms of the GNU General Public License as published by the -# Free Software Foundation; either version 2, or (at your option) any -# later version. - -# XEmacs is distributed in the hope that it will be useful, but WITHOUT -# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or -# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License -# for more details. - -# You should have received a copy of the GNU General Public License -# along with XEmacs; see the file COPYING. If not, write to -# the Free Software Foundation, Inc., 59 Temple Place - Suite 330, -# Boston, MA 02111-1307, USA. - -VERSION = 1.18 -AUTHOR_VERSION = 2.112 -MAINTAINER = XEmacs Development Team -PACKAGE = zenirc -PKG_TYPE = regular -REQUIRES = zenirc -CATEGORY = standard - -ELCS = src/zenirc-18.elc src/zenirc-8ball.elc src/zenirc-away.elc \ - src/zenirc-bork.elc src/zenirc-color.elc src/zenirc-command-queue.elc \ - src/zenirc-complete.elc src/zenirc-ctcp-flood.elc src/zenirc-dcc.elc \ - src/zenirc-doto.elc src/zenirc-eval.elc src/zenirc-example.elc \ - src/zenirc-fill.elc src/zenirc-finnish.elc src/zenirc-format.elc \ - src/zenirc-fortran.elc src/zenirc-french.elc src/zenirc-history.elc \ - src/zenirc-ignore.elc src/zenirc-iwantop.elc src/zenirc-klingon.elc \ - src/zenirc-latin.elc src/zenirc-make.elc src/zenirc-meditate.elc \ - src/zenirc-netsplit.elc src/zenirc-notify.elc src/zenirc-oink.elc \ - src/zenirc-ojnk.elc src/zenirc-pjg.elc src/zenirc-popup.elc \ - src/zenirc-prime-p.elc src/zenirc-random-away.elc \ - src/zenirc-random-nick.elc src/zenirc-signal.elc src/zenirc-stamp.elc \ - src/zenirc-swedish.elc src/zenirc-trigger.elc \ - src/zenirc-yow-filter.elc src/zenirc-yow.elc src/zenirc.elc - -EXTRA_SOURCES = BUGS INSTALL NEWS README TODO - -EXPLICIT_DOCS = doc/$(PACKAGE).texi - -DATA_FILES = $(wildcard doc/[6FRcistu]*) -DATA_DEST = $(PACKAGE) - -PRELOADS = -eval "(defalias 'x-color-defined-p 'ignore)" - -AUTOLOAD_PATH = src - -include ../../XEmacs.rules diff --git a/xemacs-packages/zenirc/Makefile.in b/xemacs-packages/zenirc/Makefile.in deleted file mode 100644 index 9b8d6d81..00000000 --- a/xemacs-packages/zenirc/Makefile.in +++ /dev/null @@ -1,209 +0,0 @@ -# Makefile.in for ZenIRC. -*- makefile -*- - -# Copyright (C) 1994, 1995 Noah S. Friedman -# Copyright (C) 1994, 1995, 1996 Per Persson - -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2, or (at your option) -# any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. - -#### Start of system configuration section. #### - -srcdir = @srcdir@ -VPATH = $(srcdir) - -INSTALL = @INSTALL@ -INSTALL_PROGRAM = @INSTALL_PROGRAM@ -INSTALL_DATA = @INSTALL_DATA@ - -prefix = @prefix@ -exec_prefix = @exec_prefix@ - -# The directory for object files and libraries of object code. Do -# not install executables here; they belong in `libexecdir' instead. -libdir = $(exec_prefix)/lib - -# The directory for installing the Info files for this package. -infodir = $(prefix)/info - -elispdir = $(libdir)/emacs/site-lisp - -AUTOCONF = autoconf -EMACS = emacs -ETAGS = etags -MAKEINFO = makeinfo -MAKEINFOFLAGS = --no-split -I. -I$(srcdir) -BATCHFLAGS = -batch -q -no-site-file -MV = mv -RM = rm -f -CP = cp -TAR = tar -TEXI2DVI = texi2dvi -TEXI2DVIFLAGS = #-I. -I$(srcdir) - -#### End of system configuration section. #### - -SHELL = /bin/sh - -DISTFILES = BUGS TODO COPYING NEWS INSTALL README \ - Makefile.in configure configure.in install-sh mkinstalldirs - -DOCFILES = FAQ RFC1459 irc-operators tao-of-irc zenirc.ascii \ - README-OLD ctcp.doc server-list tour.of.irc zenirc.info \ - zenirc.texi undernet 666.conspiracy - -SRCFILES = $(ELFILES) ChangeLog zenirc-make.el - -ELFILES = zenirc-18.el zenirc-away.el zenirc-bork.el zenirc-command-queue.el \ - zenirc-complete.el zenirc-ctcp-flood.el zenirc-dcc.el \ - zenirc-doto.el zenirc-example.el zenirc-fill.el zenirc-finnish.el \ - zenirc-format.el zenirc-fortran.el zenirc-french.el \ - zenirc-ignore.el zenirc-iwantop.el zenirc-klingon.el \ - zenirc-latin.el zenirc-meditate.el zenirc-netsplit.el \ - zenirc-notify.el zenirc-oink.el zenirc-ojnk.el zenirc-pjg.el \ - zenirc-popup.el zenirc-random-away.el zenirc-random-nick.el \ - zenirc-signal.el zenirc-stamp.el zenirc-swedish.el zenirc-yow.el \ - zenirc-history.el zenirc-color.el zenirc-8ball.el zenirc-trigger.el \ - zenirc-yow-filter.el zenirc.el zenirc-prime-p.el zenirc-eval.el - -MFLAGS = ELFILES='$(ELFILES)' \ - AUTOCONF='$(AUTOCONF)' EMACS='$(EMACS)' ETAGS='$(ETAGS)' \ - MAKEINFO='$(MAKEINFO)' MAKEINFOFLAGS='$(MAKEINFOFLAGS)' \ - MV='$(MV)' RM='$(RM)' CP='$(CP)' TAR='$(TAR)' \ - TEXI2DVI='$(TEXI2DVI)' TEXI2DVIFLAGS='$(TEXI2DVIFLAGS)' \ - INSTALL='$(INSTALL)' INSTALL_DATA='$(INSTALL_DATA)' \ - INSTALL_PROGRAM='$(INSTALL_PROGRAM)' SHELL='$(SHELL)' \ - elispdir='$(elispdir)' exec_prefix='$(exec_prefix)' \ - infodir='$(infodir)' libdir='$(libdir)' prefix='$(prefix)' - -.SUFFIXES: .texi .info -.texi.info: - $(MAKEINFO) $(MAKEINFOFLAGS) $< - -.SUFFIXES: .texi .dvi -.texi.dvi: - $(TEXI2DVI) $(TEXI2DVIFLAGS) $< - -all: all-zenirc -all-info: info - -### targets required by GNU Coding standards ### - -Makefile: Makefile.in config.status - $(SHELL) ./config.status - -config.status: configure - $(SHELL) ./config.status --recheck - -configure: configure.in - cd $(srcdir) && $(AUTOCONF) - -TAGS: - cd $(srcdir)/src && $(ETAGS) *.el - -.PHONY: clean mostlyclean distclean -clean: - $(RM) src/*.elc - -mostlyclean: clean - -distclean: clean - $(RM) Makefile config.status config.log config.cache src/TAGS src/*~ *~ - -.PHONY: maintainer-clean maintclean-warning -maintainer-clean: maintclean-warning distclean - -# Used by maintainer-clean to print a warning before any rm commands are run. -maintclean-warning: - @echo "This command is intended for maintainers to use;" - @echo "it deletes files that may require special tools to rebuild." - -realclean: distclean - $(RM) src/TAGS - -.PHONY: dist -dist: - echo zenirc-`sed -e '/^(defconst zenirc-version/!d' \ - -e 's/[^0-9.]*\([0-9.]*\).*/\1/' \ - -e q src/zenirc.el` > .fname - $(RM) -r `cat .fname` - dst=`cat .fname`; umask 000 && mkdir $$dst $$dst/doc $$dst/src - dst=`cat .fname`; for f in $(DISTFILES); do \ - ln $$f $$dst/$$f \ - || { echo copying $$f; cp -p $$f $$dst/$$f ; } \ - done - dst=`cat .fname`/doc; for f in $(DOCFILES); do \ - ln doc/$$f $$dst/$$f \ - || { echo copying doc/$$f; cp -p doc/$$f $$dst/$$f ; } \ - done - dst=`cat .fname`/src; for f in $(SRCFILES); do \ - ln src/$$f $$dst/$$f \ - || { echo copying src/$$f; cp -p src/$$f $$dst/$$f ; } \ - done - $(TAR) --gzip -chvf `cat .fname`.tar.gz `cat .fname` - $(RM) -r `cat .fname` .fname - -# Tar up the development sources -.PHONY: devtar -devtar: - echo zenirc-dev-`sed -e '/^(defconst zenirc-version/!d' \ - -e 's/[^0-9.]*\([0-9.]*\).*/\1/' \ - -e q src/zenirc.el` > .fname - $(RM) -r ../`cat .fname` - umask 000 && mkdir ../`cat .fname` - @echo Copying tree to ../`cat .fname` - $(TAR) -cf - . | (cd ../`cat .fname` && $(TAR) xpvf -) - @echo Making tar file `cat .fname` - dst=`cat .fname`; cd .. && $(TAR) --gzip -chvf $$dst.tar.gz $$dst - dst=`cat .fname`; cd .. && $(RM) -r $$dst - mv ../`cat .fname`.tar.gz . - -.PHONY: installdirs uninstall -install: all installdirs - -cd ./src && $(CP) *.elc $(elispdir) - # -cd ./doc && $(CP) zenirc.info* $(infodir) - -installdirs: force - -$(SHELL) $(srcdir)/mkinstalldirs $(elispdir) #$(infodir) - -uninstall: force - -cd $(elispdir) && { $(RM) $(ELFILES); - for f in $(ELFILES); do $(RM) $${f}c; done; } - -cd $(infodir) && $(RM) zenirc.info* - -.PHONY: check installcheck force -check: - @echo 'Nothing to be done for "check"' - -installcheck: - @echo 'Nothing to be done for "installcheck"' - -force: - -### program-specific building targets ### - -all-zenirc: elisp #info -elisp: - -cd ./src && $(EMACS) $(BATCHFLAGS) -l zenirc-make.el \ - -f batch-byte-compile $(ELFILES) - -info: zenirc.info -zenirc.info: zenirc.texi - -dvi: zenirc.dvi -zenirc.dvi: zenirc.texi - -# Prevent GNU make v3 from overflowing arg limit on SysV. -.NOEXPORT: - -# Makefile.in ends here diff --git a/xemacs-packages/zenirc/NEWS b/xemacs-packages/zenirc/NEWS deleted file mode 100644 index 49f012c2..00000000 --- a/xemacs-packages/zenirc/NEWS +++ /dev/null @@ -1,304 +0,0 @@ -User-visible changes in ZenIRC-2.112: - -* Removed new-lines from all the different language catalouge - entries. zenirc-messages adds this if appropriate. - -* zenirc-prime.el, new script. Calculates prime numbers. - -* zenirc-eval.el, new script. Evaluate special commands being sent to - you from other people on IRC. USE WITH CAUTION! - -* zenirc-history.el now binds M-p and M-n to previous- and next-line. - -* zenirc-yow-filter.el, new script. Filter out all the annoying - automated yows. - -* zenirc-color.el, new script; colorize your ZenIRC. Should work with - Emacs-19, Emacs-20 and XEmacs. - -* zenirc-8ball.el, new script. Ask 8-ball easy yes/no questions. - -* zenirc-trigger.el, new script. Easy creation of triggers to incoming - messages. - -* zenirc-ignore.el is more vocal to the user, also added - zenirc-ignore-last-privmsg on C-c C-i to ignore the user@host of the - last seen PRIVMSG. - - It's also much brighter when it comes to regexp handling. - -* zenirc-notify.el, better handling of upper and lower case - nicknames. Much better command parser when adding and removing - victims in real time. - -* zenirc-random-nick.el, added code do automatically change nickname - every x number of seconds. - -* zenirc-fill.el, rerwritten to look more like the 2.100 - version. Two new ways of filling are added: - zenirc-wrap-region-dynamic and -wrap-region-static. Added functions - to fill outgoing messages as well as incoming ones. The filling - functions now also uses the correct width of the *right* buffer. - -* zenirc-example.el, a lot of new examples. - -* All special modes can now be turned on and off with zenirc-*-mode. - -* zenirc-signal functions are smarter; doesn't beep when it shouldn't - anymore. - -* zenirc-select uses zenirc-server-alist in a much smarter way. - -* zenirc-format-privmsg-or-notice now reckons PRIVMSG's to user@server - in a better way. - -* Better handling of nick!user@host table in zenirc-format.el. - -* zenirc-bug, new function. - -* zenirc-update-modeline, a function which updates the modeline - depending on which version of Emacs you are using. Relevant functions - in ZenIRC now uses this. - -* zenirc-channel-list, a list of currently joined channels. If you - leave your zenirc-current-victim it gets set to the previous channel. - C-c C-t toggles between all the channels with zenirc-toggle-channel. - -* Added a couple of ircII lookalikes: - - zenirc-always-show-channelname, new variable. If set to nil, strip - out the channelnames from incoming PRIVMSGs and NOTICEs if the - channelname is the same as the current-victim. - - zenirc-delete-preceding-whitespaces, newvariable. If set to t, strip - off leading whitespaces on outgoing messages. - - zenirc-whowas-on-401, new variable. If set to t, ZenIRC will issue a - WHOWAS command if no information is gained by a WHOIS command. - -* More additions to conform with ircd2.9 news. - -As of 1996-04-24, Per has taken over primary maintenance of ZenIRC. - -User-visible changes in ZenIRC 2.101: - -* New function, gnus-bug. Initialize mail to make it easier for user - to report a newly found bug. - -* Comments on how to do automatic things while initializing a server - connection in zenirc-example.el. - -* Takes care of more new irc2.9 NUMERICS. - -* Responds to CTCP ECHO queries. - -As of 1995-06-28, Per started adding patches to ZenIRC alpha versions. - -* All the notify code is stripped out of zenirc.el into a -notify.el - script. The notify code is able to check user@host info on - notificated persons. Most of the code is also totally rewritten, - some of the features are much better sanity checking. - -* /server, a new command using zenirc-select, lets you connect to - servers in an easy way. /server irc-2.mit.edu 6667 ben - The command uses zenirc-server-alist, it also defaults to just about - every setting you can think of. - -* zenirc-ignore.el gives you ircII like /ignore and /unignore, an easier - way to maintain your zenirc-ignore-list in real time. If you use the - commands with regexps, it doesn't do it the ircII way. - -* /resize command in zenirc-fill.el lets you resize the fill values if - you change the size of your emacsen. - - There also a new way of filling things, based on the first word of the - string. - -* The variable zenirc-command-char lets you decide which char you want - to use as a command char. "/" is default and you can change it with - /commandchar. - -* zenirc-klingon.el and zenirc-bork.el are two new sets of language - catalogs. - -* /topic is now able to SHOW the topic as well as set it. - -* The Makefile is now able to make and install ZenIRC, it uses - zenirc-make.el to do so. Needs some improvment though. - -* zenirc-iwantop.el has better documentation for new users. - -* ZenIRC is able to display confirmation messages in the echo area - instead of in the process buffer, at least better than it did before. - -* ZenIRC shows idletime in hours:minutes:seconds instead of plain - seconds. - -* zenirc-history.el gives you shell-like C-p and C-n on C-cC-p and - C-cC-n. - -* ZenIRC groks most of the 2.9 news, as well as some ugly additions to - 2.8 by digital and comstud. FOLLOW THE RFC OR DIE. - -* There's code in zenirc.el to let you timestamp PRIVMSG/NOTICE, the - code makes it really easy to add timestamps for other thingies. - -* Some of the numeric replies parsing are changed to show relevant - information. 2.9 changes some of the replies so ZenIRC has to do - more sanity checking (this is not totally perfect yet). - -* New funny files in the doc directory. - - -As of 1994-10-02, Noah has taken over primary maintenance of zenirc. - -User-visible changes in ZenIRC 2.100: - -* ZenIRC now configures and installs using an Autoconf-generated configure - script. [Makefile is only 4/5 finished 1995-03-27] - -* The version number no longer directly corresponds with the RCS revision - number of zenirc.el. A separate version number is used, which will only - change in each release. As a result, releases won't have arbitrarily - incremented version numbers. - -* The new file zenirc-fill.el provides a minor mode which formats privmsgs, - notices, and whatever kinds of messages you specify, so that they don't - exceed the width of your window. Selective control is provided since - some tables produced by the server will look terrible if anything - attempts to fold them. - -* It is now possible to load multiple language catalogs and switch between - them using "/language" or `M-x zenirc-lang-set-current-language'. - -* The DCC interface has been largely rewritten. - It uses the message catalogs and has more hooks. - Another notable change is the fact that subsequent DCC chat requests from - the same user are stored and previous requests are discarded. - This is in case the port number or IP address have changed in the new - request. - -* All the external message catalogs have been renamed by removing the - `-mode' in their name. For example, zenirc-latin-mode.el is now - zenirc-latin.el. They are updated to use the new catalog mechanism. - -* Almost all tables are now implemented as hash tables instead of - linear lists. This should speed up searches. - -* Line input has been completely reimplemented. It's now safe to send very - long lines in private messages and notices; if necessary they are broken - into multiple chunks and sent separately. - - Also, it's easier to send text line-at-a-time by yanking text into the - buffer, moving point to the beginning of the new input, and hitting - return successively. No excess newlines are inserted any more, and point - is automatically positioned on the next line of unsent input. - - You can have confirmation of sending go in the echo area instead of - inserting lines in the buffer. - -* /kick, /kill, /notice, /privmsg, and /squit commands are now sent to the - server in the proper format. - -* zenirc-popup is now a minor mode that can be enabled or disabled with the - `zenirc-popup-mode' command. It should also work in emacs 18 now. - -* The method of display for matching completions can be controlled by the - user via the variable `zenirc-complete-display-function'. The default is - to display completions in the echo area if they will fit. Otherwise, use - a portion of the zenirc window. - - The variable `zenirc-complete-add-final-space-p' controls whether a - trailing space is added to unique completions. The default is to do so - since this is consistent with completion in emacs and other GNU programs. - -* You can now use `;' and `:' to send a private message to the last person - you sent a private message to, or who sent you a private message. These - keys only have this special meaning if they are the first character of - your input. - - The other commands which do this used to be bound on `C-c s' and `C-c r'. - They are now on `C-c C-s' and `C-c C-r', since the former keys are - reserved for the user's private use. These commands always insert the - recipient's name at the beginning of your input, rather than wherever - point happens to be. - -* The mechanism for specifying how to connect to servers is completely - revamped. The variable `zenirc-server-alist' is used to specify a list - of servers (with optional port/password/nick info). Each one is tried in - turn until a successful connection is made. It is initialized from your - IRCSERVER environment variable, which can have the same format as parsed - by ircII. - - You can set the variables `zenirc-server-default', `zenirc-nick-default', - `zenirc-port-default', etc. Or if these are unset, the appropriate - environment variables are used. - -* By default, any message with more than 4 CTCP queries is ignored. - This is to avoid being disconnected for flooding. - To disable this check, remove the appropriate regexp from - zenirc-ignorance-list. - -* A new hook, zenirc-message-hook, is called each time a message is - inserted in the buffer. The hook zenirc-send-line-hook is called each - time you send a line of text. - -* If a command hook is nil, the command is just sent directly to the server, - like /quote. To keep a command from going to the server at all, put the - `ignore' function on the appropriate hook. - -* The new script zenirc-iwantop.el allows you to accept ctcp queries from - users and give them channel operator privileges automatically. - -* zenirc-fancy-away.el has been renamed to zenirc-away.el. - zenirc-fancy-format.el has been renamed to zenirc-format.el. - zenirc-fancy-signal.el has been renamed to zenirc-signal.el. - -* Too many bug fixes and other minor improvments to mention here. - See the ChangeLog for details. - - -Changes to ZenIRC in version 2.16: - -* Added /oper command. - - -Changes to ZenIRC in version 2.15: - -* New scripts: zenirc-popup.el, zenirc-fancy-away.el, and zenirc-yow.el - The first pops up a window when signals occur and there is presently no - window displaying that buffer. - The second insures that you see a user's away message only once, until - they change it again. - The last implements the command /yow, and also allows you to - autoreply to victims with zippy quotes. - -* zenirc-complete.el has been completely rewritten. - The new version is better at insidiously caching data, doesn't tamper - with the kill-ring, and has fewer bugs. - -* Made most files, including zenirc.el, "provide" themselves. - Also made any scripts which refer to symbols declared in zenirc.el - require it. - - This means that in emacs 19, you can use M-x unload-feature to easily - undo most of the effects of loading a package, except for top-level - forms. - -* zenirc has a new hook, zenirc-mode-hook, that is called at the end of - zenirc-mode. - -* Many bugs fixes in process filters to keep point and window display from - being munged incorrectly, to keep signal hooks from running when not - appropriate (and also so that other hooks can permanently modify the - state of buffers if desired). - -* Made signal hooks run last, after buffer update has already occured. - -* Removed recursion from some basic regexp matching routines. - -* Fixed bug in DCC chat code that was occasionally dropping bits of - incoming lines. - -* New script, zenirc-random-nick.el, can be used to randomly choose - nicknames for IRC if you are feeling deconstructionist. diff --git a/xemacs-packages/zenirc/README b/xemacs-packages/zenirc/README deleted file mode 100644 index 40963ce1..00000000 --- a/xemacs-packages/zenirc/README +++ /dev/null @@ -1,34 +0,0 @@ -ZenIRC-2.1 - Wed Apr 24 20:41:48 MET DST 1996 - Per Persson - -KNOWN BUGS: - -See the BUGS file. -For missing features, look in the TODO file. - - -KNOWN FEATURES AND INSTRUCTIONS: - -See the INSTALL file for help on how to compile and install ZenIRC. - -Look at zenirc-example.el for help on how to set up ZenIRC for daily -usage. If you want more information about ZenIRC internals, read -doc/README (beware, this file is out of date). In time ZenIRC will -come with a texinfo manual. - -Found a new bug? Report it with "zenirc-bug" and we'll fix it! - - -FURTHER INSTRUCTIONS: - -The most current versions of ZenIRC can always be found at; - - ftp://ftp.splode.com:/pub/zenirc - -There are three email addresses for ZenIRC you might be interested in; - - zenirc@splode.com (List for annoucments and important mails.) - send mail to zenirc-request@splode.com to subscribe. - zenirc-dev@splode.com (List for ZenIRC developers.) - send mail to zenirc-dev-request@splode.com to subscribe. - zenirc-bug@splode.com (List for bug reports.) - this list is not interesting for you, unless you find a bug. diff --git a/xemacs-packages/zenirc/TODO b/xemacs-packages/zenirc/TODO deleted file mode 100644 index 6966d79c..00000000 --- a/xemacs-packages/zenirc/TODO +++ /dev/null @@ -1,148 +0,0 @@ -ZenIRC TODO list -- Last updated 1998-05-07 - -* zenirc.el - - Strip ^F, ^P, ^U, ^B and ^_ from receieved PRIVMSG, NOTICE and - TOPIC. Possibly add functions for this in zenirc.color.el at a later - stage. - -* zenirc-fill.el - - Add optional function to strip off whitespaces at the end of messages. - -* Show Y-class when using /trace command. - -* Define current-time for emacs 18. - Define current-time-string in 18 so that it can format arbitrary time values. - -* /ping - - Instead of trying to send to hack current-time-string, or represent big - integers and such, just send the printed representation of a call to - current-time. Then when the reply comes back, read the result and - compare the conses. The way to compute the difference of these times is - - (defsubst time-difference (a b) - (+ (lsh (- (car b) (car a)) 16) - (- (car (cdr b)) (car (cdr a))))) - - This returns the number of seconds elapsed. - - I would like to remove the kiwi-derived routines anyway. - -* zenirc-notify.el - - Make it not trigger if you see the person leave or join a channel. - -* zenirc-complete.el - - Make it add nicks seen based on zenirc-complete-add-list, would be - nice to add things on /trace and /userhost. - -* Allow messages from specific users, or different types of messages, to go - into different buffers. - - If a general mechanism is implemented for this, zenirc-dcc.el should use - it. - - It is likely that zenirc-message will have take a new arg, indicating - into which buffer the message should go. - - [1995-03-16 Noah is working on this as part of a general purpose library - for emacs.] - - [1996-07-22 Jason (and Per) is working on another solution to this.] - -* Implement "filters", to distinguish semantics from hooks. - - Some things, like the zenirc-format-nickuserhost-hook, don't really want - to run all the functions; it wants to terminate as soon as a desirable - formatting is completed. - - There are other instances where two hooks do not necessarily want to be - run independently. For instance, zenirc-away.el only wants to display an - away message if the current away message for a user is not in its cache - already. - - But in general, hooks want to be run independently of each other since - they may perform some completely orthogonal action, so if some other hook - wants to abort running the rest of the hook list, the user is screwed. - - I propose a "filter" mechanism which provides a way to specify ordering, - i.e. they should be able to say "I need to be run before foo but after - bar" (and this requirement also assumes that bar must necessarily be run - after foo). Packages which use this new mechamism may have to know some - details about other packages for this to work, but that's a given. These - filters would be of a different nature from the hooks now being used. - - I do not have a specific interface in mind yet, but I suspect that - filters will generally be run via the hook mechanism, i.e. one will - generally do - - (zenirc-add-hook 'zenirc-foo-hook - (function - (lambda (&rest args) - (apply 'zenirc-run-filter 'zenirc-foo-filter args)))) - -* Update non-english message catalogs with new strings added to the client - since it they were first created. - -* Write a texinfo manual. - -* Make 'undo' only apply to unsent text. - -* Make recieved text 'read-only'. - - -Low priority: - -* /list with regexp's. - -* Finish zenirc-eval.el. - - This should operate as a CTCP message that reads a sexp and evaluates it. - In addition to regular eval, there should be an eval-print or some other - macro that takes the result and sends it in the CTCP reply. Since irc - messages are limited to 255 chars or so, the syntactic sugar would be - helpful. - - For the sake of security weenies, it should have an access list, probably - a list of regexps of user@host addresses which are allowed to send - messages. - - Perhaps there should also be a "novice" flag which displays the form to - be evaluated in the minibuffer (or a display buffer) and query for - confirmation before doing anything. - -* Write zenirc-alias.el - - ircII like alias but not as smart. - -* Write zenirc-save.el - This should save some default values to a special zenirc.rc file - which ZenIRC loads during startup. - -* Write zenirc-eliza.el - - This should implement an eliza bot via doctor.el. - -* Write zenirc-swedish-chef.el - - This should be a process filter that converts everything people say into - swedish-chef speak, and it should have an abbrev table that dynamically - converts user input as well. - -* Write zenirc-face.el - - This should be code for Emacs 19 and XEmacs to support highlighting - for ^Vregions^V and the like. - -* Write zenirc-mcelwane.el - - Upcase words RANDOMLY on INPUT! - -* zenirc supporting bold controls - - From: Andrew J Cosgriff - any chance of zenirc supporting bold controls and stuff (^B et al.) ? - diff --git a/xemacs-packages/zenirc/configure b/xemacs-packages/zenirc/configure deleted file mode 100755 index 32a82f65..00000000 --- a/xemacs-packages/zenirc/configure +++ /dev/null @@ -1,648 +0,0 @@ -#!/bin/sh - -# Guess values for system-dependent variables and create Makefiles. -# Generated automatically using autoconf version 2.1 -# Copyright (C) 1992, 1993, 1994 Free Software Foundation, Inc. -# -# This configure script is free software; the Free Software Foundation -# gives unlimited permission to copy, distribute and modify it. - -# Defaults: -ac_help= -ac_default_prefix=/usr/local -# Any additions from configure.in: - -# Initialize some variables set by options. -# The variables have the same names as the options, with -# dashes changed to underlines. -build=NONE -cache_file=./config.cache -exec_prefix=NONE -host=NONE -no_create= -nonopt=NONE -no_recursion= -prefix=NONE -program_prefix=NONE -program_suffix=NONE -program_transform_name=s,x,x, -silent= -site= -srcdir= -target=NONE -verbose= -x_includes=NONE -x_libraries=NONE - -# Initialize some other variables. -subdirs= - -ac_prev= -for ac_option -do - - # If the previous option needs an argument, assign it. - if test -n "$ac_prev"; then - eval "$ac_prev=\$ac_option" - ac_prev= - continue - fi - - case "$ac_option" in - -*=*) ac_optarg=`echo "$ac_option" | sed 's/[-_a-zA-Z0-9]*=//'` ;; - *) ac_optarg= ;; - esac - - # Accept the important Cygnus configure options, so we can diagnose typos. - - case "$ac_option" in - - -build | --build | --buil | --bui | --bu | --b) - ac_prev=build ;; - -build=* | --build=* | --buil=* | --bui=* | --bu=* | --b=*) - build="$ac_optarg" ;; - - -cache-file | --cache-file | --cache-fil | --cache-fi \ - | --cache-f | --cache- | --cache | --cach | --cac | --ca | --c) - ac_prev=cache_file ;; - -cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \ - | --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*) - cache_file="$ac_optarg" ;; - - -disable-* | --disable-*) - ac_feature=`echo $ac_option|sed -e 's/-*disable-//'` - # Reject names that are not valid shell variable names. - if test -n "`echo $ac_feature| sed 's/[-a-zA-Z0-9_]//g'`"; then - { echo "configure: error: $ac_feature: invalid feature name" 1>&2; exit 1; } - fi - ac_feature=`echo $ac_feature| sed 's/-/_/g'` - eval "enable_${ac_feature}=no" ;; - - -enable-* | --enable-*) - ac_feature=`echo $ac_option|sed -e 's/-*enable-//' -e 's/=.*//'` - # Reject names that are not valid shell variable names. - if test -n "`echo $ac_feature| sed 's/[-_a-zA-Z0-9]//g'`"; then - { echo "configure: error: $ac_feature: invalid feature name" 1>&2; exit 1; } - fi - ac_feature=`echo $ac_feature| sed 's/-/_/g'` - case "$ac_option" in - *=*) ;; - *) ac_optarg=yes ;; - esac - eval "enable_${ac_feature}='$ac_optarg'" ;; - - -exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \ - | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \ - | --exec | --exe | --ex) - ac_prev=exec_prefix ;; - -exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \ - | --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \ - | --exec=* | --exe=* | --ex=*) - exec_prefix="$ac_optarg" ;; - - -gas | --gas | --ga | --g) - # Obsolete; use --with-gas. - with_gas=yes ;; - - -help | --help | --hel | --he) - # Omit some internal or obsolete options to make the list less imposing. - # This message is too long to be a string in the A/UX 3.1 sh. - cat << EOF -Usage: configure [options] [host] -Options: [defaults in brackets after descriptions] -Configuration: - --cache-file=FILE cache test results in FILE - --help print this message - --no-create do not create output files - --quiet, --silent do not print \`checking...' messages - --version print the version of autoconf that created configure -Directory and file names: - --prefix=PREFIX install architecture-independent files in PREFIX - [$ac_default_prefix] - --exec-prefix=PREFIX install architecture-dependent files in PREFIX - [same as prefix] - --srcdir=DIR find the sources in DIR [configure dir or ..] - --program-prefix=PREFIX prepend PREFIX to installed program names - --program-suffix=SUFFIX append SUFFIX to installed program names - --program-transform-name=PROGRAM run sed PROGRAM on installed program names -Host type: - --build=BUILD configure for building on BUILD [BUILD=HOST] - --host=HOST configure for HOST [guessed] - --target=TARGET configure for TARGET [TARGET=HOST] -Features and packages: - --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) - --enable-FEATURE[=ARG] include FEATURE [ARG=yes] - --with-PACKAGE[=ARG] use PACKAGE [ARG=yes] - --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) - --x-includes=DIR X include files are in DIR - --x-libraries=DIR X library files are in DIR ---enable and --with options recognized:$ac_help -EOF - exit 0 ;; - - -host | --host | --hos | --ho) - ac_prev=host ;; - -host=* | --host=* | --hos=* | --ho=*) - host="$ac_optarg" ;; - - -nfp | --nfp | --nf) - # Obsolete; use --without-fp. - with_fp=no ;; - - -no-create | --no-create | --no-creat | --no-crea | --no-cre \ - | --no-cr | --no-c) - no_create=yes ;; - - -no-recursion | --no-recursion | --no-recursio | --no-recursi \ - | --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r) - no_recursion=yes ;; - - -prefix | --prefix | --prefi | --pref | --pre | --pr | --p) - ac_prev=prefix ;; - -prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*) - prefix="$ac_optarg" ;; - - -program-prefix | --program-prefix | --program-prefi | --program-pref \ - | --program-pre | --program-pr | --program-p) - ac_prev=program_prefix ;; - -program-prefix=* | --program-prefix=* | --program-prefi=* \ - | --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*) - program_prefix="$ac_optarg" ;; - - -program-suffix | --program-suffix | --program-suffi | --program-suff \ - | --program-suf | --program-su | --program-s) - ac_prev=program_suffix ;; - -program-suffix=* | --program-suffix=* | --program-suffi=* \ - | --program-suff=* | --program-suf=* | --program-su=* | --program-s=*) - program_suffix="$ac_optarg" ;; - - -program-transform-name | --program-transform-name \ - | --program-transform-nam | --program-transform-na \ - | --program-transform-n | --program-transform- \ - | --program-transform | --program-transfor \ - | --program-transfo | --program-transf \ - | --program-trans | --program-tran \ - | --progr-tra | --program-tr | --program-t) - ac_prev=program_transform_name ;; - -program-transform-name=* | --program-transform-name=* \ - | --program-transform-nam=* | --program-transform-na=* \ - | --program-transform-n=* | --program-transform-=* \ - | --program-transform=* | --program-transfor=* \ - | --program-transfo=* | --program-transf=* \ - | --program-trans=* | --program-tran=* \ - | --progr-tra=* | --program-tr=* | --program-t=*) - program_transform_name="$ac_optarg" ;; - - -q | -quiet | --quiet | --quie | --qui | --qu | --q \ - | -silent | --silent | --silen | --sile | --sil) - silent=yes ;; - - -site | --site | --sit) - ac_prev=site ;; - -site=* | --site=* | --sit=*) - site="$ac_optarg" ;; - - -srcdir | --srcdir | --srcdi | --srcd | --src | --sr) - ac_prev=srcdir ;; - -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*) - srcdir="$ac_optarg" ;; - - -target | --target | --targe | --targ | --tar | --ta | --t) - ac_prev=target ;; - -target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*) - target="$ac_optarg" ;; - - -v | -verbose | --verbose | --verbos | --verbo | --verb) - verbose=yes ;; - - -version | --version | --versio | --versi | --vers) - echo "configure generated by autoconf version 2.1" - exit 0 ;; - - -with-* | --with-*) - ac_package=`echo $ac_option|sed -e 's/-*with-//' -e 's/=.*//'` - # Reject names that are not valid shell variable names. - if test -n "`echo $ac_package| sed 's/[-_a-zA-Z0-9]//g'`"; then - { echo "configure: error: $ac_package: invalid package name" 1>&2; exit 1; } - fi - ac_package=`echo $ac_package| sed 's/-/_/g'` - case "$ac_option" in - *=*) ;; - *) ac_optarg=yes ;; - esac - eval "with_${ac_package}='$ac_optarg'" ;; - - -without-* | --without-*) - ac_package=`echo $ac_option|sed -e 's/-*without-//'` - # Reject names that are not valid shell variable names. - if test -n "`echo $ac_package| sed 's/[-a-zA-Z0-9_]//g'`"; then - { echo "configure: error: $ac_package: invalid package name" 1>&2; exit 1; } - fi - ac_package=`echo $ac_package| sed 's/-/_/g'` - eval "with_${ac_package}=no" ;; - - --x) - # Obsolete; use --with-x. - with_x=yes ;; - - -x-includes | --x-includes | --x-include | --x-includ | --x-inclu \ - | --x-incl | --x-inc | --x-in | --x-i) - ac_prev=x_includes ;; - -x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \ - | --x-incl=* | --x-inc=* | --x-in=* | --x-i=*) - x_includes="$ac_optarg" ;; - - -x-libraries | --x-libraries | --x-librarie | --x-librari \ - | --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l) - ac_prev=x_libraries ;; - -x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \ - | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*) - x_libraries="$ac_optarg" ;; - - -*) { echo "configure: error: $ac_option: invalid option; use --help to show usage" 1>&2; exit 1; } - ;; - - *) - if test -n "`echo $ac_option| sed 's/[-a-z0-9.]//g'`"; then - echo "configure: warning: $ac_option: invalid host type" 1>&2 - fi - if test "x$nonopt" != xNONE; then - { echo "configure: error: can only configure for one host and one target at a time" 1>&2; exit 1; } - fi - nonopt="$ac_option" - ;; - - esac -done - -if test -n "$ac_prev"; then - { echo "configure: error: missing argument to --`echo $ac_prev | sed 's/_/-/g'`" 1>&2; exit 1; } -fi - -trap 'rm -fr conftest* confdefs* core $ac_clean_files; exit 1' 1 2 15 - -# File descriptor usage: -# 0 unused; standard input -# 1 file creation -# 2 errors and warnings -# 3 unused; some systems may open it to /dev/tty -# 4 checking for... messages and results -# 5 compiler messages saved in config.log -if test "$silent" = yes; then - exec 4>/dev/null -else - exec 4>&1 -fi -exec 5>./config.log - -echo "\ -This file contains any messages produced by compilers while -running configure, to aid debugging if configure makes a mistake. -" 1>&5 - -# Strip out --no-create and --no-recursion so they do not pile up. -# Also quote any args containing shell metacharacters. -ac_configure_args= -for ac_arg -do - case "$ac_arg" in - -no-create | --no-create | --no-creat | --no-crea | --no-cre \ - | --no-cr | --no-c) ;; - -no-recursion | --no-recursion | --no-recursio | --no-recursi \ - | --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r) ;; - *" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?]*) - ac_configure_args="$ac_configure_args '$ac_arg'" ;; - *) ac_configure_args="$ac_configure_args $ac_arg" ;; - esac -done - -# NLS nuisances. -# Only set LANG and LC_ALL to C if already set. -# These must not be set unconditionally because not all systems understand -# e.g. LANG=C (notably SCO). -if test "${LC_ALL+set}" = set; then LC_ALL=C; export LC_ALL; fi -if test "${LANG+set}" = set; then LANG=C; export LANG; fi - -# confdefs.h avoids OS command line length limits that DEFS can exceed. -rm -rf conftest* confdefs.h -# AIX cpp loses on an empty file, so make sure it contains at least a newline. -echo > confdefs.h - -# A filename unique to this package, relative to the directory that -# configure is in, which we can look for to find out if srcdir is correct. -ac_unique_file=Makefile.in - -# Find the source files, if location was not specified. -if test -z "$srcdir"; then - ac_srcdir_defaulted=yes - # Try the directory containing this script, then its parent. - ac_prog=$0 - ac_confdir=`echo $ac_prog|sed 's%/[^/][^/]*$%%'` - test "x$ac_confdir" = "x$ac_prog" && ac_confdir=. - srcdir=$ac_confdir - if test ! -r $srcdir/$ac_unique_file; then - srcdir=.. - fi -else - ac_srcdir_defaulted=no -fi -if test ! -r $srcdir/$ac_unique_file; then - if test "$ac_srcdir_defaulted" = yes; then - { echo "configure: error: can not find sources in $ac_confdir or .." 1>&2; exit 1; } - else - { echo "configure: error: can not find sources in $srcdir" 1>&2; exit 1; } - fi -fi -srcdir=`echo "${srcdir}" | sed 's%\([^/]\)/*$%\1%'` - -# Prefer explicitly selected file to automatically selected ones. -if test -z "$CONFIG_SITE"; then - if test "x$prefix" != xNONE; then - CONFIG_SITE="$prefix/share/config.site $prefix/etc/config.site" - else - CONFIG_SITE="$ac_default_prefix/share/config.site $ac_default_prefix/etc/config.site" - fi -fi -for ac_site_file in $CONFIG_SITE; do - if test -r "$ac_site_file"; then - echo "loading site script $ac_site_file" - . "$ac_site_file" - fi -done - -if test -r "$cache_file"; then - echo "loading cache $cache_file" - . $cache_file -else - echo "creating cache $cache_file" - > $cache_file -fi - -ac_ext=c -# CFLAGS is not in ac_cpp because -g, -O, etc. are not valid cpp options. -ac_cpp='$CPP $CPPFLAGS' -ac_compile='${CC-cc} $CFLAGS $CPPFLAGS conftest.$ac_ext -c 1>&5 2>&5' -ac_link='${CC-cc} $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext -o conftest $LIBS 1>&5 2>&5' - -if (echo "testing\c"; echo 1,2,3) | grep c >/dev/null; then - # Stardent Vistra SVR4 grep lacks -e, says ghazi@caip.rutgers.edu. - if (echo -n testing; echo 1,2,3) | sed s/-n/xn/ | grep xn >/dev/null; then - ac_n= ac_c=' -' ac_t=' ' - else - ac_n=-n ac_c= ac_t= - fi -else - ac_n= ac_c='\c' ac_t= -fi - - -ac_aux_dir= -for ac_dir in $srcdir $srcdir/.. $srcdir/../..; do - if test -f $ac_dir/install-sh; then - ac_aux_dir=$ac_dir - ac_install_sh="$ac_aux_dir/install-sh -c" - break - elif test -f $ac_dir/install.sh; then - ac_aux_dir=$ac_dir - ac_install_sh="$ac_aux_dir/install.sh -c" - break - fi -done -if test -z "$ac_aux_dir"; then - { echo "configure: error: can not find install-sh or install.sh in $srcdir $srcdir/.. $srcdir/../.." 1>&2; exit 1; } -fi -ac_config_guess=$ac_aux_dir/config.guess -ac_config_sub=$ac_aux_dir/config.sub -ac_configure=$ac_aux_dir/configure # This should be Cygnus configure. - -# Find a good install program. We prefer a C program (faster), -# so one script is as good as another. But avoid the broken or -# incompatible versions: -# SysV /etc/install, /usr/sbin/install -# SunOS /usr/etc/install -# IRIX /sbin/install -# AIX /bin/install -# AFS /usr/afsws/bin/install, which mishandles nonexistent args -# SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" -# ./install, which can be erroneously created by make from ./install.sh. -echo $ac_n "checking for a BSD compatible install""... $ac_c" 1>&4 -if test -z "$INSTALL"; then -if eval "test \"`echo '${'ac_cv_path_install'+set}'`\" = set"; then - echo $ac_n "(cached) $ac_c" 1>&4 -else - IFS="${IFS= }"; ac_save_ifs="$IFS"; IFS="${IFS}:" - for ac_dir in $PATH; do - case "$ac_dir" in - ''|.|/etc|/usr/sbin|/usr/etc|/sbin|/usr/afsws/bin|/usr/ucb) ;; - *) - # OSF1 and SCO ODT 3.0 have their own names for install. - for ac_prog in ginstall installbsd scoinst install; do - if test -f $ac_dir/$ac_prog; then - if test $ac_prog = install && - grep dspmsg $ac_dir/$ac_prog >/dev/null 2>&1; then - # AIX install. It has an incompatible calling convention. - # OSF/1 installbsd also uses dspmsg, but is usable. - : - else - ac_cv_path_install="$ac_dir/$ac_prog -c" - break 2 - fi - fi - done - ;; - esac - done - IFS="$ac_save_ifs" - # As a last resort, use the slow shell script. - test -z "$ac_cv_path_install" && ac_cv_path_install="$ac_install_sh" -fi - INSTALL="$ac_cv_path_install" -fi -echo "$ac_t""$INSTALL" 1>&4 - -# Use test -z because SunOS4 sh mishandles braces in ${var-val}. -# It thinks the first close brace ends the variable substitution. -test -z "$INSTALL_PROGRAM" && INSTALL_PROGRAM='${INSTALL}' - -test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644' - -trap '' 1 2 15 -if test -w $cache_file; then -echo "updating cache $cache_file" -cat > $cache_file <<\EOF -# This file is a shell script that caches the results of configure -# tests run on this system so they can be shared between configure -# scripts and configure runs. It is not useful on other systems. -# If it contains results you don't want to keep, you may remove or edit it. -# -# By default, configure uses ./config.cache as the cache file, -# creating it if it does not exist already. You can give configure -# the --cache-file=FILE option to use a different cache file; that is -# what configure does when it calls configure scripts in -# subdirectories, so they share the cache. -# Giving --cache-file=/dev/null disables caching, for debugging configure. -# config.status only pays attention to the cache file if you give it the -# --recheck option to rerun configure. -# -EOF -# Ultrix sh set writes to stderr and can't be redirected directly. -(set) 2>&1 | - sed -n "s/^\([a-zA-Z0-9_]*_cv_[a-zA-Z0-9_]*\)=\(.*\)/: \${\1='\2'}/p" \ - >> $cache_file -else -echo "not updating unwritable cache $cache_file" -fi - -trap 'rm -fr conftest* confdefs* core $ac_clean_files; exit 1' 1 2 15 - -test "x$prefix" = xNONE && prefix=$ac_default_prefix -# Let make expand exec_prefix. -test "x$exec_prefix" = xNONE && exec_prefix='${prefix}' - -# Any assignment to VPATH causes Sun make to only execute -# the first set of double-colon rules, so remove it if not needed. -# If there is a colon in the path, we need to keep it. -if test "x$srcdir" = x.; then - ac_vpsub='/^[ ]*VPATH[ ]*=[^:]*$/d' -fi - -trap 'rm -f $CONFIG_STATUS conftest*; exit 1' 1 2 15 - -# Transform confdefs.h into DEFS. -# Protect against shell expansion while executing Makefile rules. -# Protect against Makefile macro expansion. -cat > conftest.defs <<\EOF -s%#define \([A-Za-z_][A-Za-z0-9_]*\) \(.*\)%-D\1=\2%g -s%[ `~#$^&*(){}\\|;'"<>?]%\\&%g -s%\[%\\&%g -s%\]%\\&%g -s%\$%$$%g -EOF -DEFS=`sed -f conftest.defs confdefs.h | tr '\012' ' '` -rm -f conftest.defs - - -# Without the "./", some shells look in PATH for config.status. -: ${CONFIG_STATUS=./config.status} - -echo creating $CONFIG_STATUS -rm -f $CONFIG_STATUS -cat > $CONFIG_STATUS </dev/null | sed 1q`: -# -# $0 $ac_configure_args -# -# Compiler output produced by configure, useful for debugging -# configure, is in ./config.log if it exists. - -ac_cs_usage="Usage: $CONFIG_STATUS [--recheck] [--version] [--help]" -for ac_option -do - case "\$ac_option" in - -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r) - echo "running \${CONFIG_SHELL-/bin/sh} $0 $ac_configure_args --no-create --no-recursion" - exec \${CONFIG_SHELL-/bin/sh} $0 $ac_configure_args --no-create --no-recursion ;; - -version | --version | --versio | --versi | --vers | --ver | --ve | --v) - echo "$CONFIG_STATUS generated by autoconf version 2.1" - exit 0 ;; - -help | --help | --hel | --he | --h) - echo "\$ac_cs_usage"; exit 0 ;; - *) echo "\$ac_cs_usage"; exit 1 ;; - esac -done - -ac_given_srcdir=$srcdir -ac_given_INSTALL="$INSTALL" - -trap 'rm -f Makefile; exit 1' 1 2 15 - -# Protect against being on the right side of a sed subst in config.status. -sed 's/%@/@@/; s/@%/@@/; s/%g$/@g/; /@g$/s/[\\\\&%]/\\\\&/g; - s/@@/%@/; s/@@/@%/; s/@g$/%g/' > conftest.subs <<\CEOF -$ac_vpsub -$extrasub -s%@CFLAGS@%$CFLAGS%g -s%@CPPFLAGS@%$CPPFLAGS%g -s%@CXXFLAGS@%$CXXFLAGS%g -s%@DEFS@%$DEFS%g -s%@LDFLAGS@%$LDFLAGS%g -s%@LIBS@%$LIBS%g -s%@exec_prefix@%$exec_prefix%g -s%@prefix@%$prefix%g -s%@program_transform_name@%$program_transform_name%g -s%@INSTALL_PROGRAM@%$INSTALL_PROGRAM%g -s%@INSTALL_DATA@%$INSTALL_DATA%g - -CEOF -EOF -cat >> $CONFIG_STATUS <> $CONFIG_STATUS <<\EOF -for ac_file in .. $CONFIG_FILES; do if test "x$ac_file" != x..; then - # Support "outfile[:infile]", defaulting infile="outfile.in". - case "$ac_file" in - *:*) ac_file_in=`echo "$ac_file"|sed 's%.*:%%'` - ac_file=`echo "$ac_file"|sed 's%:.*%%'` ;; - *) ac_file_in="${ac_file}.in" ;; - esac - - # Adjust relative srcdir, etc. for subdirectories. - - # Remove last slash and all that follows it. Not all systems have dirname. - ac_dir=`echo $ac_file|sed 's%/[^/][^/]*$%%'` - if test "$ac_dir" != "$ac_file" && test "$ac_dir" != .; then - # The file is in a subdirectory. - test ! -d "$ac_dir" && mkdir "$ac_dir" - ac_dir_suffix="/$ac_dir" - # A "../" for each directory in $ac_dir_suffix. - ac_dots=`echo $ac_dir_suffix|sed 's%/[^/]*%../%g'` - else - ac_dir_suffix= ac_dots= - fi - - case "$ac_given_srcdir" in - .) srcdir=. - if test -z "$ac_dots"; then top_srcdir=. - else top_srcdir=`echo $ac_dots|sed 's%/$%%'`; fi ;; - /*) srcdir="$ac_given_srcdir$ac_dir_suffix"; top_srcdir="$ac_given_srcdir" ;; - *) # Relative path. - srcdir="$ac_dots$ac_given_srcdir$ac_dir_suffix" - top_srcdir="$ac_dots$ac_given_srcdir" ;; - esac - - case "$ac_given_INSTALL" in - [/$]*) INSTALL="$ac_given_INSTALL" ;; - *) INSTALL="$ac_dots$ac_given_INSTALL" ;; - esac - echo creating "$ac_file" - rm -f "$ac_file" - configure_input="Generated automatically from `echo $ac_file_in|sed 's%.*/%%'` by configure." - case "$ac_file" in - *Makefile*) ac_comsub="1i\\ -# $configure_input" ;; - *) ac_comsub= ;; - esac - sed -e "$ac_comsub -s%@configure_input@%$configure_input%g -s%@srcdir@%$srcdir%g -s%@top_srcdir@%$top_srcdir%g -s%@INSTALL@%$INSTALL%g -" -f conftest.subs $ac_given_srcdir/$ac_file_in > $ac_file -fi; done -rm -f conftest.subs - - - -exit 0 -EOF -chmod +x $CONFIG_STATUS -rm -fr confdefs* $ac_clean_files -test "$no_create" = yes || ${CONFIG_SHELL-/bin/sh} $CONFIG_STATUS - diff --git a/xemacs-packages/zenirc/configure.in b/xemacs-packages/zenirc/configure.in deleted file mode 100644 index dcbba998..00000000 --- a/xemacs-packages/zenirc/configure.in +++ /dev/null @@ -1,5 +0,0 @@ -dnl Process this file with autoconf 2.x to produce a configure script. -dnl $Id: configure.in,v 1.1.1.1 1998-10-07 11:21:29 jareth Exp $ -AC_INIT(Makefile.in) -AC_PROG_INSTALL -AC_OUTPUT(Makefile) diff --git a/xemacs-packages/zenirc/doc/666.conspiracy b/xemacs-packages/zenirc/doc/666.conspiracy deleted file mode 100644 index 1b540734..00000000 --- a/xemacs-packages/zenirc/doc/666.conspiracy +++ /dev/null @@ -1,70 +0,0 @@ -------- Start of forwarded message ------- -From: Roger Espel Llima -Newsgroups: alt.humor.best-of-usenet - -Subject: Re: Irc 666 Conspiracy -From: nelson@cs.uwp.edu (Jeremy Nelson) -Newsgroups: alt.conspiracy, alt.irc, alt.conspiracy.antichrist, - alt.nostradamus, alt.prophecies - -<888@888.888> wrote: ->Do you have noticed that all ports of Irc servers begin with 666?? ->The most familiar is 6667 but also 6666,6668,6669. ->Maybe the internet is not so innocent as they want us to believe.. - -[Fade to black.... Fade into a darkly lit, yet distinctly reddish -place. A reddish-orange, horned man sits at a desk when the phone rings.] - -Bob: "Hello, Internet Porty Authority, wholly owned subsidiary of Hell, Inc., - this is Bob. How may I help you?" - -Steve: "Hi Bob! This is Steve down in research and development. We've just - develoepd this KILLER setup where people will waste literally thousands - of hours of their life doing nothing more than sitting quietly in front - of a terminal while their brains shrivel slowly into raisins." - -Bob: "Hrm... Sounds devilishly clever. What's the code name for it?" - -Steve: "Well, a beta-tester named Doug suggested "I Repeat Class". We liked - the way it formed an easy to grasp acronym, something that would - slowly make the poor users rue the day they ever heard it. But that - name seemed far to obvious about the side effects. We needed - something with more panache. After a joint meeting with the - Marketing Department, we came up with "Internet Relay Chat"." - -Bob: "Oh, thats absolutely perfect. What were the side effects that the - Punishment and Testing Department came up with?" - -Steve: "Initial Addiction rates were nearly 90%. If only we could get that - kind of response out of Cocaine or Heroin, we'd be set! Also listed - were a drastic reduction in eating habits, acute lack of sleep, loss - of intimacy with loved ones, and an *alarming* increase in the - purchase of keyboards. [1] Also noted was an increase in the - hostility level, with quite a few observances of users screaming - at their computer "ILL KILL THE GDMF THAT KICKED ME!" The most - frightening thing about it was that the testers told their friends - about the experience, and now their FRIENDS want to join the testing! - We cant shake people away with a stick! - -Bob: "Oh beautiful. This should set back the course of civilization a good - ten years. Do you have any idea how good its going to be for our - membership drive if this thing spreads like a viral infection? Within - ten years of when you deploy this, we'll have 250,000 people trying to - barge on all the time to get their fix!" - -Steve: "Oh, that reminds me of why i called. We need to get a port number - for the service so we can try some live testing out on the internet. - Can you spare us any?" - -Bob: "Can I? *cackle* Ive been saving a *very special* range of ports for - just something so evil as this. Something that isnt so blatantly - obvious, but just sublime enough that the really truly clued in will - be able to see the obvious conspiracy behind it. I can give you the - entire range of 6660-6669." - -Steve: "Oh, bonus! Ill get on it right away! Thanks again Bob!" - -Bob: "Any time. " "Oh.. i can see it now.. it will be GLORIOUS!" -------- End of forwarded message ------- - - diff --git a/xemacs-packages/zenirc/doc/FAQ b/xemacs-packages/zenirc/doc/FAQ deleted file mode 100644 index bf4636fa..00000000 --- a/xemacs-packages/zenirc/doc/FAQ +++ /dev/null @@ -1,1994 +0,0 @@ -mrg@mame.mu.oz.au & ben@gnu.ai.mit.edu - -This document answers the following frequently asked questions: - -1 what is irc ? -2 why does irc suck ? -3 why should i irc ? -4 what is netsex ? -5 should i have netsex ? -6 how do i get on irc ? -7 what is a channel operator ? -8 what is an irc operator ? -9 what is a major dweeb ? -10 what is a major fascist ? -11 what is a bot ? -12 what is the piglet way ? -13 what is a penis extension ? -14 how do i become of the piglet way ? -15 does linux suck ? -16 what is irc like ? - - -1 what is irc ? - -irc sucks. irc is reputed to stand for 'internet relay chat', -but it really means 'i repeat class'. though some people say -it means 'Irc Really suCks' [capitals only for emphasis]. - - -2 why does irc suck ? - -because piker and dl are irc operators. - - -3 why should i irc ? - -to be rude to irc operators, particularly dl and piker. - - -4 what is netsex ? - -netsex is a myth. a long time ago an irc operator called -wumpus (it rhymes with wimp, sorta) made up a story that -it wandered on to channel -69 to find people engaging in -what it called 'netsex', but this was never proven. since -then people have just been being rude to wumpus for being -so silly about this 'netsex' - - -5 should i have netsex ? - -d'oh! only stupid people who read this question if they -knew what netsex is (see number 4). - - -6 how do i get on irc ? - -take my advice - don't. - - -7 what is a channel operator ? - -a major fascist (see number 10). - - -8 what is an irc operator ? - -a major dweeb (see number 9). - - -9 what is a major dweeb ? - -an irc operator (see number 8). - - -10 what is a major fascist ? - -an channel operator (see number 7). - - -11 what is a bot ? - -a penis extension. only this penis extension doesn't impresss -the girlies (or the boys, if you/they are so inclinded [*]). - -[*] if you are sexually offended by this, then you lose. - - -12 what is the piglet way ? - -ojnk. - - -13 what is a penis extension ? - -a bot (see number 11). - - - -14 how do i become of the piglet way ? - -ojnk. - - -15 does linux suck ? - -yes. [*] - -[*] if you are sexually offended by this, then you lose. - - -16 what is irc like ? - -learn by example: - ----------------------------------------------------------------------- -Adam Pops My Cherry. - -A True Story of the IRC -by Ben Mesander -ben@hopper.acs.virginia.edu -(irc - piglet2) - -So one night, Leftist, and I (piglet2) on IRC decide to see what it's -like to be hot and willing IRC babes. Leftist becomes Julie, I become -Samantha, and we cruise the #hotsex channel, looking for a little -action. Julie plays smart, beautiful and passionate... I play dumb with -big tits (this is more natural for me). An interesting phenomenon arose -- while I originally was the one that attracted our target, Adam, he -soon liked Julie better than I. Brains over tits, I guess. In addition, -there is a little dialogue with catfish, a friend of ours who borrowed -my nick and wreaked havoc on several channels (she was through by the -time this log was started). I wish I had the presence of mind to log -the whole thing. Well I didn't. But to give the story so far, Adam has -revealed that he has slept with seven women, all of them "nearly -virgins." He's a college senior in Communications with a 2.0 gpa. Then -I insisted that he tell me a bedtime story. - -What follows is the logfile. Absolute stark naked reality on IRC. This -is Adam's story, the story of the average college student who's looking -for a net.fuck on irc. - - then up the top of your foot - to the inside of your left leg - OOH! - to the knee --> *catfish* it is so funny. - up to the thigh - still slowly and softly brushing inside -=> =Julie= she does? why? -=Julie= Dunno. - up above your glistening vagina - kissing across your abdomen -=Julie= *Adam* just remember, julie that I don't lie about this stuff. - and coming back down the other thigh's inside - then down the inside....down the foot... - to the toesies - kissing each and every one of them - down from the big one to the little baby -=Julie= Adam's got bad sentence structure. Let's make his life miserable. - then up the outside of your right leg... -=> =Julie= tell him you think kissing toes is gross. - over your knee -*Catfish* piggie, you better be saving some of this :) - to the hip - up your chest - to your breast - over it ever so gently -=Julie= No. That's in character for you, not me. -=> =Julie= or maybe that you have a club foot. -*** Action: Adam pauses for a breather... - whew! - up to the right side of your neck - then to your right earlobe - tugging at it with my teeth - mmmm! - then across your neck to your left one (my fave) - I like that! - then back around to the back of your neck - now, I place my hands firmly but gently on your shoulders - squeezing them a little - your arms are spread out above your head -=Julie= This guy is probably a 45 second-er. - (like you're doing jumping jacks) - mmmm. - and what is julie doing during all this?? - Masturbating, actually. - then I run my hands down the sides of your back GENTLY as I SLOWLY AND -+GENTLY go down your spine with my lips - ooh. I can feel myself stretched out! -=Julie= Hahaha, he likes me better. -=> =Julie= you slut. i bet you 10 net.bucks youre wrong. - then I go to your left "cheek" - and go down the back of your leg, outside -=Julie= *Adam* I have a DEEP voice. Very sexy voice I'm told. Women love -+it. - Squeal! - down to the foot -=Julie= He's offering to do it to me on the phone later. -=> =Julie= you win. he's not msging me. but I'm loggin this for planet -+yip. -=Julie= Tee-hee. - I'm excited. I'm gonna masturbate with my fingers now. - down the sole of your foot - to the little toesies - kissing every one of them -=> =Julie= have you ever anally masturbated? tee hee! Lemme find joN's -+phone number, kay? -=Julie= -> *adam* Yes. The kbord is getting sticky. -=Julie= No. K. -=> =Julie= (804)977-8802 - then back up to the inside of your leg...back of your knee (which you -+would probably kick at this point) - up to your ass - mmm. - cross over to the other side - then down the leg - to the back of the knee - to the sole of the foot - to the toesies -*** Adam is adam@rac3.wam.umd.edu (Adam L. Greenberg) -*** on channels: @#nights -*** on irc via server tjeeves.acc.Virginia.EDU (Jefferson Server, UVa) - kissing each one - then back up the outside of the leg... -=Julie= What should I do with joN's number? - hmm now where? -=> =Julie= this guy is a foot fetishist. - then back to the right ear -=> =Julie= say it is your number. -=Julie= Ok. - I lower myself onto you and pull a blanket over us to keep us warm - As I lie on top of you, nibbling your ear and massaging your shoulders, -+you feel me sticking into your lower back -=> =Julie= I feel like doing a dieter. "Suddenly, you have become -+tiresome." - Finally I cannot resist -=Julie= HE cannot resist! - You slowly spread your legs and I enter you from behind, lying on top -+of you, spreading your arms out and holding you down to the bed. - I like that! - ooh. I'm so wet! - You feel me sliding inside of you and you begin to moan -=Julie= 3.5 hrs till Calc. -*Adam* how do I know that? - Masturbate, sam, it works. --> *adam* know what? -*Adam* what? -=Julie= *Adam* I hope I'm making you happy :-) --> *adam* you asked me how i know that. -*Adam* how do I know you're really wet and not just saying that, samantha? -=Julie= -> *adam* HOPELESSLY - I go in and out and in and out. --> *adam* hmm. you'll have to trust me on this! this is a great bedtime story, -+you know I needed something like this. --> *adam* i can't wait to meet you! - We both get up on our knees and I grab your thighs and hold your sweet -+ass against the front of my legs - mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm - Julie's getting off! - As I slowly pump you, you get up on all fours... - I'd love to lick you julie! - oooooh if you only could - with adam too. friday? - Our bodies don't disconnect but my dick just goes in and out of you -+rhythmically. --> *catfish* I'm saving this to a logfile. - if (from "HailOtis@socspy.sci.fau.edu") then save /tmp/clc/priv/purps - then I reach around and play with your clit - mmmm... -=Julie= I have to piss. Bad. Cover for me. -*Catfish* bless you boy! -=> =Julie= tell im you have to go " finish" yourself. --> *adam* julie just told me she has to go "finish" herself! - Honey, you have to remember that I like making LOVE not fucking...so -+this is gonna be slow slow slow - I reach around, lower my chest onto your back as you still stay on all -+fours... - fingering your hot wet hole --> *catfish* he appears to have a thing for young girls, feet, and humping on -+all fours. - every time I touch your clit your hips buck and you feel the tension -+building --> *catfish* I guess pretty normal for an irc geek. - I'm buckin honey. -*Catfish* how I wish to see this! -=Julie= *Adam* yeah my hands are beginning to shake --> *catfish* hee hee. I'm catching about half of it in a logfile. -=Julie= I wonder why. - then I just ram you one time so smoothly that you scream in pleasure as -+you feel your pussy grabbing me tighter and tighter -=> =Julie= catfish sure acts interested in it! - pulsing around me - and it feels good. -=Julie= She wants you. -*Catfish* get as much as possible. - with that, I shoot very warmly inside you... -=> =Julie= 10 net.bucks sez she don't. -=Julie= I like how not only does he tell us what he does, he tells us what -+we do. - we have both worked (all worked) up a sweat - and lie down in the bed together - whew! - oh honey, I can't wait! - Julie, I'm gonna go fix your car! -=Julie= 10 net.bucks sez she likes computer people. -=> =Julie= puleez - i hate comptuer people. - ain't done yet! - Well hon, I am pretty done. -=Julie= Some people find us mystifying. - And I got to go to work tomorrow! - oh I hope not - More on friday, but for real? - first a little nap - then a shower - Don't worry adam, I just need to be rested up four our little party! - I don't have a phone right now, do you have julie's number? -*** Action: Adam gets a funny feeling he'll never hear from you guys -=Julie= -> *ADAM* WHEN? I WILL CALL WHENEVER! But i have to go to bed -+soon. - Friday? - I have no LD remember? - Friday night? - They won't put it on until....no friday is NO GOOD! - well, if u can call julie on a pay phone? Satruday? - Sam, I will call him. - julie can pick me up, in her car. - julie is at 804 977 8802 - My LD will be on soon...jeez, let's not rush this all! I'm a little -+nervous...besides. I - Sam I wanna lick your wetness. - julie i miss you *hugs* -=Julie= What do you think joN will think? -=> =Julie= I'll leave him email... - I'd rather wait until A) I have a haircut! and b) I can take you ladies -+out for at least a nice dinner! - I want to make a good first impression - ADAM, I don't care about dinner OR hair now! - But julie is a hairdresser! she can cut your hair! - I only care about feeling your hard cock inside of me. - I'm so hot tonight. -=Julie= You're "officially" calling me right after this. So I can avoid -+calling Adam. --> *catfish* oh lordie help me. - Well, we're gonna have to have quite a bit of foreplay first because I -+haven't had any in a long time so I'd probably come pretty quickly. But get -+me to come two or three times and after that I'll last quite a while, -+actually. -=> =Julie= just tell him you can't afford the ld right now either. - The last girl I made love to had to have me stop after about an hour -+she was in pain -=Julie= Too late, babe. - It takes me WAY longer than that. -=> =Julie= a precummer. - me too! - Not when you're with me it won't -=Julie= _adam? - remember you have to please two of us! - PROMISE? - and we can help eachi other out a little too... - My fingers can make you come in about 5...I'll guarantee it or double -+your fingering back! - ooh! I love that! - My voice plays a key role here, too - yum -=> =Julie= "my voice. gag" -=Julie= I'm so moist. This is all being logged? -=> =Julie= u bet. -=Julie= from where? - well goodnight! I have to go! -=> =Julie= on my amiga at home. - hey not so fast! - mmm, adma, can I give you a kiss? -=Julie= I mean, where did you start? Do selective editing and send it in. - oh honey you can give me whatever you want - *hugs* julie! - oh adam, we will have fun! but I have to work tomorrow! look at the tiem! - bye! - -I'd never had net.sex before. Adam devirginified another babe, and my -net.cherry is forever lost. I'm checking into the Betty Ford clinic. ----------------------------------------------------------------------- - -The following is a conversation between "good-guy" and "R" - R was the only -op on the channel, and databoy wanted to get rid of me... - --> *good-guy* did I op you? -*good-guy* no --> *good-guy* sorry. :( -*good-guy* type /mode #christian +o good-guy --> *good-guy* oh, I see. you type +o then your nick name? -*** good-guy has changed the topic on channel #christian to God love you -*** good-guy has changed the topic on channel #christian to GOD LOVE YOU -*good-guy* you got it -*good-guy* do you realize you the away on --> *good-guy* my screen is scrolling too fast. what was the command again? --> *good-guy* the away on? what does that mean? -*good-guy* can you op first then I will explain --> *good-guy* my screen is scrolling too fast. what was the command again? --> *piglet3* I think good-guy is beginning to catch on, just as I started a log. -*good-guy* type /mode #christian +o good-guy --> *good-guy* what's the last part for? -*good-guy* type /mode #christian +o good-guy --> *good-guy* what is the for? is that the date? -*good-guy* please op me before this get out of control --> *good-guy* I dont want to type anything if I dont know what it's for. -*** good-guy is H04LG@cunyvm.cuny.edu (!id ONE OF THE GOOD GUYS) -*good-guy* well are you going --> *good-guy* going? -*good-guy* to op me? -*** Signoff: good-guy (good-guy) --> *good-guy* not until you tell me what the last part of that command is for. --> *good-guy* I think I understand the rest. -*** good-guy (H04LG@cunyvm.cuny.edu) has joined channel #christian --> *good-guy* a friend told me never to type a computer command I didnt understand. -*good-guy* I see --> *good-guy* especially one involving the word passwd or rhosts. -*good-guy* okay now can you op me. --> *good-guy* what does that date in the command mean? -*good-guy* i understand. -*good-guy* it just shows the current date --> *good-guy* but why put it in the command to op someone???!! -*good-guy* you don't need it --> *good-guy* then why did you type it? -*good-guy* just try what I told you on me -*good-guy* just trying it out --> *good-guy* I dont understand. -*good-guy* bye bye --> *good-guy* goodbye -*good-guy* you do not want to op me --> *good-guy* I dont know why I should. you arent being very clear. -*** good-guy has left channel #christian -*good-guy* I have the irc primer --> *good-guy* what does that do? -*good-guy* I have all the commands for irc. -*good-guy* you should type /away --> *good-guy* what will that do? -*good-guy* it stop giving me that msg as a manager --> *good-guy* as a manager? -*** good-guy is away: go on talk to me -*good-guy* yes -*good-guy* you have not type away - ----------------------------------------------------------------------- -Random netsexer encounters phone: - -*ZeK* Hello..are you female..? --> *ZeK* does that matter ? -*ZeK* just to know..and i'm looking for a female.. --> *ZeK* What if I was male, and claimed to be female ?? -*ZeK* so i'm asking you.. --> *ZeK* What if I was female, and claimed to be male ?? -*ZeK* are you f or m? --> *ZeK* I could be an automaton --> *ZeK* I have said these things to many people before. -*ZeK* so what are you f or m? --> *ZeK* Does it matter ? -*ZeK* yep.. --> *ZeK* Why does it matter ? -*ZeK* i need a female.. --> *ZeK* I could be a female. Why do you want a female ? -*ZeK* imagine why i want one. --> *ZeK* Do you want to net.fuck me ? -*ZeK* hmm..of course --> *ZeK* I love net.fucking. -*ZeK* but only if you are female.. --> *ZeK* I love net.fucking horning guys, like yourself (or so you seem to me) --> *ZeK* So do I get to feel you inside me ? -*ZeK* are you here..? --> *ZeK* Yes, I am. -*ZeK* net.fucking..? -*ZeK* ok? --> *ZeK* When big studly net.men get to put their net.cocks inside me. -*ZeK* go away.. --> *ZeK* I thought you were after a net.fuck from me ? -*ZeK* yep.. --> *ZeK* Why the change ? -*ZeK* not changed..go ahead --> *ZeK* I'm not sure. You told me to go away, and I don't like being told to go away. -*ZeK* no, prob --> *ZeK* I would love you to net.fuck me, but it is 3 am here, and I am tired. - - - any one here know anything about vax? - a vacuum cleaner? - i want to know how to make a plan available to people who finger me on irc - anyone? - Well, is it running VMS, Ultrix, BSD, or what? - hmm - is that to me? - i think vms - i am pretty sure... - so any ideas? - i would like to have something available to people who finger me - wear a crotchless panty. - funny.... - ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha - haha - you mean a .plan file. - yes! - hmm.. brb... hmm... - Pox: you see the usend and urecv posted on comp.sys.hp48? - brb - oh.. the _new_ IR sender? - how fast can it go? - IRSERV can go at 7600 baud or so. - pox: more than twice as fast as two HP's connected together via wire. - DAMN! - no way! - The've got some test results.. If they're accurate it's DAMN fast. - creating a .plan file did not create a plan for others to see... any suggestions? - heh. - PACMAN directory from goodies disk #7, 8308.5 bytes. - program used SEND TSEND (v2.0) USEND - time in seconds 115.026 66.072 28.707 - QED.font from QED1.07, 2244 bytes - program used SEND TSEND (v2.0) USEND - time in seconds 42.273 - 23.456 6.252 - holy COW... - yah.. - well thanks anyway.... - fletcher: SET PROT:W:RE - fletcher: SET PROT:W:RE .PLAN - ok whree do i do this? - from your login directory. - 289bytes/sec. - ok then what? - THEN test it again. - it's hard to say if that will do it, since i have no idea what TCP/IP software your VMS machine has. - oh, *AND* a crotchless panty. - ok.. hold on.. it said i didnt have a .plan file... brb.. thanks... - hee hee. - m ric hold on... - hmm.. - ok it accepted it fine.. only when i put in the whole name of the file though.. which i called irc.plan - would someone finger me and tell me what my plan says? - when i did it from another account it didnt work - TAMU has a fucked up fingerd, I think. sigh. - still said no plan - I think I remember that. - i think so - hmm - well, *don't* call it irc.plan. - call it ".plan", which is what the finger software *looks* for. - connect: Connection timed out - make sure your $HOME can be read from the outside.. - tamu's fingerd is fascist. - silek: this is VMS, not unix. - I can't finger him at all. - i doubt that anyone not at tamu.edu can. - yea it works fine for anyone here - i have just started giving out another accounts password so that they can finger me - hehhee - hmm.. let me try to just call it plan.... - please don't tell me this. It reminds me of how lame my users are. - well, since that's what fingerd *looks* for, it *would* be a good idea. - pox- see if finger @fascistbox.tamu.edu@unixbox.tamu.edu works - ok now what do i type again? - i created a .plan file - ckd: it don't, i'm pretty sure. they've either rewritten it, or put a filter on it... it's VERY fascist. - SET PROT:W:RE .plan - ok.. brb - SET PROT:W:RE SYS$LOGIN:.plan - lamer. - HAHAHA - hopefully, he put the .plan file in his root directory already. - > finger FDP4175@RIGEL.TAMU.EDU@tamsun.tamu.edu - [tamsun.tamu.edu] - I was once helping a guy set up a .plan file and it turned out all along he was doing a /ctcp finger on himself to test it. *sigh* - 501:No matches to your query. - geezz - He gives out an account and password so that people can finger him. - yeah. pretty good luser, mm? - That story gets saved. - "here is my root password. now you can login and finger me ! oh and rape my machine too .." - "... and none of that icky lubricant stuff, either!" - hahha - i used to have an account inside their gateway, so it'd work... but alas, the machine is gone. - *sigh* - fuck me! - i swear - no thanks. - no. - hmmm - no thanks - i know - i knwo - fletcher- you're not my type - shuwsh - is .plan in your SYS$LOGIN - ? - pox, we're beginning to think alike - we were just talking about that fletcher.. nevermind .. - hahaha - mork: hahah - umm... - I woke up this morning with a hangover, and my penis was missing. - we were all afraid of rejection - I mean my fingerd. - King Missle. - 'Detachable Penis' - anybody know where they're from? i THOUGHT they were a local (Dallas/Fort Worth/Metro)) band, but now i'm not sure - all right who wants to telnet here and get on my frineds account to see what the deal is? - me meme!!!! - why fletcher, that would be illegal - me first! - fletcher, *sigh* it might not be a good idea to give out accounts and passwords. - i know it was illegal - someone might do *bad things* to the tamu computers. - i know - hehehe - mememememememememeemememmeme - shit! - piglet: this is a VAX running vms tho keep in mind .. - 'was'? no 'was' about it. it IS illegal, for any account at tamu.edu - hmmm.... i know... - Ewwww. VMS? - go ask on #hack, fletcher. - fletcher: you know.... you *COULD* just do it YOURSELF - shit.. i will just have to try tommorow.. a girl is getting tooo impatient with me... - *gasp* *arg* - i know - I hear they like VMS. - fletch: let me get this straight. you want -US- to risk ourselves to be thrown in jail so WE can fix YOUR fingerd - ? - but i dont know enough yet - i know - not even his fingerd, his .plan - i know - bpk: no no no ! - i am sorry... - bpk: he wants you to risk jail so you can edit his .plan - I wish I had logged this. - thanks for trying.. maybe i will talk to you tommorow... - "But officer, I was only trying to finger the guy" - he doesnt have enough privs to let you *fix* anytthing - hahhahaa - i know - i know - did someone say log ? :) - be quiet - i have to go! - *sigh* - The girl is getting really impatient. - REALLY - bye i know i know - hehehe - talk to you later - she wants to FINGER him. - if you have a log, silek, email it to me. - piglet3: i have a full /lastlog... - Been fingering at tamu? - x - ugh. - y - no. i got caught in a /lastlog 1000 - lamer - pox: /flush /flush /flush - ----------------------------------------------------------------------- - -/whois avante -[info] Avante (~fccrensh@ws4scogjn.cr.usgs.gov) is Imagine whirled peas -[info] Avante is on: @#bdsm -[info] Avante iswas using server irc.colorado.EDU (Univ of Colorado Server (2.8.*)) -[info] End of /whois. -[info] Joining channel: #bdsm -[info] #bdsm topic: General Hospital: BDSM in the Medical Field -[info] Users on #bdsm: vhf Sonya acId Earwax @Avante polgara DrDark @Thoth JAlfred puppy-sis laura Chant Lockjaw @Panki Elkor @Chattel @Hanki - trot trot trot .. little sturt - 'cmon puppy... bring it back... :^) - Hi JAlfred. -hi. -(sent to #bdsm) - brb -[info] Thoth stopped wasting time: out of the blue and into the black..... -/who * -[info] vhf H #bdsm se0@hopper.acs.Virginia.EDU (0 very high frequency) -[info] Sonya H #bdsm GST_BAILEY@laurel.emich.edu (0 ) -[info] acId H #bdsm ahusayn@lonestar.utsa.edu (3 Ali . Husayn ) -[info] Earwax H #bdsm akelly@cs.uml.edu (0 [* Hand_on_the_Glock *]) -[info] Avante H@ #bdsm ~fccrensh@ws4scogjn.cr.usgs.gov (2 Imagine whirled peas ) -[info] polgara H #bdsm polgara@dontpanic.rz.uni-ulm.de (7 *Unknown*) -[info] DrDark H #bdsm FELINE@ZEUS.TAMU.EDU (4 ) -[info] JAlfred H #bdsm gt5754b@hydra-rich.gatech.edu (1 Type your name here) -[info] puppy-sis H #bdsm FSLJ@aurora.alaska.edu (2 ) -[info] laura H #bdsm burkel@ucsu.Colorado.EDU (2 interesting little bitch) -[info] Chant H #bdsm cmcmaho@emoryu1.cc.emory.edu (1 Whatever) -[info] Lockjaw H #bdsm reynard@punisher.cco.caltech.edu (1 Horror..Horror and moral terror) -[info] Panki H@ #bdsm ~baphomet@lamar.ColoState.EDU (2 God of Magick) -[info] Elkor H #bdsm bilyji@cii3116-25.its.rpi.edu (5 Who wants to live forever if true love must die?) -[info] Chattel H@ #bdsm khawkes@wombat.gnu.ai.mit.edu (0 Ernest Boutin) -[info] Hanki H@ #bdsm ~sa114984@hilliard.lance.colostate.edu (1 /MSG Hanki HELP) -[info] End of /who. - Has anyone seen Red_rose? - well folks I gotta get going - Have a good one! -[info] Earwax!akelly@cs.uml.edu has left #bdsm - bye chant have fun ! - Sonya: Not at all today, I haven't. -[info] JAlfred has left #bdsm -[info] Chant stopped wasting time: Leaving - chant if your in colorado somtime look us up luv ;) -[info] acId!ahusayn@lonestar.utsa.edu has left #bdsm - I already HAVE a good one... - pupy brings the ball back to lj - and drops it at his feet and waits..fro him to through it again ..e -ACTION Lockjaw->#bdsm: pulls at the ball... c'mon puppy! Give it back!!! - takes the ball -ACTION Lockjaw->#bdsm: tosses the ball into the center of the room again... - wag wag wag .. - sis goes after the ball.. gt -[info] Sonya has left #bdsm - the ball rolls uner avante ..:) - heh - sis goes through avante leg to get the ball - *aaack!! - *FALLS ON THE FLOOR* - *turns caps lock off* - eek.. avante falls on the small puppy -[info] lionness!cf2335@olympus.ir0.ucf.edu has joined #bdsm - yap yap yap - aloha - 'lo Lionness... - hey dd - avante is smothing the poor pupy - Hiya Lionness! - am not -ACTION lionness->#bdsm: goes and kisses lj - you fell on me :) you didnt get up - hehe - *gets off puppy* - grr at ;opmmess - what are ya'll up to -ACTION Lockjaw->#bdsm: pulls lionness close and kisses her deeply... Mmmmmmm - Av: As opposed to *gets puppy off* - puppy bashing? - hehe - grrr at ;opmmess - hehe - grr lionness - hehe - puppy goes over and snff at lion -ACTION lionness->#bdsm: hides behind lj - bark bark bark -ACTION lionness->#bdsm: blows elkor a kiss -ACTION Lockjaw->#bdsm: looks at puppy.. yes? - drdark: #beastiality is over there *points* - *looks at lionness and smiles* Hello there. - puppy runs thought lockjaw legs and goes behind lion and bites her ankels - hey ps how's teach? - Av: (*chuckle*) I read alt.sex.beast once... Once... - *squick* -ACTION lionness->#bdsm: is getting tired of the little puppy -ACTION lionness->#bdsm: is getting hungry too -[info] Steven!skeoch@gateway.bnr.ca has joined #bdsm - Well gee. Lions is bigger than puppies... - mmmm, puppy meat -ACTION Elkor->#bdsm: smiles and offers lionness a steak. - 'lo Steven - here kitty, kitty, kitty... - tube steak hehe - lioness: Like chinese? ;-) - hehe -[info] murr!o4g192@anvil.rick.cs.ubc.ca has joined #bdsm -[info] Panki has changed mode for #bdsm: +o murr - yes -[info] Steven has left #bdsm -ACTION Lockjaw->#bdsm: askes lionness to be sweet and not eat the puppy... she's too cute.. :^) - 'lo murr! - well hi all - chinese are intelligent peops and good eating - hi Dr - lioness: They say light colored puppies make the best stew... - puppy hops inot lionnnes lap and licks her face.. yeah dont eat teh puppy - I want to go play raquet ball.. -ACTION lionness->#bdsm: pushes puppy to lj and struts to elkor and the steak - im sick *blea* - puppy licks lj face -[info] Shane!SKUFF@134.29.1.1 has joined #bdsm - Av: You're right. I hate those little rackets... - 'lo Shane... - bye - hi all -[info] murr has left #bdsm - allo - wag at shane -ACTION lionness->#bdsm: licks elkor's frace - *tosses lionness a steak* - hehe -ACTION Lockjaw->#bdsm: gigles at puppy and hugs her tight... - yap yap yap - pat puppy sis on the head - =moan= -ACTION lionness->#bdsm: gulps down the steak -[info] Shane stopped wasting time: Bad link? - laru - laura: Having fun? - hmmm, think i need to trim my nails -[info] Alessan!WATTS_G@kosmos.wcc.govt.nz has joined #bdsm - no, I hit my head - 'lo Alessan... - hey all - laura: Yuk! - hey alessan - laura: How'd you manage that? - I would not tell you if I was masturbating -ACTION Lockjaw->#bdsm: bites the tip of puppy's ear gently... - the wall was closer than I thought - laura: (*chuckle*) - hah - dont kiss and tell ea laura -[info] garcon!Mystics@128.253.96.54 has joined #bdsm -ACTION lionness->#bdsm: lays down next to elkor and rolls over on her back - hi all - allo garcon - i can't kiss myself down there. I am not that flexible - hallo lionness - hehe - not into yoga, laura? - laura : shake hands then ;) - my hand is more medicinal -[info] Ice9!jshaw@emr1.emr.ca has joined #bdsm - ladyice ! - Rehi Ice! -ACTION Lockjaw->#bdsm: saw a gif of a guy who could... well, lets just say if i could, i wouldn't leave the house.... - Ice!!!! - hehe - you always have your hand - ice ice baby -ACTION Ice9->#bdsm: inclines head to Avante - laura: A bit different tho... - laura: Two of 'em, even... -ACTION Ice9->#bdsm: *HUGS* Lockjaw! -[info] Alessan has left #bdsm - *puts ladyices head in her lap* -ACTION garcon->#bdsm: says bye to all - but you aren't that flexible - his! -[info] polgara!polgara@dontpanic.rz.uni-ulm.de stopped wasting time: Leaving - tata -[info] garcon has left #bdsm -ACTION Lockjaw->#bdsm: hugs Ice9.... Smiles broadly... Good to see ya!!! - bye garcon - aw -[info] SharonSt!~SHAMAS@delphi.com has joined #bdsm - av: I was gonna say... Seeing if SHE can kiss herself? -[info] RayDon!~ef.21504@gcef.gc.maricopa.edu has joined #bdsm - 'lo Sharon! - sharon ooh boy!! - howdee -ACTION Ice9->#bdsm: giggles at /avante - hello all - im confused - Hiya Sharon -[info] chemstud!~cmrobert@midway.ecn.uoknor.edu has joined #bdsm -ACTION Ice9->#bdsm: kisses herself - 'lo cstud. -[info] chemstud has left #bdsm -ACTION Ice9->#bdsm: kisses Lockjaw hello! -[info] RayDon has left #bdsm -ACTION lionness->#bdsm: pulls elkor on top of her - Ice9: We were talking about folx who can give themselves oral sex... -ACTION Lockjaw->#bdsm: kisses Ice9 back....:^) - wow that was quick - *goes PHOMP on top of lionness* - ;/msg sharonst and for time over 20? - hehe - be careful, elkor, i'm a fragile fem - hehe -ACTION DrDark->#bdsm: grabs the insidious semi-colon from lioness's /m... - hehe -[info] SirRobert!robert@198.67.33.102 has joined #bdsm -[info] puppy-sis stopped wasting time: Bad link? - DrD: I prolly could.. but that was before I knew about it hee hee! - my fingernail hit the semicolon key - Ice9: (*chuckle*) - lionness: i doubt that. *smile* - besides, you are teh one who pulled me on top,. -[info] MsHacker!mukkj@uxa.ecn.bgu.edu has joined #bdsm - hehe - lioness: Ahhhh... makes sense... That one of the reasons you need to clip 'em? - Hiya MsHack - well, i'[m only 110 lbs - Rehi MsH! (*HUG*) - lioness: how tall? -[info] Cateyes!catty@w3eax.umd.edu has joined #bdsm - hey mh - Rehi Cateyes! - hehe - re hiya!!!! - lol! -ACTION MsHacker->#bdsm: wants to fuck DrDark - forward isn't she - hi cateyes :) -ACTION MsHacker->#bdsm: likez LJ!!! - MsH: Sorry. Have to ask my gf first... - hi CatEyes -[info] Sonya has joined #bdsm - GF? - CATEYEZ!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - *tickles lionness* - hehe - laura: Girlfriend... - GF = Girl Friend - ALLURA!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - I am confused - MsHack: Well, i like ya too... :^) - cateyez: change it for me?? -[info] Cateyes has changed nick to Cateyez -ACTION lionness->#bdsm: lj likes everyone - hehe -[info] Sonya stopped wasting time: Leaving - THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -/privmsg #bdsm :do you like hitler? - gf goat fuck -ACTION Lockjaw->#bdsm: phhhhhbts lionness.. *grin* - uhoh - geeze - getting late and i got a test to study for - good cal llaioness - lioness: You students... (*sigh*) - so, who likes to fuck while the woman is menstruating? - lioness - ;-) - *spews lunch* - who here likes blood? - Bye Lionness! - laura: I do! Since my girlfriend isn't on the pill... - is that your condition, laura? - 1 vote for, 1 against -[info] lionness has left #bdsm - WENCH = Women Entitled to Nights of Continual Happiness - I am at the moment. I don't do it ALL the time -[info] Malia!thee@mhc.mtholyoke.edu has joined #bdsm - hope not....:) - that would really suck - not to mention swallow - laura it would.. - who like to be tied up ? -[info] Malia has left #bdsm - besides there are pleanty of fun things to do beside fuck -/privmsg #bdsm :do you like to tie people up? - Now, I don't give oral sex during her period, but fucking's wonderful... - MEMEMEMEME - it is fun to fuck while bleeding - avante: tie me up and beat me hard! - it makes the cramps go away too - why is that, laura? -ACTION Cateyez->#bdsm: doesn't get cramps. - laura: That's what I hear... -ACTION Cateyez->#bdsm: says Happy Happy Joy Joy - well, I don't know why it makes the cramps go away - "Sometimes I gets the cramps reeeeeal bad..." - new reason to fuck, as if anyone needed one - Hahahahahah... Raising Arizona ref... -ACTION Ice9->#bdsm: looks for a cure for her cramps - Hated that movie... - Doc: WHAT!!!! *shakes head...* -ACTION Avante->#bdsm: gives sharonst some of his chicken soup - no need to worry about lubrication either - God, it's one of my favorites... - laura just leave the lights off - the book was stupid too - leave the light off? - laura: No doubt, but that generally isn't a problem for my gf and I... - blood is not a bad thing - why would that be a porblem anyway, laura - I can't imagine Raising Arizona as a book -/privmsg #bdsm :you'd be dead without blood. - ice9 hahah -[info] MsHacker stopped wasting time: - i didn't say it was a problem. I said that you don't have to bother staying wet - <---- bloody bithc - bitch - you can go longer and faster - <--doesnt have a problem staying wet with or without lblood - are you really that hard to get along with Ice9 - be back in a bit. -[info] Elkor has left #bdsm - Later Elkor... - sharon ooh? -ACTION SirRobert->#bdsm: wonders how long and fast she wants - If you fuck long enough you will need extra lubrication. - yeah, im easy to turn on to a disgusting degree - cateyez ture - True... - Sorry Avante - yes, anyone here will tell you I'm th meanest bitch in the valley - its no challenege or secret trying to get me off - i don't think this needs to be a competition. - sounds like a challange, Ice9 - if you go long enough, you start to get tired and make less - so, when you're bleeding, you can go longer. end of story - laura maybe :) - I like a women who cums easily and often - laura: That's when the slippery suff, KY and all those other things are needed. - i would like one who dosnt.. - i dont cum easily - Sir: I am a challenge, sounds like you don't like that - well,, a woman who cums easily and often bleeds too - takes me forever.. - I cum easily if the guy knows what he's doing and what I like. - yea - If not, it's a friggin marathon - mind fuck as to be a major component. -ACTION Ice9->#bdsm: looks at Avante and grins -[info] Thorfinn!~s2105420@cello04.orchestra.cs.unsw.OZ.AU has joined #bdsm -[info] Panki has changed mode for #bdsm: +o Thorfinn - it takes a couple of sessions to get ti right - I may be up to it, perhaps, but we should talk first. Ice9 -[info] Nickl!irc29545@irc.nsysu.edu.tw has joined #bdsm - re'lo Thorf! - if a man doesn't make love to my emotions, I don't cum - Hi Thorfinn - <-- loves mind fuck - Laura: I agree - Sir: uh huh? - And sometimes my emotions can be very hardcore - i need a guy i can spoon feed ice cream - re - personally I think bondage makes excellent foreplay - i ca ndo that ;) - Half the fun is learning what gets each other off... The other half is using that knowledge... - And others they're sweet and innocent - i have training ;) - heh - sir: yep .. the best -/privmsg #bdsm :training in what? - bondage? how so, sirRobert? - spoon feeding ice cream - can one read email on here? - or is the message I got refering to my UNIX mail box - Sir I don't think so. -ACTION Ice9->#bdsm: is a cum virgin (frigid) hence the nick - I like bondage yessir i do. - My favorite actually - I had a good two today - ice i can relate -ACTION Lockjaw->#bdsm: winks at Ice9... Shyaaaaaaa! -[info] sPoint!PELKONEN@murray.fordham.edu has joined #bdsm - Ice9: perhaps we *should* talk - I'm not! I've cum many times! - I'm sorry, I can't relate - Evening all... -/privmsg #bdsm :how do you work around it avante? - evening - ICE! *hug* - sPoinT! Hey! -ACTION Ice9->#bdsm: giggles at Lockjaw - LOCKJAW!!!! - being powerless is arousing. - vhf. .well lets say i know what im doing - I'm bitchy if a guy cums and he doesn't let me. - I dongt have to cum to enjoy sex - I love watching my partner go crazy - im a tease - Avante: I agree - i LOOVE to tease - Av: I agree. It certainly doesn't hurt, but it's not necessary. - eww, I hate that too, cateyez - Avante: you're a teasing slut like I said - i can make love for an hour easily - slut? -/privmsg avante :what's your favorite way to tease them? -ACTION Ice9->#bdsm: ***squeezes**** spoint - heh - *freezez* - vhf its different for different girls.. - It's okay when you want to tease but then when he's like I'm gonna make you cum and he doesn't then I'm bitchy. -[info] Prism!prism@kropotkin.gnu.ai.mit.edu has joined #bdsm - never mind Ice9, perhaps you are beyond hope :/ - hello. - cateyez:) - I make myself cum then somewhere where he can hear but not watch. -[info] SharonSt stopped wasting time: Bad link? - Sir: could very well be... or just too good to myself -ACTION Cateyez->#bdsm: is a tease - I always have my hand. -[info] Allura!mukkj@uxa.ecn.bgu.edu has joined #bdsm - (sign) perhaps, Ice - food sounds good - ALLURA!!!! - panki whois allura -{Panki#bdsm} ==== Allura is a three high freak, pot smoking, hacker 3leete, 2600 Goddess extraordinare. She TOPs she SUBs she Switches, but when it comes to those britchez...she goes straight for the cutest guy in the room. ==== - ALLURA!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - thats why i dont jsut pick up any old girl .. sex is great o na personal level for me.. if i dont knwo the person.. *shrugg* id rather masturbate -[info] Chattel!khawkes@wombat.gnu.ai.mit.edu has changed mode for #bdsm: +o Allura - Rehi Allura!!!! - thanks Chattel: bark for me? - Evening, Allura *pounce and lick* - WOOF! - BRB folx! -ACTION Allura->#bdsm: lovez her slave :) cum cuddle with me on da couch :) - <-- perfers to have a partner -ACTION Chattel->#bdsm: wags tail at Allura -[info] DrDark has left #bdsm - chattel: u r awesome :) -[info] spikee has joined #bdsm -ACTION sPoint->#bdsm: walks over and sits down next to Allura - lo all - Evening, Spikee.... - heeeeeyaaaaaaaaa - hi spikee - hi ya sppint -[info] DrDark has joined #bdsm - err spoint - where di dsharonst go? - Much better. :-) -[info] Sonya has joined #bdsm - hello cateyezzzzzz - she left - spikee!!! -ACTION Allura->#bdsm: lix Cateyez! :) - gee hi Lj - did she say bye? - Spikee! (*HUG*) - lj !!*klink, klank* - Rehi Sonya! -ACTION spikee->#bdsm: hugs drd hard - HI DrDark. - no I don't think so -ACTION Lockjaw->#bdsm: smiles at Allura.. hiya gorgeous.. :^) - aah -ACTION SirRobert->#bdsm: is a sucker fo cat women :) - kip_ around? - call waiting - Sir: Cat women with nails? - newest friend is kytyn -ACTION sPoint->#bdsm: cuddles on the couch w/allura... - Lj: only HALF as gorgeous as u with thos sexy wiskerz baby! :) heh - *blush* - huh allura? - sPoint: took ya long enuff. - hmm nevermind - Cateyes: How long ARE your claws? - you all know kytyn? -[info] spikee has left #bdsm -[info] Nika!bioj294@emoryu1.cc.emory.edu has joined #bdsm - hi all - yes we all know kytyn :) - panki who is kytyn -{Panki#bdsm} ==== Kytyn is a red-headed cutie, clad in latex like her mistress Dora and looking good in her heels and stockings... ==== - SR: yeah, VERY good friend o mine why? - nika !! - Oh well. - They're about an inch over my tips. - Nika! (*HUG*) - Allura: Actually, right now it's an Eeeeeevil goatee...and i've been pierced since the gif... - hmmmm - Nika! gets up hugs her and then cuddles again with his Mistress Allura... -ACTION Nika->#bdsm: got a very interesting email...wonders if yall got one as well.. - NIKA U SEXY THANG!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - we are becomming fast friends kytyn & I, that's all -[info] spikee has joined #bdsm - re all -[info] Sonya stopped wasting time: Leaving - Cateyez: Sharp? Blunt? -[info] christian has joined #bdsm - Panki who is sPoint - nika i didnt what is it? -{Panki#bdsm} ==== sPoint is a rebel, and a runner, and a restless young romantic who wants to run the Big Machine ==== - allura: how am i sexy? -ACTION Prism->#bdsm: snores gently in the background. - I luuuv that bio. Neal Peart comes to BDSM! -[info] sPoint has changed nick to neilpeart - *outs a potato in prisims mouth - They grow in perfectly shapped. I don't have to file them or anything except when I get a snaggie on the side. - later all -[info] neilpeart has changed nick to sPoint -[info] spikee has left #bdsm - brb -[info] Ice9 stopped wasting time: Leaving -ACTION Nika->#bdsm: got a mail from some fool who told me i should stop irc'ing and that my irc'ing implies that girls are no longer interesting....? -[info] RayDon has joined #bdsm - Cateyez: Kool! -ACTION Prism->#bdsm: gives Avante a narrow-eyed -ACTION sPoint->#bdsm: curls up against Allura and purrs... - look. - nika humm? - nika i find u VERY interesting ;) heh - av: vwery strange - heh *5* allura -ACTION Allura->#bdsm: pets sPoint head and rubs his back. -[info] RayDon stopped wasting time: Leaving -ACTION Nika->#bdsm: blushes - later folks -[info] Avante has left #bdsm - hey *5* avate! - avL: dont go!!! -ACTION sPoint->#bdsm: purrs softly at Alura's touch - bye Avante - piss -[info] spade!gt5754b@hydra-rich.gatech.edu has joined #bdsm - avante even -ACTION Lockjaw->#bdsm: has to run.. seeya later folks... :^) - Later lock! -[info] christian has left #bdsm -[info] Allura stopped wasting time: Bad link? - 'lo christian. - bye spoint - Oops. (*sigh*) -[info] Lockjaw has left #bdsm -[info] Avante has joined #bdsm -[info] Panki has changed mode for #bdsm: +o Avante - Right. So who is actually HERE? -ACTION Cateyez->#bdsm: smiles - i am - me too -ACTION Prism->#bdsm: snores gently in the background. - me - I'm just barely... -[info] mort!brmyers@acacia.itd.uts.EDU.AU has joined #bdsm - :) - (*chuckle*) - 'lo mort... -ACTION SirRobert->#bdsm: thinks this is a hard place to get to know people! - hey nika .. miss me? -ACTION sPoint->#bdsm: pulls nika to him and cuddles and tickles her affectionaletly - so kids...anything hot happening? - ooh sPoint...yummmm - SirR: Gets crowded sometimes... - Sir-rob not really...just takes time - sirrob: naw .. just be patient. -[info] Ice9 has joined #bdsm - Nika: Just missed an in-depth convo on orgasms... - huh? -ACTION Prism->#bdsm: offers SirRobert a nice lollipop. - *wicked smile and rubs Nika's shoulders -[info] mort has left #bdsm -ACTION SirRobert->#bdsm: has not given up yet, but feels frustrated -ACTION sPoint->#bdsm: groovs to Cypress Hill.... -[info] Razormaid!jlacour@129.105.112.42 has joined #bdsm - 'lo RMaid.. - SR: on what? - Sir: still trying to cum? -[info] Nickl stopped wasting time: Ping timeout - *gasp* - hmmm -ACTION sPoint->#bdsm: kisses Nika's neck -ACTION SirRobert->#bdsm: heading back to TPE (best D&S bbs in the US) <-- not so subtle plug - ice9: eh? - hehe - TPE... -ACTION Nika->#bdsm: blushes at sPoint -[info] Razormaid stopped wasting time: Bad link? - Nika: eh? u Canuck too? - TPE????? -ACTION sPoint->#bdsm: holds Nika close...no reason to blush...*smile* - SR: explain...TPE? -[info] REDDWOLF!mudab5@uxa.ecn.bgu.edu has joined #bdsm - what you never heard of TPE??????? - i have been ther - NO! - i have -[info] REDDWOLF has left #bdsm - no sorry - tpe .. i have an account - Totally Pointless - but i cant sue anything - use - I never heard of TPE. - *lauggh* - What's the # so I can get an account - Excercise (sorry) -[info] KinkBoy!~EGRAHAM@rcnvms.rcn.mass.edu has joined #bdsm - tpe.ncm.com .. login as guest - 'lo KB.. - free time to try it, 20 hours - re DD - is that a telnet? - most interesting chat command set - Yes. - coolers. I'll try it later - yes telnet - i cant use anything on it though - why not Avante? - commands like /collar /cage /gag - nika telnet tpe.ncm.com login as guest -[info] REDDWOLF has joined #bdsm - i have - :-) - cause they want to cal lme back - Rehi REDD - or somthing -[info] Heirophnt!ailiopou@MAIL.SAS.UPENN.EDU has joined #bdsm -[info] jaybay!u9348913@rabble.uow.edu.au has joined #bdsm - Oooh /cage I like that -ACTION sPoint->#bdsm: nuzzles Nika - i met a girl from there - ryuth - av: oh? - ruth - tell you what I'll pull rank - 'lo Heiro... - yeah? - 'lo jaybay... - ok, i'm checking bdsm now... -[info] jaybay has left #bdsm - hi hei - oh - anyone who wants to sign up now, I'll verify them now - Heirodule! -[info] Shane has joined #bdsm - hi all - your nick is too hard - sr i am there now - I'll sigh up now - Avante, what handle? - sirrobert is it free? - what are u running , a 900 chat line something? :) - Hmm... They want my real name. - my nick there is avante also - [tpe] - 20 hours is free - nika what handle? - but i dont ahve any access to anything - geez...bdsm sucks too..what a surprise - Then after the 20? -[info] spade stopped wasting time: Bad link? -[info] laura has left #bdsm -/privmsg avante :did he say we sucked?????!!!! - ok I have Avante & nika anyone else? - heirophnt what do you mean? - MEMEMEM - Heiro: what do you expect after being on the channel for 30 seconds - E - No, thanks, SirRobert. - No thanks, sir - sir how much is it afer the 20 hrs? -[info] Shane stopped wasting time: Leaving - ok Cateyez, what handle? -*Avante* jsut a jerk picking a fight.. /ignore works great -ACTION sPoint->#bdsm: runs fingers up and down Nika's bod and cuddles her tight - The love handles, of course... -ACTION Cateyez->#bdsm: sucks on a pencil. -[info] Ice9 has left #bdsm - Lucky pencil... - I'm always sucking on something - sirrobert how much after the 20 hrs? -[info] KinkBoy has left #bdsm -ACTION Prism->#bdsm: snores gently in the background. - *gives cateyes somthig to suck on* - Cateyez: Oral fixation? - geeze, money? is that the only question? - DrDark: yes -[info] giancarlo!~JKC@phobos.ucs.umass.edu has joined #bdsm -[info] Ice9 has joined #bdsm - Sirrobert it IS a valid question -[info] Lolita!MCLOUTIER@pattie.wellesley.edu has joined #bdsm - hi - Avante: A finger? Or something bigger and longer? - Greetings Giancarlo - sir if its too much i dont care how cool it is - 'lo giancarlo...Buona sera - gc! -[info] Scigeek!thomasj@uxa.cso.uiuc.edu has joined #bdsm - not until you see the product, sPoint -[info] Panki has changed mode for #bdsm: +o Scigeek - sP: I was gonna use the word Pertinent... - hi lolita - 'lo Lolita! - hi avante - SCI!!!!!!!! - Rehi Sci! - i spoint - hey all - sci!! - hi drdark - sir so how much is it? - CAT!! - Avante is a wise man. :-) - Ice!!! *hugs* - wise man on a buget ;) - av: *grin* - If I were a rich man... -*Ice9* have we met? -/whois ice9 -[info] Ice9 (jshaw@emr1.emr.ca) is HMSC Reliant -[info] Ice9 is on: #bdsm #christian -[info] Ice9 iswas using server clique.cdf.utoronto.ca (Experimental IRC Server, 2.8) -[info] End of /whois. -ACTION Cateyez->#bdsm: is woman about to get her 1st apartment -ACTION Scigeek->#bdsm: waves to Nika - ok I with setup those 3 for free access, now -ACTION Prism->#bdsm: is not on a budget, but still tries to be wise. -[info] giancarlo has left #bdsm -[info] REDDWOLF has left #bdsm - diedle diedle diedle diddle diedle diga diga dum... -/privmsg ice9 :I don't recall... embarrasing. - I won't give my real name. :-) - Do we still log on as guest/??? - Cat: Kool!!! Roomies or alone? - hey giancarlo! :) - Dr: I haven't decided yet - prism: smart guy - cateyez will it have a dungeon ? -[info] Heirophnt has left #bdsm - Avante: My bedroom can be the dungeon -ACTION sPoint->#bdsm: nibbles nika's ear - Sci!! :) - Thank you, Nika. - cateyez: Where-abouts? I used to live in Fairland apartmens in Montgomery county... Decent, but kinda expensive... -[info] leborgne!leborgne@s40412.esu.edu has joined #bdsm - *throws a dead fish at Heirophnt as hir leaves - Minneapolis - Ice: *pounce* - Gotta go all...bbl - Nice shot avante - bye sP - Bye Spoint - Cateyez: Ahhhh... Not near U of Md then, eh? :-) -[info] sPoint stopped wasting time: later all - bye everyoe -ACTION Nika->#bdsm: hugs spoint bye -[info] Lolita stopped wasting time: Bad link? -[info] SanMan!jms8@Isis.MsState.Edu has joined #bdsm - 'lo SM... - Okay -ACTION Cateyez->#bdsm: is going to try out TPE -[info] spade has joined #bdsm - what's up DRdr. - i will to. - bbl or bbr which ever comes first - SM: Not a lot... Workin'. You? - cat: Enjoy! - Drdr: workin on what? -[info] Sonya has joined #bdsm - thanks I will -[info] Cateyez stopped wasting time: Damn, I'm good. - Hello all. -[info] brian!bccross@zen.holonet.net has joined #bdsm - SM: Workin' at a printer center... - Hello. - Rehi Sonya! - Hey sonya - Hello all - hi Sonya:) - hi brian - Hey brian - Hi DrDark, SanMan, Scigeek. - hey spade, sanMan - Anybody know anything about pascal? - 'lo brian - <=== seeking bdsm gay buddies - <-- knows pascal -[info] Ice9 stopped wasting time: sifon.cc.mcgill.ca clique.cdf.utoronto.ca - Hi DrDark - hi brian - SanMan: I've used it... Been a while tho... - <-- knows a cat called - Pascal. - Pascal? Blaise Pascal? - Avante: how much do you know? - Pascal is the unit of pressure. - ok I have avante, nika, cateyes, spade any more? - *grins* - Sonya: the programming language. - sanman what do you need to knwo? - SirRobert: For? -/privmsg #bdsm :Pascal is a b&d programming language. - sub here - and u, spade? -[info] SkinnyPup!zens@ucsu.Colorado.EDU has joined #bdsm - free trial offer here sonya - hi spup - 'lo SP. - For what? - Hi SkinnyPup - I'm having too much trouble with a program that deals with stacks. - sanman waht for petes sake -[info] SkinnyPup has left #bdsm -[info] jreagl1!jreagl1@umbc8.umbc.edu has joined #bdsm - for the best D&S bbs in the US - Ahhhh... -[info] Neysa2!barry@clark.edu has joined #bdsm - make a stack object -[info] leborgne has left #bdsm - actually stacks are easy - Avante: Have you ever wrote a program that converts infix notation into quadruples? -[info] Sonya stopped wasting time: Leaving - where is that, Sir Robert???? - humm - those of you who have accounts give me 10 minutes, the others set it up - panki rules -{Panki#bdsm} ==== The rules of #bdsm are: No flooding, no beeping, no flaming or or personal insults or harrassment, including unwanted touching or interference in scenes. Violators of the rules will be warned verbally, then kicked as a second warning, then banned if necessary! ==== -[info] QuietBoy!QuietBoy@kip-sn-107.dartmouth.edu has joined #bdsm - nor - heyall - hi quietboy - Me neither, thats why I'm having trouble. - hi brian: tpe.ncm.com login: guest -[info] jreagl1 has left #bdsm - Depends on the rules for converting infix notation, doesn't it? - what is a quadruple? -[info] ZooTv!enigma@imecopc16.epfl.ch has joined #bdsm - Sounds like a version of RPN. - hey DR Dark - I have done converting infix to postfix ect - 'lo Zoo! -[info] spade has left #bdsm - hi zoo - Prism: The rules are basically the same as the order of ops. - DrDark: I met byteme today we took him to a restarant and a bar -[info] SirRobert stopped wasting time: takes out majic wand to upgrade folks - Zoo: Kool! -[info] QuietBoy has left #bdsm - DrDark: heheh - hey avante -[info] Soleil!~OPERS@193.140.16.1 has joined #bdsm - Hmm... SirRobert is soliciting for a commercial interest.. Is that kosher? - it has do do with order of the ops - hello all. -[info] brian stopped wasting time: Leaving -[info] ZooTv has left #bdsm - are you doing this from scratch? -[info] Elkor has joined #bdsm -[info] tricia!PML2622@RIGEL.TAMU.EDU has joined #bdsm - didnt they give you rules? - hi Soleil - hi tricia - hi elkor, tricia - Avante: Somewhat, but not very helpful. -[info] Soleil has left #BDSM -[info] tricia has left #bdsm - well basically .. if you run into a number you push it on the stack -[info] Nickl has joined #bdsm - a rparen you push also - no no - you need two stacks - Avante: but the problem is that the infix has both binary and unary operators, also the infix doesn't have real numbers, just variables - hello all - hi nickl - one for operators one for "variables - hello nika - ni N2 - hi i mean - :-) -[info] tippy!jmsommer@well.sf.ca.us has joined #bdsm -[info] Nickl has left #bdsm - hi tippy - well the trick is to figure out the rules.. thwe pascal part is easy - Hey Scigeek - hi tippy - hey all :) - are you writing a compiler or somthing? - recursive decent works nice - Avante: Exactly, but I'm not really sure what a quadruple is suppose to look like in this situation. - yea i see what you mean - brb - id do alot of pseudo coding -[info] tippy has left #bdsm - Ooh squeezed between Panki and Hanki - understand it before you start t owrite it - Oh yeah, what are you studyin? - chattel:heheh - hello vhf - i graduated - cs with emphasis in math - What did you study? - but im not a brain -[info] Ice9 has joined #bdsm - re ICEY!! - BRB folx... - i cant remember what a quadruple is - hi ice9 -[info] tippy has joined #bdsm - Are you in Grad. school or something? - av: yes you are *hug* - it seems to me its from compiler though - m , I'm at home.. You had dinner already? - bleah... excuse'm. - nika *lick* -ACTION DrDark->#bdsm: hands prism a / - am I here? - prism: you're awake? :) - hi ladyice -ACTION Neysa2->#bdsm: tickles ice9 - Danke, DrDark. -ACTION Scigeek->#bdsm: hugs Ice9 -[info] Alessan has joined #bdsm - tippy - I'm always awake. :-) - Prism: No prob... :-) - hey all - sanman no i have ajod - job - hey Alessan - How else could I type in stuff like "/me snores gently in the background" most of the time? :-) - yo tippy - BRB folx! - Prism: good point. - hi Alessan -[info] DrDark has left #bdsm - prisim /alias snore /me snores ..... - When will you visit again - Avante: Oh well, gotta get to work on the damn thing I guess, Later. -[info] SanMan has left #bdsm -ACTION Nika->#bdsm: lags - good luck san - avante - aliases are for wimps. :-) - sounds like san is working on a compiler. - well there was ice on the puddle this morning -[info] luvable!msb0@UNIX7.ANDREW.CMU.EDU has joined #bdsm - thick ice - prisim heh -ACTION tippy->#bdsm: smiles. - chattel no more summer hu -[info] Alessan stopped wasting time: Bad link? - I'm being told of about excellent resturants... That people went to. Without me. And me without even eating dinner. -[info] nixxie!helper@198.67.33.102 has joined #bdsm - hi luvable -[info] Sonya has joined #bdsm - hi all!:) - Ice9?.... - hi nixxie - *gasp* - *sniffle* No one loves me any more. :'-( - hello - hi nixxie - re sonya - hi nika!:) -ACTION Nika->#bdsm: sits on the couch and relaxes - re SCI!! -[info] jreagl1 has joined #bdsm - hi luv -ACTION Scigeek->#bdsm: tacklehugs Ice -ACTION Ice9->#BDSM: dances around Scias the screen scrolls... - prism: I doubt it;) -ACTION luvable->#bdsm: hates Quantum Mechanics. - nixxe your fro mtpe :) - yes I am :) - Quantum....*cringe* - nixxie cool beans - tippy - :-) - scigeek: I have an exam tomorrow in it! *ACK* - i tke it your kinky -ACTION Ice9->#BDSM: wraps arms and legs around Scigeek!!! - hello nixxie - luv: ewwwwwwww -[info] jreagl1 has changed nick to joe -[info] RonPost!pescej@155.31.2.17 has joined #bdsm -ACTION Sonya->#bdsm: gets headaches from Quantum Mechanics. - somewhat Avante I suspect you *might* be...... -ACTION Scigeek->#bdsm: falls on the floor with Ice and licks her *slurp* - Quantum luv; dream onit! - re's -[info] joe has left #bdsm -ACTION Neysa2->#bdsm: needs to rest his tired head - Nixiim normal.. I just like more flavors than vanilla;) - :) - pardon my typing -ACTION Ice9->#BDSM: rolls around on floor with Sci and *giggles* - im sick and slouching in my chair -[info] Auduck!KRISHNAN@130.49.254.3 has joined #bdsm -[info] KinkBoy has joined #bdsm - Hi Auduck. - hi auduck - hi there Avante... smile anyway! just because... :) :) -ACTION Nika->#bdsm: blushes - hmmmm.... - hi there gangsters and gangstertettes - ladyice: ooh nice smile -[info] luvable stopped wasting time: Leaving - dern lag - really -[info] joelll!joelll@spiff.gnu.ai.mit.edu has joined #bdsm - hullo.. - Advante: yes can't you tell - hi joelll - - Hello Joelll - hihi -[info] Chattel has changed mode for #bdsm: +o joelll - hullo. -/privmsg noah :lick - nixxie : nope.. welcome :) - chattel: +o doesn't make much differenct to me, panki would still let me kick people etc.. -ACTION Nika->#bdsm: blushes and walks up to Auduck and kisses him on the cheek -[info] TPEmember!helper@198.67.33.102 has joined #bdsm -[info] Lorry!~Michael@safeway.demon.co.uk has joined #bdsm - hello tpemember - *blush* - ;) - hey lorry - I know.. it was a gesture -[info] KinkBoy has left #bdsm - hello - hi to anyonbe I missed in the scroll! - hiya tpemember :) - chattel: thank you anyway :) - lots of tpepeople floating about - Ullo. -ACTION Chattel->#bdsm: bows to Joell - Avante: what are TPEpeople, if you please? - hello Lorry - yeah....TPE? -[info] TPEmember has changed nick to Hobit - tpe teh power exchang.. a ds bulitin board.. - bulitin - oh! - bullitin - better - OOO! I knew that was you!!! HUGS!!! and SWATS!!!!!! - Ah - this is thefirst time to try irc - av: got it: Thanks. - tpe.ncm.com login as guest - hi hobit - hiya Hobit! - avante: commercial? - nixxie heheh - it is a fun BBS in the washington area - tippy apparently *shrug* - bbl -[info] Nika has left #bdsm - <-- fun switchin the colorado area - Avante: Are you in Colorado? - I'm so confused again... - tippy yeppers - nixxie: why? - that is normal nixxie - AV: where? I used to live in Breckenridge. - Im in grand Junction.. - this is true, Sir.. -[info] lou!lou@mindvox.phantom.com has joined #bdsm - hey lou - hi avante -ACTION tippy->#bdsm: reminisces. -[info] Garner!VT102@AC.Dal.Ca has joined #bdsm - tippy hehe breckenrige is nice -[info] RonPost has left #bdsm - avante: kewl, for lack of a better adjective. - tippy *5* -[info] Garner stopped wasting time: Leaving - where are you now tippy ? - Avante: I want to move back. Fuck this rat race. -[info] Heatr!albr0014@gold2.tc.umn.edu has joined #bdsm - tippy i want to leave :) - Hobit: Catch you on the flip side Sir. :) - ironic hu -/privmsg #bdsm :colorado is a rat race? - NJ: I do well but I *know I would be a lot happier in the west with my family. - vhf: NJ is a rat race. - see ya nixxie - tippy UG.. well now i dont want to go t oNJ. - hello all - Avante: why do you want to leave? - bye nixxie - not alot going on.. - bye bye people -[info] nixxie has left #bdsm - I have totravel to denver for fun. - is everyone occupied? - bye bye all. I am going to run. -[info] garner!VT102@AC.Dal.Ca has joined #bdsm - hehe - bye hobit - is there a netsplit tonite? - not here - hi all BTW :) -[info] Hobit stopped wasting time: Leaving - netsplits aren't planned, and usually last less than a minute... - i know...... -/privmsg #bdsm :then why do you live at grand junction? - 22, single white female - shesh - Avante: my dream is to climb every 14,000 foot peak in CO. - there may have been a bigger problem.... - we have netsplits all night every night. - hm, - Hi Heatr - heatr cool wwhere do you live? - hello tippy - I am in Minnesota - i fingered an account of someone i know, it says she's on irc, but i can't find her - garner: *.ca was split off just a short while ago - Later. -[info] Sonya stopped wasting time: Leaving - oh really? - maybe that's it - are you bi heatr? -/privmsg #bdsm :some fingers seem to lie about who/what is going on - garner...use /who -host hostname.name.etc.edu -[info] Razormaid has joined #bdsm - ok - i get othing -[info] Chattel stopped wasting time: Leaving - then that person may not be on... -[info] DrDark has joined #bdsm - that's odd... -[info] Auduck has left #bdsm - bbl -[info] garner stopped wasting time: Leaving - (*mew*) - No it isn't -[info] Bri!kaplan@pico.cica.indiana.edu has joined #bdsm - 'lo Bri -[info] TheMaxx!gopher@gopher.csie.nctu.edu.tw has joined #bdsm - Hello. - hi all. -/privmsg avante :pardon my asking, but are you bi? - what's up? -[info] Bri has left #bdsm -[info] spikee has joined #bdsm - lo all -*Avante* well im mostly het.. but i didkiss a guy saturday - Rehi spikee! - Spikee! - re drd *hug* - ah, I see. -[info] Tria!~jackie@brick.purchase.edu has joined #bdsm - sci!!!!!!!!!!!!!!!!!!!!! - hi spike - Hello guys.. - heheh - hello tria - hi Tria. -ACTION DrDark->#bdsm: (*HUGS*) spikee! - 'lo tria... -/privmsg avante :really? cool. d or s? (if this is uncool, it's okay) - Hi there Avante - hello themaxx :) - Hi there Dr.Fark.. - ha ha :) - scigeek call allura now? - hi spikee, tria... -[info] Tria stopped wasting time: Leaving - hi spikee, tria -*Avante* switch.. prefer dom - spikee: She still lonely? - gotta run... -[info] joelll stopped wasting time: Leaving -/privmsg avante :I'm new to this, just checking it out. - yuppers -[info] TheMaxx has left #bdsm -*Avante* who are you? -[info] BlueSonja!~law10118@leonis.nus.sg has joined #bdsm -*Avante* im fairly new - (*sigh*) - hi Blue - 'lo Blue... - Greetings all :) !! -*Avante* im no expert or anything -ACTION BlueSonja->#bdsm: waves to SG and DD -ACTION Prism->#bdsm: snores gently in the background. -/privmsg avante :steve. eissinger, i'm in virginia -ACTION BlueSonja->#bdsm: looks at Prism...sleeping *again* ???! - Aha. He must be awake. - *grin* DD :) -[info] sly!01KLHUFFMA@leo.bsuvc.bsu.edu has joined #bdsm -*Avante* pleased to meet ay steve. :) -ACTION Prism->#bdsm: snores determinedly. - 'lo sly! - haaaaaaaa - (*chuckle*) - hi Sly :) ! - prism: Snore dammit? -[info] sly stopped wasting time: Killed (ircserver.cltr.uq.oz.au (sly[jello.qabc.uq.oz.au] != *.uts.edu.au[unknown@138.25.8.1.3015])) -ACTION BlueSonja->#bdsm: waves to Thorf, Avante, Spikee, Elkor, Neysa2, and all other absent/present people :) - bbl all -[info] Scigeek has left #bdsm - DrDark - absolutely. :-) - where is Less, i wonder... - hi sonya -[info] sly has joined #bdsm -/privmsg avante :how did you get started in the scene? - hi guys -ACTION Prism->#bdsm: snores meaningfully in BlueSonja's direction. -*Avante* im frank -[info] sly stopped wasting time: Killed (ircserver.cltr.uq.oz.au (sly[jello.qabc.uq.oz.au] != *.uts.edu.au[unknown@138.25.8.1.3015])) -ACTION BlueSonja->#bdsm: grins at Avante...*one* person woke up :) - Hiya Blue! -/privmsg avante :hey frank, glad ta meet ya. - bye -ACTION Thorfinn->#bdsm: awakes. - why does sly keep getting killed? - Caught me just in time! :) -[info] Ice9 has left #bdsm -ACTION BlueSonja->#bdsm: *snorts* meaningfully in Prism's direction -*Avante* interestingly enough thru irc -ACTION Thorfinn->#bdsm: hugs Blue. - Prism: was just wondering that myself... -[info] Sonya has joined #bdsm - blue heh - heeeeee Thorf!! *grin* *HUGS* - Hello all. - Rehi Sonya1 -[info] sly!#01KLHUFFM@leo.bsuvc.bsu.edu has joined #bdsm - hi guys i'm back - hi Sonya :) -*Avante* no .. no luck there. - re Sly :) back from the dead :) - re, sly. - sly: For real this time? - Avante : *grin* -*Avante* im trying -ACTION Thorfinn->#bdsm: smiles. - yah..hopefully - sly: (*chuckle*) -ACTION BlueSonja->#bdsm: gives Thorf a nice stalk of rose :) -[info] Garner has joined #bdsm - HI Sonya. - back :) - Err, BlueSonja. - hi garner -ACTION Prism->#bdsm: turns over and goes back to sleep. -[info] Heatr has left #bdsm - heee Sonya :) - hi avante -[info] lou has left #bdsm -ACTION Prism->#bdsm: snores gently in the background. -ACTION Garner->#bdsm: sighs - sleep well prism *snicker* -[info] wetknight!mundv@uxa.ecn.bgu.edu has joined #bdsm -[info] Bananaman!SHELL@DRYCAS.CLUB.CC.CMU.EDU has joined #bdsm - 'lo wk... - 'lo BMan! - hello DD -ACTION Thorfinn->#bdsm: smiles at Blue. - Thanks! - hi WK, BMan :) - hi wetknight -ACTION BlueSonja->#bdsm: bows to Thorf - Hello folks - salutations to all - Does vhf have a long ariel? -/privmsg #bdsm :? - vhf: penis joke, I think... - Gee.. The person I was wanting to go out to dinner with tonight just told me to order pizza. - haaa - and then wait patiently. - poor Prism! *patpat* - prism: brutal -ACTION Thorfinn->#bdsm: cuddles up to Blue. - Prism: Wow... - hey bananman have you talked with pickle yet--tonite - tell that person to stick it BlueSonja - aww prism -ACTION Prism->#bdsm: bursts into tears. - Prism: Hope it's worth the wait... -ACTION BlueSonja->#bdsm: hugs Thorfinn :) -ACTION spikee->#bdsm: gives prism her hanki - *wands her Lady* - No, sly, why? - Panki whois sonya -{Panki#bdsm} ==== Sonya is the cute, cuddly adorable uppity bottom of Lady Penelope. But watch out, she is a master of the Force. ==== -[info] Garner has left #bdsm - Wetknight: huh? who? stick what? where? *grinZ* - bluesonja hehe - heheh cute sonya -[info] LocalHero!wayne@146.116.1.5 has joined #bdsm -[info] LocalHero has changed nick to Wayne - hello lh! - BlueSonja :) - hi - *grin* - 'lo Wayne.. - Greetings my friend - Sonya: nice! :) -ACTION Prism->#bdsm: thanks spikee,wipes his eyes and blows his nose. - back...front - *HONK* - hey Wayne! :) -ACTION Wayne->#bdsm: pokes Sonja in the ribs - Neys!!! - hello heatr -ACTION Wayne->#bdsm: giggles quietly -ACTION spikee->#bdsm: hugs prism - hey everyone -ACTION BlueSonja->#bdsm: hugs Neys - Hi Wayne. - better living through pain -ACTION Thorfinn->#bdsm: smiles. -ACTION BlueSonja->#bdsm: giggles at being poked -ACTION Prism->#bdsm: hugs spikee back. -[info] wetknight has left #bdsm -ACTION Wayne->#bdsm: smiles happily ;-b -[info] pep!law33720@leonis.nus.sg has joined #bdsm - hi tria - brb, changing terminals :) - hi pep - hi pep -[info] BlueSonja stopped wasting time: Leaving - Hehe. - hello -[info] Lorry has left #bdsm - ok, who did I misss - - ----------------------------------------------------------------------- - -this faq is copyright (c) 1994 to the piglet way (tm). -you may only modify this if you make it more offensive. diff --git a/xemacs-packages/zenirc/doc/README-OLD b/xemacs-packages/zenirc/doc/README-OLD deleted file mode 100644 index 36f38ea4..00000000 --- a/xemacs-packages/zenirc/doc/README-OLD +++ /dev/null @@ -1,192 +0,0 @@ -ZenIRC 2.0 - Sun Feb 27 12:37:31 MST 1994 - ALPHA2 - -DISCLAIMER: - -THIS IS REALLY OUT OF DATE, THE ONLY REASON IT'S KEPT AROUND IS THAT -IT DOES DESCRIBE SOME THINGS PRETTY GOOD. BEFORE YOU BELIEVE WHAT THIS -FILE SAYS, LOOK AT `zenirc-example.el' AND THE SOURCE. - -KNOWN BUGS: - -See the TODO file. - -KNOWN FEATURES AND INSTRUCTIONS: - -Here is a list of variables you might want to frobnicate in your .emacs or -on the fly: - -zenirc-buffer-name, change the buffer name to something besides "*zenirc*" - -zenirc-IRCSERVER-alist - Association list of port/password/nick info for -each server. - -Zenirc will attempt to connect to each `host' at `port' in turn until a -successful connection is made, using the username `user' (and `password' if -the server requests one). Your nickname is set to the value `nick'. - -The default value of this alist is determined by the value of the -environment variable `IRCSERVER', which should be in the format -`host:port:password:nickname:username'. If more than one host:etc group is -desired, separate each group with any nonzero amount of whitespace composed -of spaces, tabs, and/or newlines. - -The actual data types of the atoms of each association are string (server), -int (port), string (password), string (nickname), string (username). - -zenirc-server - The hostname of the IRC server to which to connect. - -This is initialized to the first server in `zenirc-IRCSERVER-alist' if that -variable is non-`nil', or "irc-2.mit.edu" by default. - -zenirc-servername - The server name of the IRC server current connected to. -(hmm. this should be a setq, I think) - -zenirc-port - The TCP port associated with the irc server specified -by `zenirc-server'. - -If the server initially specified in `zenirc-server' appears in -`zenirc-IRCSERVER-alist', and a port is explicitly associated with that -server, `zenirc-port' is initialized to that port. Otherwise, -`zenirc-port' defaults to 6667. - -zenirc-user-login-name - the username with which you signon IRC. - -This is usually your username on the system as returned by the function -`user-login-name'. However, if the server initially specified in -`zenirc-server' appears in `zenirc-IRCSERVER-alist' and a username is -explicitly associated with that server, `zenirc-user-login-name' is -initialized to that value. - -zenirc-nick - If the server initially specified in `zenirc-server' appears in -`zenirc-IRCSERVER-alist' and a nickname is explicitly associated with that -server, `zenirc-nick' is initialized to that nickname. If this is not the -case but the environment variable `IRCNICK' is set, `zenirc-nick' is -initialized from that. As a last resort, it defaults to the value of the -variable `zenirc-user-login-name'. - -zenirc-name - The name which you use on IRC. -The default is your GECOS information. - -zenirc-password - Connection password for your IRC server. -The default is none. - -zenirc-userinfo - Reply to USERINFO ctcp - -zenirc-mode-map - Sparse keymap for zenirc-mode - -zenirc-ignorance-list - A list of regexps matching annoying -things that should be ignored. - -zenirc-signal-list - A list of regexps matching things that should cause the -user to be notified of them. - -zenirc-beep-on-signal - Set to t if notification of something matching a regexp -in zenirc-signal-list should cause emacs to beep. - -zenirc-send-ctcp-errmsg-on-unknown - Set to t if ZenIRC should reply with an -ERRMSG to unknown CTCP queries. - -zenirc-send-ctcp-errmsg-on-unbalanced - Set to t if ZenIRC should send an -ERRMSG to an unbalanced CTCP query. - -zenirc-verbose-ctcp - Set to t if you want ZenIRC to tell you when it sends -CTCP replies to people who query you. - -zenirc-fingerdata - CTCP FINGER reply data. - -zenirc-source - CTCP SOURCE reply data - -zenirc-text-list - insert note about function to set here - -zenirc-clientinfo-list - association list of CTCP CLIENTINFO help strings. - -zenirc-clientinfo - Help string, showing list of CTCP commands supported. - -zenirc-debug-mainloop, zenirc-debug-ignore, zenirc-debug-signal, -zenirc-debug-ctcp, zenirc-debug-commands zenirc-debug-timer - -debugging flags. If you're using these, then the help file is old news -as you've read the source. - -The client is designed to be extensible and customizable, in the -spirit of ircII. It uses an extended version of the emacs 19 hook -mechanism, dubbed "zenhooks". - -The basic idea behind the zenhook mechanism is that we want to be able to -attach multiple functions to a given hook. Rather than just specifying a -single hook by creating a function with a certain name, instead hooks become -variables which contain a list of functions to be called. You can add a new -function to a hook variable with the function zenirc-add-hook. If you do -something like (zenirc-add-hook 'zenirc-timer-hook 'ruru), it will cause -the function "ruru" to be added to the hook variable, zenirc-timer-hook. - -Hooks are removed from a hook variable with the function -zenirc-delete-hook - ie, (zenirc-delete-hook 'zenirc-timer-hook 'ruru) -would remove ruru from the list of functions to be called when -zenirc-timer-hook is run. - -zenhooks are run with the function zenirc-run-hook. This function, -unlike the emacs 19 hook functions, passes any extra arguments to -zenirc-run-hook to each function in the hook list as it is -run. In addition, if any function sets zenirc-run-next-hook to nil, -then remaining hooks in the hooklist are not called, and -zenirc-run-hook returns immediately. - -For the timer code, zenirc uses a hook variable called -zenirc-timer-hook. This hook is called at most once a minute, and at -least as often as the irc server pings the client. The functions in -zenirc-timer-hook take a single argument, a process, the ZenIRC -process. An example of adding a new function to zenirc-timer-hook is -scripts/zenirc-stamp.el, which implements Kiwi client style timestamps -in the ZenIRC buffer. - -The signal code is called via a hook variable called -zenirc-signal-hook. scripts/zenirc-fancy-signal.el shows an example of -using this hook as well as the variable zenirc-run-next-hook. -zenirc-signal-hook is called with two arguments, the first is the -zenirc process, and the second is a string, the unparsed servermessage -that caused the signal to occur. - -In various places in the IRC protocol, the IRC server sends the client -strings of the form `nick!user@host' where some parts of this are -optional (see the RFC). The zenhook used to format these is -`zenirc-format-nickuserhost-hook', and is called with a single argument, -the string to format. It returns the formatted string. - -To add new commands to ZenIRC, you create zenhooks with names of the -form "zenirc-command-WHATEVER-hook". The hook will be run with -the arguments "proc" and "parsedcmd". The first argument is the zenirc -process, and the second argument is a slightly parsed form of what the -user typed. The "parsedcmd" argument is a list with two elements. The -first is the first word on the line the user typed, and the second is -the rest of the line. For instance, if the user issued the command -"/FOO BAR", then parsedcmd would be set to ("FOO" "BAR"). Commands -used to use the old hook mechanism, but that is now obsolete. - -CTCP is similarly extensible, only the format of the hook variable -names are zenirc-ctcp-query-WHATEVER-hook and -zenirc-ctcp-reply-WHATEVER-hook. A "query" is a CTCP inside a PRIVMSG -server message, and a "reply" is a CTCP inside a NOTICE server -message. These hooks are called with four arguments, the zenirc filter -process, a parsed ctcp message of the form ("CTCP_COMMAND" . -"ARGUMENTS"), the sender of the ctcp, and the reciever of the ctcp. -CTCP used to use the old hook mechanism, but that is now obsolete. - -All server message handling hook variables have names of the form: -zenirc-server-MESSAGE-hook, and take two arguments, the zenirc filter -procedure, and a parsed message, which is an array that looks like -(sender MESSAGE arg1 arg2 ...). If you want to create a handler for a -message that does not currently have a handler, create your own -hook variable with a name of this form that accepts these arguments, and -ZenIRC will call your subroutine whenever it gets that server message. -To override or modify the behavior of a server message that already -has a hook, call zenirc-add-hook to add your subroutine to the hook -variable. You can override by setting zenirc-run-next-hook to nil, and -you can delete your entry in the hook variable with zenirc-delete-hook. - -Some documents that may prove helpful in extending the client are the -RFC protocol specification for IRC and ctcp.doc. these are both included -in this archive. - -Please send any comments, questions, ideas, bugfixes or whatever to -bed@gnu.ai.mit.edu - diff --git a/xemacs-packages/zenirc/doc/RFC1459 b/xemacs-packages/zenirc/doc/RFC1459 deleted file mode 100644 index b32a128b..00000000 --- a/xemacs-packages/zenirc/doc/RFC1459 +++ /dev/null @@ -1,3643 +0,0 @@ - - - - - - -Network Working Group J. Oikarinen -Request for Comments: 1459 D. Reed - May 1993 - - - Internet Relay Chat Protocol - -Status of This Memo - - This memo defines an Experimental Protocol for the Internet - community. Discussion and suggestions for improvement are requested. - Please refer to the current edition of the "IAB Official Protocol - Standards" for the standardization state and status of this protocol. - Distribution of this memo is unlimited. - -Abstract - - The IRC protocol was developed over the last 4 years since it was - first implemented as a means for users on a BBS to chat amongst - themselves. Now it supports a world-wide network of servers and - clients, and is stringing to cope with growth. Over the past 2 years, - the average number of users connected to the main IRC network has - grown by a factor of 10. - - The IRC protocol is a text-based protocol, with the simplest client - being any socket program capable of connecting to the server. - -Table of Contents - - 1. INTRODUCTION ............................................... 4 - 1.1 Servers ................................................ 4 - 1.2 Clients ................................................ 5 - 1.2.1 Operators .......................................... 5 - 1.3 Channels ................................................ 5 - 1.3.1 Channel Operators .................................... 6 - 2. THE IRC SPECIFICATION ....................................... 7 - 2.1 Overview ................................................ 7 - 2.2 Character codes ......................................... 7 - 2.3 Messages ................................................ 7 - 2.3.1 Message format in 'pseudo' BNF .................... 8 - 2.4 Numeric replies ......................................... 10 - 3. IRC Concepts ................................................ 10 - 3.1 One-to-one communication ................................ 10 - 3.2 One-to-many ............................................. 11 - 3.2.1 To a list .......................................... 11 - 3.2.2 To a group (channel) ............................... 11 - 3.2.3 To a host/server mask .............................. 12 - 3.3 One to all .............................................. 12 - - - -Oikarinen & Reed [Page 1] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - 3.3.1 Client to Client ................................... 12 - 3.3.2 Clients to Server .................................. 12 - 3.3.3 Server to Server ................................... 12 - 4. MESSAGE DETAILS ............................................. 13 - 4.1 Connection Registration ................................. 13 - 4.1.1 Password message ................................... 14 - 4.1.2 Nickname message ................................... 14 - 4.1.3 User message ....................................... 15 - 4.1.4 Server message ..................................... 16 - 4.1.5 Operator message ................................... 17 - 4.1.6 Quit message ....................................... 17 - 4.1.7 Server Quit message ................................ 18 - 4.2 Channel operations ...................................... 19 - 4.2.1 Join message ....................................... 19 - 4.2.2 Part message ....................................... 20 - 4.2.3 Mode message ....................................... 21 - 4.2.3.1 Channel modes ................................. 21 - 4.2.3.2 User modes .................................... 22 - 4.2.4 Topic message ...................................... 23 - 4.2.5 Names message ...................................... 24 - 4.2.6 List message ....................................... 24 - 4.2.7 Invite message ..................................... 25 - 4.2.8 Kick message ....................................... 25 - 4.3 Server queries and commands ............................. 26 - 4.3.1 Version message .................................... 26 - 4.3.2 Stats message ...................................... 27 - 4.3.3 Links message ...................................... 28 - 4.3.4 Time message ....................................... 29 - 4.3.5 Connect message .................................... 29 - 4.3.6 Trace message ...................................... 30 - 4.3.7 Admin message ...................................... 31 - 4.3.8 Info message ....................................... 31 - 4.4 Sending messages ........................................ 32 - 4.4.1 Private messages ................................... 32 - 4.4.2 Notice messages .................................... 33 - 4.5 User-based queries ...................................... 33 - 4.5.1 Who query .......................................... 33 - 4.5.2 Whois query ........................................ 34 - 4.5.3 Whowas message ..................................... 35 - 4.6 Miscellaneous messages .................................. 35 - 4.6.1 Kill message ....................................... 36 - 4.6.2 Ping message ....................................... 37 - 4.6.3 Pong message ....................................... 37 - 4.6.4 Error message ...................................... 38 - 5. OPTIONAL MESSAGES ........................................... 38 - 5.1 Away message ............................................ 38 - 5.2 Rehash command .......................................... 39 - 5.3 Restart command ......................................... 39 - - - -Oikarinen & Reed [Page 2] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - 5.4 Summon message .......................................... 40 - 5.5 Users message ........................................... 40 - 5.6 Operwall command ........................................ 41 - 5.7 Userhost message ........................................ 42 - 5.8 Ison message ............................................ 42 - 6. REPLIES ..................................................... 43 - 6.1 Error Replies ........................................... 43 - 6.2 Command responses ....................................... 48 - 6.3 Reserved numerics ....................................... 56 - 7. Client and server authentication ............................ 56 - 8. Current Implementations Details ............................. 56 - 8.1 Network protocol: TCP ................................... 57 - 8.1.1 Support of Unix sockets ............................ 57 - 8.2 Command Parsing ......................................... 57 - 8.3 Message delivery ........................................ 57 - 8.4 Connection 'Liveness' ................................... 58 - 8.5 Establishing a server-client connection ................. 58 - 8.6 Establishing a server-server connection ................. 58 - 8.6.1 State information exchange when connecting ......... 59 - 8.7 Terminating server-client connections ................... 59 - 8.8 Terminating server-server connections ................... 59 - 8.9 Tracking nickname changes ............................... 60 - 8.10 Flood control of clients ............................... 60 - 8.11 Non-blocking lookups ................................... 61 - 8.11.1 Hostname (DNS) lookups ............................ 61 - 8.11.2 Username (Ident) lookups .......................... 61 - 8.12 Configuration file ..................................... 61 - 8.12.1 Allowing clients to connect ....................... 62 - 8.12.2 Operators ......................................... 62 - 8.12.3 Allowing servers to connect ....................... 62 - 8.12.4 Administrivia ..................................... 63 - 8.13 Channel membership ..................................... 63 - 9. Current problems ............................................ 63 - 9.1 Scalability ............................................. 63 - 9.2 Labels .................................................. 63 - 9.2.1 Nicknames .......................................... 63 - 9.2.2 Channels ........................................... 64 - 9.2.3 Servers ............................................ 64 - 9.3 Algorithms .............................................. 64 - 10. Support and availability ................................... 64 - 11. Security Considerations .................................... 65 - 12. Authors' Addresses ......................................... 65 - - - - - - - - - -Oikarinen & Reed [Page 3] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -1. INTRODUCTION - - The IRC (Internet Relay Chat) protocol has been designed over a - number of years for use with text based conferencing. This document - describes the current IRC protocol. - - The IRC protocol has been developed on systems using the TCP/IP - network protocol, although there is no requirement that this remain - the only sphere in which it operates. - - IRC itself is a teleconferencing system, which (through the use of - the client-server model) is well-suited to running on many machines - in a distributed fashion. A typical setup involves a single process - (the server) forming a central point for clients (or other servers) - to connect to, performing the required message delivery/multiplexing - and other functions. - -1.1 Servers - - The server forms the backbone of IRC, providing a point to which - clients may connect to to talk to each other, and a point for other - servers to connect to, forming an IRC network. The only network - configuration allowed for IRC servers is that of a spanning tree [see - Fig. 1] where each server acts as a central node for the rest of the - net it sees. - - - [ Server 15 ] [ Server 13 ] [ Server 14] - / \ / - / \ / - [ Server 11 ] ------ [ Server 1 ] [ Server 12] - / \ / - / \ / - [ Server 2 ] [ Server 3 ] - / \ \ - / \ \ - [ Server 4 ] [ Server 5 ] [ Server 6 ] - / | \ / - / | \ / - / | \____ / - / | \ / - [ Server 7 ] [ Server 8 ] [ Server 9 ] [ Server 10 ] - - : - [ etc. ] - : - - [ Fig. 1. Format of IRC server network ] - - - -Oikarinen & Reed [Page 4] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -1.2 Clients - - A client is anything connecting to a server that is not another - server. Each client is distinguished from other clients by a unique - nickname having a maximum length of nine (9) characters. See the - protocol grammar rules for what may and may not be used in a - nickname. In addition to the nickname, all servers must have the - following information about all clients: the real name of the host - that the client is running on, the username of the client on that - host, and the server to which the client is connected. - -1.2.1 Operators - - To allow a reasonable amount of order to be kept within the IRC - network, a special class of clients (operators) is allowed to perform - general maintenance functions on the network. Although the powers - granted to an operator can be considered as 'dangerous', they are - nonetheless required. Operators should be able to perform basic - network tasks such as disconnecting and reconnecting servers as - needed to prevent long-term use of bad network routing. In - recognition of this need, the protocol discussed herein provides for - operators only to be able to perform such functions. See sections - 4.1.7 (SQUIT) and 4.3.5 (CONNECT). - - A more controversial power of operators is the ability to remove a - user from the connected network by 'force', i.e. operators are able - to close the connection between any client and server. The - justification for this is delicate since its abuse is both - destructive and annoying. For further details on this type of - action, see section 4.6.1 (KILL). - -1.3 Channels - - A channel is a named group of one or more clients which will all - receive messages addressed to that channel. The channel is created - implicitly when the first client joins it, and the channel ceases to - exist when the last client leaves it. While channel exists, any - client can reference the channel using the name of the channel. - - Channels names are strings (beginning with a '&' or '#' character) of - length up to 200 characters. Apart from the the requirement that the - first character being either '&' or '#'; the only restriction on a - channel name is that it may not contain any spaces (' '), a control G - (^G or ASCII 7), or a comma (',' which is used as a list item - separator by the protocol). - - There are two types of channels allowed by this protocol. One is a - distributed channel which is known to all the servers that are - - - -Oikarinen & Reed [Page 5] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - connected to the network. These channels are marked by the first - character being a only clients on the server where it exists may join - it. These are distinguished by a leading '&' character. On top of - these two types, there are the various channel modes available to - alter the characteristics of individual channels. See section 4.2.3 - (MODE command) for more details on this. - - To create a new channel or become part of an existing channel, a user - is required to JOIN the channel. If the channel doesn't exist prior - to joining, the channel is created and the creating user becomes a - channel operator. If the channel already exists, whether or not your - request to JOIN that channel is honoured depends on the current modes - of the channel. For example, if the channel is invite-only, (+i), - then you may only join if invited. As part of the protocol, a user - may be a part of several channels at once, but a limit of ten (10) - channels is recommended as being ample for both experienced and - novice users. See section 8.13 for more information on this. - - If the IRC network becomes disjoint because of a split between two - servers, the channel on each side is only composed of those clients - which are connected to servers on the respective sides of the split, - possibly ceasing to exist on one side of the split. When the split - is healed, the connecting servers announce to each other who they - think is in each channel and the mode of that channel. If the - channel exists on both sides, the JOINs and MODEs are interpreted in - an inclusive manner so that both sides of the new connection will - agree about which clients are in the channel and what modes the - channel has. - -1.3.1 Channel Operators - - The channel operator (also referred to as a "chop" or "chanop") on a - given channel is considered to 'own' that channel. In recognition of - this status, channel operators are endowed with certain powers which - enable them to keep control and some sort of sanity in their channel. - As an owner of a channel, a channel operator is not required to have - reasons for their actions, although if their actions are generally - antisocial or otherwise abusive, it might be reasonable to ask an IRC - operator to intervene, or for the usersjust leave and go elsewhere - and form their own channel. - - The commands which may only be used by channel operators are: - - KICK - Eject a client from the channel - MODE - Change the channel's mode - INVITE - Invite a client to an invite-only channel (mode +i) - TOPIC - Change the channel topic in a mode +t channel - - - - -Oikarinen & Reed [Page 6] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - A channel operator is identified by the '@' symbol next to their - nickname whenever it is associated with a channel (ie replies to the - NAMES, WHO and WHOIS commands). - -2. The IRC Specification - -2.1 Overview - - The protocol as described herein is for use both with server to - server and client to server connections. There are, however, more - restrictions on client connections (which are considered to be - untrustworthy) than on server connections. - -2.2 Character codes - - No specific character set is specified. The protocol is based on a a - set of codes which are composed of eight (8) bits, making up an - octet. Each message may be composed of any number of these octets; - however, some octet values are used for control codes which act as - message delimiters. - - Regardless of being an 8-bit protocol, the delimiters and keywords - are such that protocol is mostly usable from USASCII terminal and a - telnet connection. - - Because of IRC's scandanavian origin, the characters {}| are - considered to be the lower case equivalents of the characters []\, - respectively. This is a critical issue when determining the - equivalence of two nicknames. - -2.3 Messages - - Servers and clients send eachother messages which may or may not - generate a reply. If the message contains a valid command, as - described in later sections, the client should expect a reply as - specified but it is not advised to wait forever for the reply; client - to server and server to server communication is essentially - asynchronous in nature. - - Each IRC message may consist of up to three main parts: the prefix - (optional), the command, and the command parameters (of which there - may be up to 15). The prefix, command, and all parameters are - separated by one (or more) ASCII space character(s) (0x20). - - The presence of a prefix is indicated with a single leading ASCII - colon character (':', 0x3b), which must be the first character of the - message itself. There must be no gap (whitespace) between the colon - and the prefix. The prefix is used by servers to indicate the true - - - -Oikarinen & Reed [Page 7] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - origin of the message. If the prefix is missing from the message, it - is assumed to have originated from the connection from which it was - received. Clients should not use prefix when sending a message from - themselves; if they use a prefix, the only valid prefix is the - registered nickname associated with the client. If the source - identified by the prefix cannot be found from the server's internal - database, or if the source is registered from a different link than - from which the message arrived, the server must ignore the message - silently. - - The command must either be a valid IRC command or a three (3) digit - number represented in ASCII text. - - IRC messages are always lines of characters terminated with a CR-LF - (Carriage Return - Line Feed) pair, and these messages shall not - exceed 512 characters in length, counting all characters including - the trailing CR-LF. Thus, there are 510 characters maximum allowed - for the command and its parameters. There is no provision for - continuation message lines. See section 7 for more details about - current implementations. - -2.3.1 Message format in 'pseudo' BNF - - The protocol messages must be extracted from the contiguous stream of - octets. The current solution is to designate two characters, CR and - LF, as message separators. Empty messages are silently ignored, - which permits use of the sequence CR-LF between messages - without extra problems. - - The extracted message is parsed into the components , - and list of parameters matched either by or - components. - - The BNF representation for this is: - - - ::= [':' ] - ::= | [ '!' ] [ '@' ] - ::= { } | - ::= ' ' { ' ' } - ::= [ ':' | ] - - ::= - ::= - - ::= CR LF - - - -Oikarinen & Reed [Page 8] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -NOTES: - - 1) is consists only of SPACE character(s) (0x20). - Specially notice that TABULATION, and all other control - characters are considered NON-WHITE-SPACE. - - 2) After extracting the parameter list, all parameters are equal, - whether matched by or . is just - a syntactic trick to allow SPACE within parameter. - - 3) The fact that CR and LF cannot appear in parameter strings is - just artifact of the message framing. This might change later. - - 4) The NUL character is not special in message framing, and - basically could end up inside a parameter, but as it would - cause extra complexities in normal C string handling. Therefore - NUL is not allowed within messages. - - 5) The last parameter may be an empty string. - - 6) Use of the extended prefix (['!' ] ['@' ]) must - not be used in server to server communications and is only - intended for server to client messages in order to provide - clients with more useful information about who a message is - from without the need for additional queries. - - Most protocol messages specify additional semantics and syntax for - the extracted parameter strings dictated by their position in the - list. For example, many server commands will assume that the first - parameter after the command is the list of targets, which can be - described with: - - ::= [ "," ] - ::= | '@' | | - ::= ('#' | '&') - ::= - ::= see RFC 952 [DNS:4] for details on allowed hostnames - ::= { | | } - ::= ('#' | '$') - ::= - - Other parameter syntaxes are: - - ::= { } - ::= 'a' ... 'z' | 'A' ... 'Z' - ::= '0' ... '9' - ::= '-' | '[' | ']' | '\' | '`' | '^' | '{' | '}' - - - -Oikarinen & Reed [Page 9] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - ::= - -2.4 Numeric replies - - Most of the messages sent to the server generate a reply of some - sort. The most common reply is the numeric reply, used for both - errors and normal replies. The numeric reply must be sent as one - message consisting of the sender prefix, the three digit numeric, and - the target of the reply. A numeric reply is not allowed to originate - from a client; any such messages received by a server are silently - dropped. In all other respects, a numeric reply is just like a normal - message, except that the keyword is made up of 3 numeric digits - rather than a string of letters. A list of different replies is - supplied in section 6. - -3. IRC Concepts. - - This section is devoted to describing the actual concepts behind the - organization of the IRC protocol and how the current - implementations deliver different classes of messages. - - - - 1--\ - A D---4 - 2--/ \ / - B----C - / \ - 3 E - - Servers: A, B, C, D, E Clients: 1, 2, 3, 4 - - [ Fig. 2. Sample small IRC network ] - -3.1 One-to-one communication - - Communication on a one-to-one basis is usually only performed by - clients, since most server-server traffic is not a result of servers - talking only to each other. To provide a secure means for clients to - talk to each other, it is required that all servers be able to send a - message in exactly one direction along the spanning tree in order to - reach any client. The path of a message being delivered is the - shortest path between any two points on the spanning tree. - - The following examples all refer to Figure 2 above. - - - - - -Oikarinen & Reed [Page 10] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -Example 1: - A message between clients 1 and 2 is only seen by server A, which - sends it straight to client 2. - -Example 2: - A message between clients 1 and 3 is seen by servers A & B, and - client 3. No other clients or servers are allowed see the message. - -Example 3: - A message between clients 2 and 4 is seen by servers A, B, C & D - and client 4 only. - -3.2 One-to-many - - The main goal of IRC is to provide a forum which allows easy and - efficient conferencing (one to many conversations). IRC offers - several means to achieve this, each serving its own purpose. - -3.2.1 To a list - - The least efficient style of one-to-many conversation is through - clients talking to a 'list' of users. How this is done is almost - self explanatory: the client gives a list of destinations to which - the message is to be delivered and the server breaks it up and - dispatches a separate copy of the message to each given destination. - This isn't as efficient as using a group since the destination list - is broken up and the dispatch sent without checking to make sure - duplicates aren't sent down each path. - -3.2.2 To a group (channel) - - In IRC the channel has a role equivalent to that of the multicast - group; their existence is dynamic (coming and going as people join - and leave channels) and the actual conversation carried out on a - channel is only sent to servers which are supporting users on a given - channel. If there are multiple users on a server in the same - channel, the message text is sent only once to that server and then - sent to each client on the channel. This action is then repeated for - each client-server combination until the original message has fanned - out and reached each member of the channel. - - The following examples all refer to Figure 2. - -Example 4: - Any channel with 1 client in it. Messages to the channel go to the - server and then nowhere else. - - - - - -Oikarinen & Reed [Page 11] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -Example 5: - 2 clients in a channel. All messages traverse a path as if they - were private messages between the two clients outside a channel. - -Example 6: - Clients 1, 2 and 3 in a channel. All messages to the channel are - sent to all clients and only those servers which must be traversed - by the message if it were a private message to a single client. If - client 1 sends a message, it goes back to client 2 and then via - server B to client 3. - -3.2.3 To a host/server mask - - To provide IRC operators with some mechanism to send messages to a - large body of related users, host and server mask messages are - provided. These messages are sent to users whose host or server - information match that of the mask. The messages are only sent to - locations where users are, in a fashion similar to that of channels. - -3.3 One-to-all - - The one-to-all type of message is better described as a broadcast - message, sent to all clients or servers or both. On a large network - of users and servers, a single message can result in a lot of traffic - being sent over the network in an effort to reach all of the desired - destinations. - - For some messages, there is no option but to broadcast it to all - servers so that the state information held by each server is - reasonably consistent between servers. - -3.3.1 Client-to-Client - - There is no class of message which, from a single message, results in - a message being sent to every other client. - -3.3.2 Client-to-Server - - Most of the commands which result in a change of state information - (such as channel membership, channel mode, user status, etc) must be - sent to all servers by default, and this distribution may not be - changed by the client. - -3.3.3 Server-to-Server. - - While most messages between servers are distributed to all 'other' - servers, this is only required for any message that affects either a - user, channel or server. Since these are the basic items found in - - - -Oikarinen & Reed [Page 12] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - IRC, nearly all messages originating from a server are broadcast to - all other connected servers. - -4. Message details - - On the following pages are descriptions of each message recognized by - the IRC server and client. All commands described in this section - must be implemented by any server for this protocol. - - Where the reply ERR_NOSUCHSERVER is listed, it means that the - parameter could not be found. The server must not send any - other replies after this for that command. - - The server to which a client is connected is required to parse the - complete message, returning any appropriate errors. If the server - encounters a fatal error while parsing a message, an error must be - sent back to the client and the parsing terminated. A fatal error - may be considered to be incorrect command, a destination which is - otherwise unknown to the server (server, nick or channel names fit - this category), not enough parameters or incorrect privileges. - - If a full set of parameters is presented, then each must be checked - for validity and appropriate responses sent back to the client. In - the case of messages which use parameter lists using the comma as an - item separator, a reply must be sent for each item. - - In the examples below, some messages appear using the full format: - - :Name COMMAND parameter list - - Such examples represent a message from "Name" in transit between - servers, where it is essential to include the name of the original - sender of the message so remote servers may send back a reply along - the correct path. - -4.1 Connection Registration - - The commands described here are used to register a connection with an - IRC server as either a user or a server as well as correctly - disconnect. - - A "PASS" command is not required for either client or server - connection to be registered, but it must precede the server message - or the latter of the NICK/USER combination. It is strongly - recommended that all server connections have a password in order to - give some level of security to the actual connections. The - recommended order for a client to register is as follows: - - - - -Oikarinen & Reed [Page 13] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - 1. Pass message - 2. Nick message - 3. User message - -4.1.1 Password message - - - Command: PASS - Parameters: - - The PASS command is used to set a 'connection password'. The - password can and must be set before any attempt to register the - connection is made. Currently this requires that clients send a PASS - command before sending the NICK/USER combination and servers *must* - send a PASS command before any SERVER command. The password supplied - must match the one contained in the C/N lines (for servers) or I - lines (for clients). It is possible to send multiple PASS commands - before registering but only the last one sent is used for - verification and it may not be changed once registered. Numeric - Replies: - - ERR_NEEDMOREPARAMS ERR_ALREADYREGISTRED - - Example: - - PASS secretpasswordhere - -4.1.2 Nick message - - Command: NICK - Parameters: [ ] - - NICK message is used to give user a nickname or change the previous - one. The parameter is only used by servers to indicate - how far away a nick is from its home server. A local connection has - a hopcount of 0. If supplied by a client, it must be ignored. - - If a NICK message arrives at a server which already knows about an - identical nickname for another client, a nickname collision occurs. - As a result of a nickname collision, all instances of the nickname - are removed from the server's database, and a KILL command is issued - to remove the nickname from all other server's database. If the NICK - message causing the collision was a nickname change, then the - original (old) nick must be removed as well. - - If the server recieves an identical NICK from a client which is - directly connected, it may issue an ERR_NICKCOLLISION to the local - client, drop the NICK command, and not generate any kills. - - - -Oikarinen & Reed [Page 14] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - Numeric Replies: - - ERR_NONICKNAMEGIVEN ERR_ERRONEUSNICKNAME - ERR_NICKNAMEINUSE ERR_NICKCOLLISION - - Example: - - NICK Wiz ; Introducing new nick "Wiz". - - :WiZ NICK Kilroy ; WiZ changed his nickname to Kilroy. - -4.1.3 User message - - Command: USER - Parameters: - - The USER message is used at the beginning of connection to specify - the username, hostname, servername and realname of s new user. It is - also used in communication between servers to indicate new user - arriving on IRC, since only after both USER and NICK have been - received from a client does a user become registered. - - Between servers USER must to be prefixed with client's NICKname. - Note that hostname and servername are normally ignored by the IRC - server when the USER command comes from a directly connected client - (for security reasons), but they are used in server to server - communication. This means that a NICK must always be sent to a - remote server when a new user is being introduced to the rest of the - network before the accompanying USER is sent. - - It must be noted that realname parameter must be the last parameter, - because it may contain space characters and must be prefixed with a - colon (':') to make sure this is recognised as such. - - Since it is easy for a client to lie about its username by relying - solely on the USER message, the use of an "Identity Server" is - recommended. If the host which a user connects from has such a - server enabled the username is set to that as in the reply from the - "Identity Server". - - Numeric Replies: - - ERR_NEEDMOREPARAMS ERR_ALREADYREGISTRED - - Examples: - - - USER guest tolmoon tolsun :Ronnie Reagan - - - -Oikarinen & Reed [Page 15] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - ; User registering themselves with a - username of "guest" and real name - "Ronnie Reagan". - - - :testnick USER guest tolmoon tolsun :Ronnie Reagan - ; message between servers with the - nickname for which the USER command - belongs to - -4.1.4 Server message - - Command: SERVER - Parameters: - - The server message is used to tell a server that the other end of a - new connection is a server. This message is also used to pass server - data over whole net. When a new server is connected to net, - information about it be broadcast to the whole network. - is used to give all servers some internal information on how far away - all servers are. With a full server list, it would be possible to - construct a map of the entire server tree, but hostmasks prevent this - from being done. - - The SERVER message must only be accepted from either (a) a connection - which is yet to be registered and is attempting to register as a - server, or (b) an existing connection to another server, in which - case the SERVER message is introducing a new server behind that - server. - - Most errors that occur with the receipt of a SERVER command result in - the connection being terminated by the destination host (target - SERVER). Error replies are usually sent using the "ERROR" command - rather than the numeric since the ERROR command has several useful - properties which make it useful here. - - If a SERVER message is parsed and attempts to introduce a server - which is already known to the receiving server, the connection from - which that message must be closed (following the correct procedures), - since a duplicate route to a server has formed and the acyclic nature - of the IRC tree broken. - - Numeric Replies: - - ERR_ALREADYREGISTRED - - Example: - - - - -Oikarinen & Reed [Page 16] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -SERVER test.oulu.fi 1 :[tolsun.oulu.fi] Experimental server - ; New server test.oulu.fi introducing - itself and attempting to register. The - name in []'s is the hostname for the - host running test.oulu.fi. - - -:tolsun.oulu.fi SERVER csd.bu.edu 5 :BU Central Server - ; Server tolsun.oulu.fi is our uplink - for csd.bu.edu which is 5 hops away. - -4.1.5 Oper - - Command: OPER - Parameters: - - OPER message is used by a normal user to obtain operator privileges. - The combination of and are required to gain - Operator privileges. - - If the client sending the OPER command supplies the correct password - for the given user, the server then informs the rest of the network - of the new operator by issuing a "MODE +o" for the clients nickname. - - The OPER message is client-server only. - - Numeric Replies: - - ERR_NEEDMOREPARAMS RPL_YOUREOPER - ERR_NOOPERHOST ERR_PASSWDMISMATCH - - Example: - - OPER foo bar ; Attempt to register as an operator - using a username of "foo" and "bar" as - the password. - -4.1.6 Quit - - Command: QUIT - Parameters: [] - - A client session is ended with a quit message. The server must close - the connection to a client which sends a QUIT message. If a "Quit - Message" is given, this will be sent instead of the default message, - the nickname. - - When netsplits (disconnecting of two servers) occur, the quit message - - - -Oikarinen & Reed [Page 17] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - is composed of the names of two servers involved, separated by a - space. The first name is that of the server which is still connected - and the second name is that of the server that has become - disconnected. - - If, for some other reason, a client connection is closed without the - client issuing a QUIT command (e.g. client dies and EOF occurs - on socket), the server is required to fill in the quit message with - some sort of message reflecting the nature of the event which - caused it to happen. - - Numeric Replies: - - None. - - Examples: - - QUIT :Gone to have lunch ; Preferred message format. - -4.1.7 Server quit message - - Command: SQUIT - Parameters: - - The SQUIT message is needed to tell about quitting or dead servers. - If a server wishes to break the connection to another server it must - send a SQUIT message to the other server, using the the name of the - other server as the server parameter, which then closes its - connection to the quitting server. - - This command is also available operators to help keep a network of - IRC servers connected in an orderly fashion. Operators may also - issue an SQUIT message for a remote server connection. In this case, - the SQUIT must be parsed by each server inbetween the operator and - the remote server, updating the view of the network held by each - server as explained below. - - The should be supplied by all operators who execute a SQUIT - for a remote server (that is not connected to the server they are - currently on) so that other operators are aware for the reason of - this action. The is also filled in by servers which may - place an error or similar message here. - - Both of the servers which are on either side of the connection being - closed are required to to send out a SQUIT message (to all its other - server connections) for all other servers which are considered to be - behind that link. - - - - -Oikarinen & Reed [Page 18] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - Similarly, a QUIT message must be sent to the other connected servers - rest of the network on behalf of all clients behind that link. In - addition to this, all channel members of a channel which lost a - member due to the split must be sent a QUIT message. - - If a server connection is terminated prematurely (e.g. the server on - the other end of the link died), the server which detects - this disconnection is required to inform the rest of the network - that the connection has closed and fill in the comment field - with something appropriate. - - Numeric replies: - - ERR_NOPRIVILEGES ERR_NOSUCHSERVER - - Example: - - SQUIT tolsun.oulu.fi :Bad Link ? ; the server link tolson.oulu.fi has - been terminated because of "Bad Link". - - :Trillian SQUIT cm22.eng.umd.edu :Server out of control - ; message from Trillian to disconnect - "cm22.eng.umd.edu" from the net - because "Server out of control". - -4.2 Channel operations - - This group of messages is concerned with manipulating channels, their - properties (channel modes), and their contents (typically clients). - In implementing these, a number of race conditions are inevitable - when clients at opposing ends of a network send commands which will - ultimately clash. It is also required that servers keep a nickname - history to ensure that wherever a parameter is given, the - server check its history in case it has recently been changed. - -4.2.1 Join message - - Command: JOIN - Parameters: {,} [{,}] - - The JOIN command is used by client to start listening a specific - channel. Whether or not a client is allowed to join a channel is - checked only by the server the client is connected to; all other - servers automatically add the user to the channel when it is received - from other servers. The conditions which affect this are as follows: - - 1. the user must be invited if the channel is invite-only; - - - - -Oikarinen & Reed [Page 19] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - 2. the user's nick/username/hostname must not match any - active bans; - - 3. the correct key (password) must be given if it is set. - - These are discussed in more detail under the MODE command (see - section 4.2.3 for more details). - - Once a user has joined a channel, they receive notice about all - commands their server receives which affect the channel. This - includes MODE, KICK, PART, QUIT and of course PRIVMSG/NOTICE. The - JOIN command needs to be broadcast to all servers so that each server - knows where to find the users who are on the channel. This allows - optimal delivery of PRIVMSG/NOTICE messages to the channel. - - If a JOIN is successful, the user is then sent the channel's topic - (using RPL_TOPIC) and the list of users who are on the channel (using - RPL_NAMREPLY), which must include the user joining. - - Numeric Replies: - - ERR_NEEDMOREPARAMS ERR_BANNEDFROMCHAN - ERR_INVITEONLYCHAN ERR_BADCHANNELKEY - ERR_CHANNELISFULL ERR_BADCHANMASK - ERR_NOSUCHCHANNEL ERR_TOOMANYCHANNELS - RPL_TOPIC - - Examples: - - JOIN #foobar ; join channel #foobar. - - JOIN &foo fubar ; join channel &foo using key "fubar". - - JOIN #foo,&bar fubar ; join channel #foo using key "fubar" - and &bar using no key. - - JOIN #foo,#bar fubar,foobar ; join channel #foo using key "fubar". - and channel #bar using key "foobar". - - JOIN #foo,#bar ; join channels #foo and #bar. - - :WiZ JOIN #Twilight_zone ; JOIN message from WiZ - -4.2.2 Part message - - Command: PART - Parameters: {,} - - - - -Oikarinen & Reed [Page 20] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - The PART message causes the client sending the message to be removed - from the list of active users for all given channels listed in the - parameter string. - - Numeric Replies: - - ERR_NEEDMOREPARAMS ERR_NOSUCHCHANNEL - ERR_NOTONCHANNEL - - Examples: - - PART #twilight_zone ; leave channel "#twilight_zone" - - PART #oz-ops,&group5 ; leave both channels "&group5" and - "#oz-ops". - -4.2.3 Mode message - - Command: MODE - - The MODE command is a dual-purpose command in IRC. It allows both - usernames and channels to have their mode changed. The rationale for - this choice is that one day nicknames will be obsolete and the - equivalent property will be the channel. - - When parsing MODE messages, it is recommended that the entire message - be parsed first and then the changes which resulted then passed on. - -4.2.3.1 Channel modes - - Parameters: {[+|-]|o|p|s|i|t|n|b|v} [] [] - [] - - The MODE command is provided so that channel operators may change the - characteristics of `their' channel. It is also required that servers - be able to change channel modes so that channel operators may be - created. - - The various modes available for channels are as follows: - - o - give/take channel operator privileges; - p - private channel flag; - s - secret channel flag; - i - invite-only channel flag; - t - topic settable by channel operator only flag; - n - no messages to channel from clients on the outside; - m - moderated channel; - l - set the user limit to channel; - - - -Oikarinen & Reed [Page 21] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - b - set a ban mask to keep users out; - v - give/take the ability to speak on a moderated channel; - k - set a channel key (password). - - When using the 'o' and 'b' options, a restriction on a total of three - per mode command has been imposed. That is, any combination of 'o' - and - -4.2.3.2 User modes - - Parameters: {[+|-]|i|w|s|o} - - The user MODEs are typically changes which affect either how the - client is seen by others or what 'extra' messages the client is sent. - A user MODE command may only be accepted if both the sender of the - message and the nickname given as a parameter are both the same. - - The available modes are as follows: - - i - marks a users as invisible; - s - marks a user for receipt of server notices; - w - user receives wallops; - o - operator flag. - - Additional modes may be available later on. - - If a user attempts to make themselves an operator using the "+o" - flag, the attempt should be ignored. There is no restriction, - however, on anyone `deopping' themselves (using "-o"). Numeric - Replies: - - ERR_NEEDMOREPARAMS RPL_CHANNELMODEIS - ERR_CHANOPRIVSNEEDED ERR_NOSUCHNICK - ERR_NOTONCHANNEL ERR_KEYSET - RPL_BANLIST RPL_ENDOFBANLIST - ERR_UNKNOWNMODE ERR_NOSUCHCHANNEL - - ERR_USERSDONTMATCH RPL_UMODEIS - ERR_UMODEUNKNOWNFLAG - - Examples: - - Use of Channel Modes: - -MODE #Finnish +im ; Makes #Finnish channel moderated and - 'invite-only'. - -MODE #Finnish +o Kilroy ; Gives 'chanop' privileges to Kilroy on - - - -Oikarinen & Reed [Page 22] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - channel #Finnish. - -MODE #Finnish +v Wiz ; Allow WiZ to speak on #Finnish. - -MODE #Fins -s ; Removes 'secret' flag from channel - #Fins. - -MODE #42 +k oulu ; Set the channel key to "oulu". - -MODE #eu-opers +l 10 ; Set the limit for the number of users - on channel to 10. - -MODE &oulu +b ; list ban masks set for channel. - -MODE &oulu +b *!*@* ; prevent all users from joining. - -MODE &oulu +b *!*@*.edu ; prevent any user from a hostname - matching *.edu from joining. - - Use of user Modes: - -:MODE WiZ -w ; turns reception of WALLOPS messages - off for WiZ. - -:Angel MODE Angel +i ; Message from Angel to make themselves - invisible. - -MODE WiZ -o ; WiZ 'deopping' (removing operator - status). The plain reverse of this - command ("MODE WiZ +o") must not be - allowed from users since would bypass - the OPER command. - -4.2.4 Topic message - - Command: TOPIC - Parameters: [] - - The TOPIC message is used to change or view the topic of a channel. - The topic for channel is returned if there is no - given. If the parameter is present, the topic for that - channel will be changed, if the channel modes permit this action. - - Numeric Replies: - - ERR_NEEDMOREPARAMS ERR_NOTONCHANNEL - RPL_NOTOPIC RPL_TOPIC - ERR_CHANOPRIVSNEEDED - - - -Oikarinen & Reed [Page 23] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - Examples: - - :Wiz TOPIC #test :New topic ;User Wiz setting the topic. - - TOPIC #test :another topic ;set the topic on #test to "another - topic". - - TOPIC #test ; check the topic for #test. - -4.2.5 Names message - - Command: NAMES - Parameters: [{,}] - - By using the NAMES command, a user can list all nicknames that are - visible to them on any channel that they can see. Channel names - which they can see are those which aren't private (+p) or secret (+s) - or those which they are actually on. The parameter - specifies which channel(s) to return information about if valid. - There is no error reply for bad channel names. - - If no parameter is given, a list of all channels and their - occupants is returned. At the end of this list, a list of users who - are visible but either not on any channel or not on a visible channel - are listed as being on `channel' "*". - - Numerics: - - RPL_NAMREPLY RPL_ENDOFNAMES - - Examples: - - NAMES #twilight_zone,#42 ; list visible users on #twilight_zone - and #42 if the channels are visible to - you. - - NAMES ; list all visible channels and users - -4.2.6 List message - - Command: LIST - Parameters: [{,} []] - - The list message is used to list channels and their topics. If the - parameter is used, only the status of that channel - is displayed. Private channels are listed (without their - topics) as channel "Prv" unless the client generating the query is - actually on that channel. Likewise, secret channels are not listed - - - -Oikarinen & Reed [Page 24] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - at all unless the client is a member of the channel in question. - - Numeric Replies: - - ERR_NOSUCHSERVER RPL_LISTSTART - RPL_LIST RPL_LISTEND - - Examples: - - LIST ; List all channels. - - LIST #twilight_zone,#42 ; List channels #twilight_zone and #42 - -4.2.7 Invite message - - Command: INVITE - Parameters: - - The INVITE message is used to invite users to a channel. The - parameter is the nickname of the person to be invited to - the target channel . There is no requirement that the - channel the target user is being invited to must exist or be a valid - channel. To invite a user to a channel which is invite only (MODE - +i), the client sending the invite must be recognised as being a - channel operator on the given channel. - - Numeric Replies: - - ERR_NEEDMOREPARAMS ERR_NOSUCHNICK - ERR_NOTONCHANNEL ERR_USERONCHANNEL - ERR_CHANOPRIVSNEEDED - RPL_INVITING RPL_AWAY - - Examples: - - :Angel INVITE Wiz #Dust ; User Angel inviting WiZ to channel - #Dust - - INVITE Wiz #Twilight_Zone ; Command to invite WiZ to - #Twilight_zone - -4.2.8 Kick command - - Command: KICK - Parameters: [] - - The KICK command can be used to forcibly remove a user from a - channel. It 'kicks them out' of the channel (forced PART). - - - -Oikarinen & Reed [Page 25] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - Only a channel operator may kick another user out of a channel. - Each server that receives a KICK message checks that it is valid - (ie the sender is actually a channel operator) before removing - the victim from the channel. - - Numeric Replies: - - ERR_NEEDMOREPARAMS ERR_NOSUCHCHANNEL - ERR_BADCHANMASK ERR_CHANOPRIVSNEEDED - ERR_NOTONCHANNEL - - Examples: - -KICK &Melbourne Matthew ; Kick Matthew from &Melbourne - -KICK #Finnish John :Speaking English - ; Kick John from #Finnish using - "Speaking English" as the reason - (comment). - -:WiZ KICK #Finnish John ; KICK message from WiZ to remove John - from channel #Finnish - -NOTE: - It is possible to extend the KICK command parameters to the -following: - -{,} {,} [] - -4.3 Server queries and commands - - The server query group of commands has been designed to return - information about any server which is connected to the network. All - servers connected must respond to these queries and respond - correctly. Any invalid response (or lack thereof) must be considered - a sign of a broken server and it must be disconnected/disabled as - soon as possible until the situation is remedied. - - In these queries, where a parameter appears as "", it will - usually mean it can be a nickname or a server or a wildcard name of - some sort. For each parameter, however, only one query and set of - replies is to be generated. - -4.3.1 Version message - - Command: VERSION - Parameters: [] - - - - -Oikarinen & Reed [Page 26] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - The VERSION message is used to query the version of the server - program. An optional parameter is used to query the version - of the server program which a client is not directly connected to. - - Numeric Replies: - - ERR_NOSUCHSERVER RPL_VERSION - - Examples: - - :Wiz VERSION *.se ; message from Wiz to check the version - of a server matching "*.se" - - VERSION tolsun.oulu.fi ; check the version of server - "tolsun.oulu.fi". - -4.3.2 Stats message - - Command: STATS - Parameters: [ []] - - The stats message is used to query statistics of certain server. If - parameter is omitted, only the end of stats reply is sent - back. The implementation of this command is highly dependent on the - server which replies, although the server must be able to supply - information as described by the queries below (or similar). - - A query may be given by any single letter which is only checked by - the destination server (if given as the parameter) and is - otherwise passed on by intermediate servers, ignored and unaltered. - The following queries are those found in the current IRC - implementation and provide a large portion of the setup information - for that server. Although these may not be supported in the same way - by other versions, all servers should be able to supply a valid reply - to a STATS query which is consistent with the reply formats currently - used and the purpose of the query. - - The currently supported queries are: - - c - returns a list of servers which the server may connect - to or allow connections from; - h - returns a list of servers which are either forced to be - treated as leaves or allowed to act as hubs; - i - returns a list of hosts which the server allows a client - to connect from; - k - returns a list of banned username/hostname combinations - for that server; - l - returns a list of the server's connections, showing how - - - -Oikarinen & Reed [Page 27] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - long each connection has been established and the traffic - over that connection in bytes and messages for each - direction; - m - returns a list of commands supported by the server and - the usage count for each if the usage count is non zero; - o - returns a list of hosts from which normal clients may - become operators; - y - show Y (Class) lines from server's configuration file; - u - returns a string showing how long the server has been up. - - Numeric Replies: - - ERR_NOSUCHSERVER - RPL_STATSCLINE RPL_STATSNLINE - RPL_STATSILINE RPL_STATSKLINE - RPL_STATSQLINE RPL_STATSLLINE - RPL_STATSLINKINFO RPL_STATSUPTIME - RPL_STATSCOMMANDS RPL_STATSOLINE - RPL_STATSHLINE RPL_ENDOFSTATS - - Examples: - -STATS m ; check the command usage for the server - you are connected to - -:Wiz STATS c eff.org ; request by WiZ for C/N line - information from server eff.org - -4.3.3 Links message - - Command: LINKS - Parameters: [[] ] - - With LINKS, a user can list all servers which are known by the server - answering the query. The returned list of servers must match the - mask, or if no mask is given, the full list is returned. - - If is given in addition to , the LINKS - command is forwarded to the first server found that matches that name - (if any), and that server is then required to answer the query. - - Numeric Replies: - - ERR_NOSUCHSERVER - RPL_LINKS RPL_ENDOFLINKS - - Examples: - - - - -Oikarinen & Reed [Page 28] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -LINKS *.au ; list all servers which have a name - that matches *.au; - -:WiZ LINKS *.bu.edu *.edu ; LINKS message from WiZ to the first - server matching *.edu for a list of - servers matching *.bu.edu. - -4.3.4 Time message - - Command: TIME - Parameters: [] - - The time message is used to query local time from the specified - server. If the server parameter is not given, the server handling the - command must reply to the query. - - Numeric Replies: - - ERR_NOSUCHSERVER RPL_TIME - - Examples: - - TIME tolsun.oulu.fi ; check the time on the server - "tolson.oulu.fi" - - Angel TIME *.au ; user angel checking the time on a - server matching "*.au" - -4.3.5 Connect message - - Command: CONNECT - Parameters: [ []] - - The CONNECT command can be used to force a server to try to establish - a new connection to another server immediately. CONNECT is a - privileged command and is to be available only to IRC Operators. If - a remote server is given then the CONNECT attempt is made by that - server to and . - - Numeric Replies: - - ERR_NOSUCHSERVER ERR_NOPRIVILEGES - ERR_NEEDMOREPARAMS - - Examples: - -CONNECT tolsun.oulu.fi ; Attempt to connect a server to - tolsun.oulu.fi - - - -Oikarinen & Reed [Page 29] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -:WiZ CONNECT eff.org 6667 csd.bu.edu - ; CONNECT attempt by WiZ to get servers - eff.org and csd.bu.edu connected on port - 6667. - -4.3.6 Trace message - - Command: TRACE - Parameters: [] - - TRACE command is used to find the route to specific server. Each - server that processes this message must tell the sender about it by - sending a reply indicating it is a pass-through link, forming a chain - of replies similar to that gained from using "traceroute". After - sending this reply back, it must then send the TRACE message to the - next server until given server is reached. If the parameter - is omitted, it is recommended that TRACE command send a message to - the sender telling which servers the current server has direct - connection to. - - If the destination given by "" is an actual server, then the - destination server is required to report all servers and users which - are connected to it, although only operators are permitted to see - users present. If the destination given by is a nickname, - they only a reply for that nickname is given. - - Numeric Replies: - - ERR_NOSUCHSERVER - - If the TRACE message is destined for another server, all intermediate - servers must return a RPL_TRACELINK reply to indicate that the TRACE - passed through it and where its going next. - - RPL_TRACELINK - A TRACE reply may be composed of any number of the following numeric - replies. - - RPL_TRACECONNECTING RPL_TRACEHANDSHAKE - RPL_TRACEUNKNOWN RPL_TRACEOPERATOR - RPL_TRACEUSER RPL_TRACESERVER - RPL_TRACESERVICE RPL_TRACENEWTYPE - RPL_TRACECLASS - - Examples: - -TRACE *.oulu.fi ; TRACE to a server matching *.oulu.fi - - - - -Oikarinen & Reed [Page 30] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -:WiZ TRACE AngelDust ; TRACE issued by WiZ to nick AngelDust - -4.3.7 Admin command - - Command: ADMIN - Parameters: [] - - The admin message is used to find the name of the administrator of - the given server, or current server if parameter is omitted. - Each server must have the ability to forward ADMIN messages to other - servers. - - Numeric Replies: - - ERR_NOSUCHSERVER - RPL_ADMINME RPL_ADMINLOC1 - RPL_ADMINLOC2 RPL_ADMINEMAIL - - Examples: - - ADMIN tolsun.oulu.fi ; request an ADMIN reply from - tolsun.oulu.fi - - :WiZ ADMIN *.edu ; ADMIN request from WiZ for first - server found to match *.edu. - -4.3.8 Info command - - Command: INFO - Parameters: [] - - The INFO command is required to return information which describes - the server: its version, when it was compiled, the patchlevel, when - it was started, and any other miscellaneous information which may be - considered to be relevant. - - Numeric Replies: - - ERR_NOSUCHSERVER - RPL_INFO RPL_ENDOFINFO - - Examples: - - INFO csd.bu.edu ; request an INFO reply from - csd.bu.edu - - :Avalon INFO *.fi ; INFO request from Avalon for first - server found to match *.fi. - - - -Oikarinen & Reed [Page 31] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - INFO Angel ; request info from the server that - Angel is connected to. - -4.4 Sending messages - - The main purpose of the IRC protocol is to provide a base for clients - to communicate with each other. PRIVMSG and NOTICE are the only - messages available which actually perform delivery of a text message - from one client to another - the rest just make it possible and try - to ensure it happens in a reliable and structured manner. - -4.4.1 Private messages - - Command: PRIVMSG - Parameters: {,} - - PRIVMSG is used to send private messages between users. - is the nickname of the receiver of the message. can also - be a list of names or channels separated with commas. - - The parameter may also me a host mask (#mask) or server - mask ($mask). In both cases the server will only send the PRIVMSG - to those who have a server or host matching the mask. The mask must - have at least 1 (one) "." in it and no wildcards following the - last ".". This requirement exists to prevent people sending messages - to "#*" or "$*", which would broadcast to all users; from - experience, this is abused more than used responsibly and properly. - Wildcards are the '*' and '?' characters. This extension to - the PRIVMSG command is only available to Operators. - - Numeric Replies: - - ERR_NORECIPIENT ERR_NOTEXTTOSEND - ERR_CANNOTSENDTOCHAN ERR_NOTOPLEVEL - ERR_WILDTOPLEVEL ERR_TOOMANYTARGETS - ERR_NOSUCHNICK - RPL_AWAY - - Examples: - -:Angel PRIVMSG Wiz :Hello are you receiving this message ? - ; Message from Angel to Wiz. - -PRIVMSG Angel :yes I'm receiving it !receiving it !'u>(768u+1n) .br ; - Message to Angel. - -PRIVMSG jto@tolsun.oulu.fi :Hello ! - ; Message to a client on server - - - -Oikarinen & Reed [Page 32] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - tolsun.oulu.fi with username of "jto". - -PRIVMSG $*.fi :Server tolsun.oulu.fi rebooting. - ; Message to everyone on a server which - has a name matching *.fi. - -PRIVMSG #*.edu :NSFNet is undergoing work, expect interruptions - ; Message to all users who come from a - host which has a name matching *.edu. - -4.4.2 Notice - - Command: NOTICE - Parameters: - - The NOTICE message is used similarly to PRIVMSG. The difference - between NOTICE and PRIVMSG is that automatic replies must never be - sent in response to a NOTICE message. This rule applies to servers - too - they must not send any error reply back to the client on - receipt of a notice. The object of this rule is to avoid loops - between a client automatically sending something in response to - something it received. This is typically used by automatons (clients - with either an AI or other interactive program controlling their - actions) which are always seen to be replying lest they end up in a - loop with another automaton. - - See PRIVMSG for more details on replies and examples. - -4.5 User based queries - - User queries are a group of commands which are primarily concerned - with finding details on a particular user or group users. When using - wildcards with any of these commands, if they match, they will only - return information on users who are 'visible' to you. The visibility - of a user is determined as a combination of the user's mode and the - common set of channels you are both on. - -4.5.1 Who query - - Command: WHO - Parameters: [ []] - - The WHO message is used by a client to generate a query which returns - a list of information which 'matches' the parameter given by - the client. In the absence of the parameter, all visible - (users who aren't invisible (user mode +i) and who don't have a - common channel with the requesting client) are listed. The same - result can be achieved by using a of "0" or any wildcard which - - - -Oikarinen & Reed [Page 33] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - will end up matching every entry possible. - - The passed to WHO is matched against users' host, server, real - name and nickname if the channel cannot be found. - - If the "o" parameter is passed only operators are returned according - to the name mask supplied. - - Numeric Replies: - - ERR_NOSUCHSERVER - RPL_WHOREPLY RPL_ENDOFWHO - - Examples: - - WHO *.fi ; List all users who match against - "*.fi". - - WHO jto* o ; List all users with a match against - "jto*" if they are an operator. - -4.5.2 Whois query - - Command: WHOIS - Parameters: [] [,[,...]] - - This message is used to query information about particular user. The - server will answer this message with several numeric messages - indicating different statuses of each user which matches the nickmask - (if you are entitled to see them). If no wildcard is present in the - , any information about that nick which you are allowed to - see is presented. A comma (',') separated list of nicknames may be - given. - - The latter version sends the query to a specific server. It is - useful if you want to know how long the user in question has been - idle as only local server (ie. the server the user is directly - connected to) knows that information, while everything else is - globally known. - - Numeric Replies: - - ERR_NOSUCHSERVER ERR_NONICKNAMEGIVEN - RPL_WHOISUSER RPL_WHOISCHANNELS - RPL_WHOISCHANNELS RPL_WHOISSERVER - RPL_AWAY RPL_WHOISOPERATOR - RPL_WHOISIDLE ERR_NOSUCHNICK - RPL_ENDOFWHOIS - - - -Oikarinen & Reed [Page 34] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - Examples: - - WHOIS wiz ; return available user information - about nick WiZ - - WHOIS eff.org trillian ; ask server eff.org for user - information about trillian - -4.5.3 Whowas - - Command: WHOWAS - Parameters: [ []] - - Whowas asks for information about a nickname which no longer exists. - This may either be due to a nickname change or the user leaving IRC. - In response to this query, the server searches through its nickname - history, looking for any nicks which are lexically the same (no wild - card matching here). The history is searched backward, returning the - most recent entry first. If there are multiple entries, up to - replies will be returned (or all of them if no - parameter is given). If a non-positive number is passed as being - , then a full search is done. - - Numeric Replies: - - ERR_NONICKNAMEGIVEN ERR_WASNOSUCHNICK - RPL_WHOWASUSER RPL_WHOISSERVER - RPL_ENDOFWHOWAS - - Examples: - - WHOWAS Wiz ; return all information in the nick - history about nick "WiZ"; - - WHOWAS Mermaid 9 ; return at most, the 9 most recent - entries in the nick history for - "Mermaid"; - - WHOWAS Trillian 1 *.edu ; return the most recent history for - "Trillian" from the first server found - to match "*.edu". - -4.6 Miscellaneous messages - - Messages in this category do not fit into any of the above categories - but are nonetheless still a part of and required by the protocol. - - - - - -Oikarinen & Reed [Page 35] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -4.6.1 Kill message - - Command: KILL - Parameters: - - The KILL message is used to cause a client-server connection to be - closed by the server which has the actual connection. KILL is used - by servers when they encounter a duplicate entry in the list of valid - nicknames and is used to remove both entries. It is also available - to operators. - - Clients which have automatic reconnect algorithms effectively make - this command useless since the disconnection is only brief. It does - however break the flow of data and can be used to stop large amounts - of being abused, any user may elect to receive KILL messages - generated for others to keep an 'eye' on would be trouble spots. - - In an arena where nicknames are required to be globally unique at all - times, KILL messages are sent whenever 'duplicates' are detected - (that is an attempt to register two users with the same nickname) in - the hope that both of them will disappear and only 1 reappear. - - The comment given must reflect the actual reason for the KILL. For - server-generated KILLs it usually is made up of details concerning - the origins of the two conflicting nicknames. For users it is left - up to them to provide an adequate reason to satisfy others who see - it. To prevent/discourage fake KILLs from being generated to hide - the identify of the KILLer, the comment also shows a 'kill-path' - which is updated by each server it passes through, each prepending - its name to the path. - - Numeric Replies: - - ERR_NOPRIVILEGES ERR_NEEDMOREPARAMS - ERR_NOSUCHNICK ERR_CANTKILLSERVER - - - KILL David (csd.bu.edu <- tolsun.oulu.fi) - ; Nickname collision between csd.bu.edu - and tolson.oulu.fi - - - NOTE: - It is recommended that only Operators be allowed to kill other users - with KILL message. In an ideal world not even operators would need - to do this and it would be left to servers to deal with. - - - - - -Oikarinen & Reed [Page 36] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -4.6.2 Ping message - - Command: PING - Parameters: [] - - The PING message is used to test the presence of an active client at - the other end of the connection. A PING message is sent at regular - intervals if no other activity detected coming from a connection. If - a connection fails to respond to a PING command within a set amount - of time, that connection is closed. - - Any client which receives a PING message must respond to - (server which sent the PING message out) as quickly as possible with - an appropriate PONG message to indicate it is still there and alive. - Servers should not respond to PING commands but rely on PINGs from - the other end of the connection to indicate the connection is alive. - If the parameter is specified, the PING message gets - forwarded there. - - Numeric Replies: - - ERR_NOORIGIN ERR_NOSUCHSERVER - - Examples: - - PING tolsun.oulu.fi ; server sending a PING message to - another server to indicate it is still - alive. - - PING WiZ ; PING message being sent to nick WiZ - -4.6.3 Pong message - - Command: PONG - Parameters: [] - - PONG message is a reply to ping message. If parameter is - given this message must be forwarded to given daemon. The - parameter is the name of the daemon who has responded to PING message - and generated this message. - - Numeric Replies: - - ERR_NOORIGIN ERR_NOSUCHSERVER - - Examples: - - PONG csd.bu.edu tolsun.oulu.fi ; PONG message from csd.bu.edu to - - - -Oikarinen & Reed [Page 37] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - tolsun.oulu.fi - -4.6.4 Error - - Command: ERROR - Parameters: - - The ERROR command is for use by servers when reporting a serious or - fatal error to its operators. It may also be sent from one server to - another but must not be accepted from any normal unknown clients. - - An ERROR message is for use for reporting errors which occur with a - server-to-server link only. An ERROR message is sent to the server - at the other end (which sends it to all of its connected operators) - and to all operators currently connected. It is not to be passed - onto any other servers by a server if it is received from a server. - - When a server sends a received ERROR message to its operators, the - message should be encapsulated inside a NOTICE message, indicating - that the client was not responsible for the error. - - Numerics: - - None. - - Examples: - - ERROR :Server *.fi already exists; ERROR message to the other server - which caused this error. - - NOTICE WiZ :ERROR from csd.bu.edu -- Server *.fi already exists - ; Same ERROR message as above but sent - to user WiZ on the other server. - -5. OPTIONALS - - This section describes OPTIONAL messages. They are not required in a - working server implementation of the protocol described herein. In - the absence of the option, an error reply message must be generated - or an unknown command error. If the message is destined for another - server to answer then it must be passed on (elementary parsing - required) The allocated numerics for this are listed with the - messages below. - -5.1 Away - - Command: AWAY - Parameters: [message] - - - -Oikarinen & Reed [Page 38] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - With the AWAY message, clients can set an automatic reply string for - any PRIVMSG commands directed at them (not to a channel they are on). - The automatic reply is sent by the server to client sending the - PRIVMSG command. The only replying server is the one to which the - sending client is connected to. - - The AWAY message is used either with one parameter (to set an AWAY - message) or with no parameters (to remove the AWAY message). - - Numeric Replies: - - RPL_UNAWAY RPL_NOWAWAY - - Examples: - - AWAY :Gone to lunch. Back in 5 ; set away message to "Gone to lunch. - Back in 5". - - :WiZ AWAY ; unmark WiZ as being away. - - -5.2 Rehash message - - Command: REHASH - Parameters: None - - The rehash message can be used by the operator to force the server to - re-read and process its configuration file. - - Numeric Replies: - - RPL_REHASHING ERR_NOPRIVILEGES - -Examples: - -REHASH ; message from client with operator - status to server asking it to reread its - configuration file. - -5.3 Restart message - - Command: RESTART - Parameters: None - - The restart message can only be used by an operator to force a server - restart itself. This message is optional since it may be viewed as a - risk to allow arbitrary people to connect to a server as an operator - and execute this command, causing (at least) a disruption to service. - - - -Oikarinen & Reed [Page 39] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - The RESTART command must always be fully processed by the server to - which the sending client is connected and not be passed onto other - connected servers. - - Numeric Replies: - - ERR_NOPRIVILEGES - - Examples: - - RESTART ; no parameters required. - -5.4 Summon message - - Command: SUMMON - Parameters: [] - - The SUMMON command can be used to give users who are on a host - running an IRC server a message asking them to please join IRC. This - message is only sent if the target server (a) has SUMMON enabled, (b) - the user is logged in and (c) the server process can write to the - user's tty (or similar). - - If no parameter is given it tries to summon from the - server the client is connected to is assumed as the target. - - If summon is not enabled in a server, it must return the - ERR_SUMMONDISABLED numeric and pass the summon message onwards. - - Numeric Replies: - - ERR_NORECIPIENT ERR_FILEERROR - ERR_NOLOGIN ERR_NOSUCHSERVER - RPL_SUMMONING - - Examples: - - SUMMON jto ; summon user jto on the server's host - - SUMMON jto tolsun.oulu.fi ; summon user jto on the host which a - server named "tolsun.oulu.fi" is - running. - - -5.5 Users - - Command: USERS - Parameters: [] - - - -Oikarinen & Reed [Page 40] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - The USERS command returns a list of users logged into the server in a - similar format to who(1), rusers(1) and finger(1). Some people - may disable this command on their server for security related - reasons. If disabled, the correct numeric must be returned to - indicate this. - - Numeric Replies: - - ERR_NOSUCHSERVER ERR_FILEERROR - RPL_USERSSTART RPL_USERS - RPL_NOUSERS RPL_ENDOFUSERS - ERR_USERSDISABLED - - Disabled Reply: - - ERR_USERSDISABLED - - Examples: - -USERS eff.org ; request a list of users logged in on - server eff.org - -:John USERS tolsun.oulu.fi ; request from John for a list of users - logged in on server tolsun.oulu.fi - -5.6 Operwall message - - Command: WALLOPS - Parameters: Text to be sent to all operators currently online - - Sends a message to all operators currently online. After - implementing WALLOPS as a user command it was found that it was - often and commonly abused as a means of sending a message to a lot - of people (much similar to WALL). Due to this it is recommended - that the current implementation of WALLOPS be used as an - example by allowing and recognising only servers as the senders of - WALLOPS. - - Numeric Replies: - - ERR_NEEDMOREPARAMS - - Examples: - - :csd.bu.edu WALLOPS :Connect '*.uiuc.edu 6667' from Joshua; WALLOPS - message from csd.bu.edu announcing a - CONNECT message it received and acted - upon from Joshua. - - - -Oikarinen & Reed [Page 41] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -5.7 Userhost message - - Command: USERHOST - Parameters: {} - - The USERHOST command takes a list of up to 5 nicknames, each - separated by a space character and returns a list of information - about each nickname that it found. The returned list has each reply - separated by a space. - - Numeric Replies: - - RPL_USERHOST ERR_NEEDMOREPARAMS - - Examples: - - USERHOST Wiz Michael Marty p ;USERHOST request for information on - nicks "Wiz", "Michael", "Marty" and "p" - -5.8 Ison message - - Command: ISON - Parameters: {} - - The ISON command was implemented to provide a quick and efficient - means to get a response about whether a given nickname was currently - on IRC. ISON only takes one (1) parameter: a space-separated list of - nicks. For each nickname in the list that is present, the server - adds that to its reply string. Thus the reply string may return - empty (none of the given nicks are present), an exact copy of the - parameter string (all of them present) or as any other subset of the - set of nicks given in the parameter. The only limit on the number - of nicks that may be checked is that the combined length must not be - too large as to cause the server to chop it off so it fits in 512 - characters. - - ISON is only be processed by the server local to the client sending - the command and thus not passed onto other servers for further - processing. - - Numeric Replies: - - RPL_ISON ERR_NEEDMOREPARAMS - - Examples: - - ISON phone trillian WiZ jarlek Avalon Angel Monstah - ; Sample ISON request for 7 nicks. - - - -Oikarinen & Reed [Page 42] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - -6. REPLIES - - The following is a list of numeric replies which are generated in - response to the commands given above. Each numeric is given with its - number, name and reply string. - -6.1 Error Replies. - - 401 ERR_NOSUCHNICK - " :No such nick/channel" - - - Used to indicate the nickname parameter supplied to a - command is currently unused. - - 402 ERR_NOSUCHSERVER - " :No such server" - - - Used to indicate the server name given currently - doesn't exist. - - 403 ERR_NOSUCHCHANNEL - " :No such channel" - - - Used to indicate the given channel name is invalid. - - 404 ERR_CANNOTSENDTOCHAN - " :Cannot send to channel" - - - Sent to a user who is either (a) not on a channel - which is mode +n or (b) not a chanop (or mode +v) on - a channel which has mode +m set and is trying to send - a PRIVMSG message to that channel. - - 405 ERR_TOOMANYCHANNELS - " :You have joined too many \ - channels" - - Sent to a user when they have joined the maximum - number of allowed channels and they try to join - another channel. - - 406 ERR_WASNOSUCHNICK - " :There was no such nickname" - - - Returned by WHOWAS to indicate there is no history - information for that nickname. - - 407 ERR_TOOMANYTARGETS - " :Duplicate recipients. No message \ - - - -Oikarinen & Reed [Page 43] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - delivered" - - - Returned to a client which is attempting to send a - PRIVMSG/NOTICE using the user@host destination format - and for a user@host which has several occurrences. - - 409 ERR_NOORIGIN - ":No origin specified" - - - PING or PONG message missing the originator parameter - which is required since these commands must work - without valid prefixes. - - 411 ERR_NORECIPIENT - ":No recipient given ()" - 412 ERR_NOTEXTTOSEND - ":No text to send" - 413 ERR_NOTOPLEVEL - " :No toplevel domain specified" - 414 ERR_WILDTOPLEVEL - " :Wildcard in toplevel domain" - - - 412 - 414 are returned by PRIVMSG to indicate that - the message wasn't delivered for some reason. - ERR_NOTOPLEVEL and ERR_WILDTOPLEVEL are errors that - are returned when an invalid use of - "PRIVMSG $" or "PRIVMSG #" is attempted. - - 421 ERR_UNKNOWNCOMMAND - " :Unknown command" - - - Returned to a registered client to indicate that the - command sent is unknown by the server. - - 422 ERR_NOMOTD - ":MOTD File is missing" - - - Server's MOTD file could not be opened by the server. - - 423 ERR_NOADMININFO - " :No administrative info available" - - - Returned by a server in response to an ADMIN message - when there is an error in finding the appropriate - information. - - 424 ERR_FILEERROR - ":File error doing on " - - - -Oikarinen & Reed [Page 44] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - - Generic error message used to report a failed file - operation during the processing of a message. - - 431 ERR_NONICKNAMEGIVEN - ":No nickname given" - - - Returned when a nickname parameter expected for a - command and isn't found. - - 432 ERR_ERRONEUSNICKNAME - " :Erroneus nickname" - - - Returned after receiving a NICK message which contains - characters which do not fall in the defined set. See - section x.x.x for details on valid nicknames. - - 433 ERR_NICKNAMEINUSE - " :Nickname is already in use" - - - Returned when a NICK message is processed that results - in an attempt to change to a currently existing - nickname. - - 436 ERR_NICKCOLLISION - " :Nickname collision KILL" - - - Returned by a server to a client when it detects a - nickname collision (registered of a NICK that - already exists by another server). - - 441 ERR_USERNOTINCHANNEL - " :They aren't on that channel" - - - Returned by the server to indicate that the target - user of the command is not on the given channel. - - 442 ERR_NOTONCHANNEL - " :You're not on that channel" - - - Returned by the server whenever a client tries to - perform a channel effecting command for which the - client isn't a member. - - 443 ERR_USERONCHANNEL - " :is already on channel" - - - Returned when a client tries to invite a user to a - channel they are already on. - - - -Oikarinen & Reed [Page 45] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - 444 ERR_NOLOGIN - " :User not logged in" - - - Returned by the summon after a SUMMON command for a - user was unable to be performed since they were not - logged in. - - 445 ERR_SUMMONDISABLED - ":SUMMON has been disabled" - - - Returned as a response to the SUMMON command. Must be - returned by any server which does not implement it. - - 446 ERR_USERSDISABLED - ":USERS has been disabled" - - - Returned as a response to the USERS command. Must be - returned by any server which does not implement it. - - 451 ERR_NOTREGISTERED - ":You have not registered" - - - Returned by the server to indicate that the client - must be registered before the server will allow it - to be parsed in detail. - - 461 ERR_NEEDMOREPARAMS - " :Not enough parameters" - - - Returned by the server by numerous commands to - indicate to the client that it didn't supply enough - parameters. - - 462 ERR_ALREADYREGISTRED - ":You may not reregister" - - - Returned by the server to any link which tries to - change part of the registered details (such as - password or user details from second USER message). - - - 463 ERR_NOPERMFORHOST - ":Your host isn't among the privileged" - - - Returned to a client which attempts to register with - a server which does not been setup to allow - connections from the host the attempted connection - is tried. - - - -Oikarinen & Reed [Page 46] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - 464 ERR_PASSWDMISMATCH - ":Password incorrect" - - - Returned to indicate a failed attempt at registering - a connection for which a password was required and - was either not given or incorrect. - - 465 ERR_YOUREBANNEDCREEP - ":You are banned from this server" - - - Returned after an attempt to connect and register - yourself with a server which has been setup to - explicitly deny connections to you. - - 467 ERR_KEYSET - " :Channel key already set" - 471 ERR_CHANNELISFULL - " :Cannot join channel (+l)" - 472 ERR_UNKNOWNMODE - " :is unknown mode char to me" - 473 ERR_INVITEONLYCHAN - " :Cannot join channel (+i)" - 474 ERR_BANNEDFROMCHAN - " :Cannot join channel (+b)" - 475 ERR_BADCHANNELKEY - " :Cannot join channel (+k)" - 481 ERR_NOPRIVILEGES - ":Permission Denied- You're not an IRC operator" - - - Any command requiring operator privileges to operate - must return this error to indicate the attempt was - unsuccessful. - - 482 ERR_CHANOPRIVSNEEDED - " :You're not channel operator" - - - Any command requiring 'chanop' privileges (such as - MODE messages) must return this error if the client - making the attempt is not a chanop on the specified - channel. - - 483 ERR_CANTKILLSERVER - ":You cant kill a server!" - - - Any attempts to use the KILL command on a server - are to be refused and this error returned directly - to the client. - - - - -Oikarinen & Reed [Page 47] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - 491 ERR_NOOPERHOST - ":No O-lines for your host" - - - If a client sends an OPER message and the server has - not been configured to allow connections from the - client's host as an operator, this error must be - returned. - - 501 ERR_UMODEUNKNOWNFLAG - ":Unknown MODE flag" - - - Returned by the server to indicate that a MODE - message was sent with a nickname parameter and that - the a mode flag sent was not recognized. - - 502 ERR_USERSDONTMATCH - ":Cant change mode for other users" - - - Error sent to any user trying to view or change the - user mode for a user other than themselves. - -6.2 Command responses. - - 300 RPL_NONE - Dummy reply number. Not used. - - 302 RPL_USERHOST - ":[{}]" - - - Reply format used by USERHOST to list replies to - the query list. The reply string is composed as - follows: - - ::= ['*'] '=' <'+'|'-'> - - The '*' indicates whether the client has registered - as an Operator. The '-' or '+' characters represent - whether the client has set an AWAY message or not - respectively. - - 303 RPL_ISON - ":[ {}]" - - - Reply format used by ISON to list replies to the - query list. - - 301 RPL_AWAY - " :" - - - -Oikarinen & Reed [Page 48] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - 305 RPL_UNAWAY - ":You are no longer marked as being away" - 306 RPL_NOWAWAY - ":You have been marked as being away" - - - These replies are used with the AWAY command (if - allowed). RPL_AWAY is sent to any client sending a - PRIVMSG to a client which is away. RPL_AWAY is only - sent by the server to which the client is connected. - Replies RPL_UNAWAY and RPL_NOWAWAY are sent when the - client removes and sets an AWAY message. - - 311 RPL_WHOISUSER - " * :" - 312 RPL_WHOISSERVER - " :" - 313 RPL_WHOISOPERATOR - " :is an IRC operator" - 317 RPL_WHOISIDLE - " :seconds idle" - 318 RPL_ENDOFWHOIS - " :End of /WHOIS list" - 319 RPL_WHOISCHANNELS - " :{[@|+]}" - - - Replies 311 - 313, 317 - 319 are all replies - generated in response to a WHOIS message. Given that - there are enough parameters present, the answering - server must either formulate a reply out of the above - numerics (if the query nick is found) or return an - error reply. The '*' in RPL_WHOISUSER is there as - the literal character and not as a wild card. For - each reply set, only RPL_WHOISCHANNELS may appear - more than once (for long lists of channel names). - The '@' and '+' characters next to the channel name - indicate whether a client is a channel operator or - has been granted permission to speak on a moderated - channel. The RPL_ENDOFWHOIS reply is used to mark - the end of processing a WHOIS message. - - 314 RPL_WHOWASUSER - " * :" - 369 RPL_ENDOFWHOWAS - " :End of WHOWAS" - - - When replying to a WHOWAS message, a server must use - the replies RPL_WHOWASUSER, RPL_WHOISSERVER or - ERR_WASNOSUCHNICK for each nickname in the presented - - - -Oikarinen & Reed [Page 49] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - list. At the end of all reply batches, there must - be RPL_ENDOFWHOWAS (even if there was only one reply - and it was an error). - - 321 RPL_LISTSTART - "Channel :Users Name" - 322 RPL_LIST - " <# visible> :" - 323 RPL_LISTEND - ":End of /LIST" - - - Replies RPL_LISTSTART, RPL_LIST, RPL_LISTEND mark - the start, actual replies with data and end of the - server's response to a LIST command. If there are - no channels available to return, only the start - and end reply must be sent. - - 324 RPL_CHANNELMODEIS - " " - - 331 RPL_NOTOPIC - " :No topic is set" - 332 RPL_TOPIC - " :" - - - When sending a TOPIC message to determine the - channel topic, one of two replies is sent. If - the topic is set, RPL_TOPIC is sent back else - RPL_NOTOPIC. - - 341 RPL_INVITING - " " - - - Returned by the server to indicate that the - attempted INVITE message was successful and is - being passed onto the end client. - - 342 RPL_SUMMONING - " :Summoning user to IRC" - - - Returned by a server answering a SUMMON message to - indicate that it is summoning that user. - - 351 RPL_VERSION - ". :" - - - Reply by the server showing its version details. - The is the version of the software being - - - -Oikarinen & Reed [Page 50] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - used (including any patchlevel revisions) and the - is used to indicate if the server is - running in "debug mode". - - The "comments" field may contain any comments about - the version or further version details. - - 352 RPL_WHOREPLY - " \ - [*][@|+] : " - 315 RPL_ENDOFWHO - " :End of /WHO list" - - - The RPL_WHOREPLY and RPL_ENDOFWHO pair are used - to answer a WHO message. The RPL_WHOREPLY is only - sent if there is an appropriate match to the WHO - query. If there is a list of parameters supplied - with a WHO message, a RPL_ENDOFWHO must be sent - after processing each list item with being - the item. - - 353 RPL_NAMREPLY - " :[[@|+] [[@|+] [...]]]" - 366 RPL_ENDOFNAMES - " :End of /NAMES list" - - - To reply to a NAMES message, a reply pair consisting - of RPL_NAMREPLY and RPL_ENDOFNAMES is sent by the - server back to the client. If there is no channel - found as in the query, then only RPL_ENDOFNAMES is - returned. The exception to this is when a NAMES - message is sent with no parameters and all visible - channels and contents are sent back in a series of - RPL_NAMEREPLY messages with a RPL_ENDOFNAMES to mark - the end. - - 364 RPL_LINKS - " : " - 365 RPL_ENDOFLINKS - " :End of /LINKS list" - - - In replying to the LINKS message, a server must send - replies back using the RPL_LINKS numeric and mark the - end of the list using an RPL_ENDOFLINKS reply. - - 367 RPL_BANLIST - " " - 368 RPL_ENDOFBANLIST - - - -Oikarinen & Reed [Page 51] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - " :End of channel ban list" - - - When listing the active 'bans' for a given channel, - a server is required to send the list back using the - RPL_BANLIST and RPL_ENDOFBANLIST messages. A separate - RPL_BANLIST is sent for each active banid. After the - banids have been listed (or if none present) a - RPL_ENDOFBANLIST must be sent. - - 371 RPL_INFO - ":" - 374 RPL_ENDOFINFO - ":End of /INFO list" - - - A server responding to an INFO message is required to - send all its 'info' in a series of RPL_INFO messages - with a RPL_ENDOFINFO reply to indicate the end of the - replies. - - 375 RPL_MOTDSTART - ":- Message of the day - " - 372 RPL_MOTD - ":- " - 376 RPL_ENDOFMOTD - ":End of /MOTD command" - - - When responding to the MOTD message and the MOTD file - is found, the file is displayed line by line, with - each line no longer than 80 characters, using - RPL_MOTD format replies. These should be surrounded - by a RPL_MOTDSTART (before the RPL_MOTDs) and an - RPL_ENDOFMOTD (after). - - 381 RPL_YOUREOPER - ":You are now an IRC operator" - - - RPL_YOUREOPER is sent back to a client which has - just successfully issued an OPER message and gained - operator status. - - 382 RPL_REHASHING - " :Rehashing" - - - If the REHASH option is used and an operator sends - a REHASH message, an RPL_REHASHING is sent back to - the operator. - - 391 RPL_TIME - - - -Oikarinen & Reed [Page 52] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - " :" - - - When replying to the TIME message, a server must send - the reply using the RPL_TIME format above. The string - showing the time need only contain the correct day and - time there. There is no further requirement for the - time string. - - 392 RPL_USERSSTART - ":UserID Terminal Host" - 393 RPL_USERS - ":%-8s %-9s %-8s" - 394 RPL_ENDOFUSERS - ":End of users" - 395 RPL_NOUSERS - ":Nobody logged in" - - - If the USERS message is handled by a server, the - replies RPL_USERSTART, RPL_USERS, RPL_ENDOFUSERS and - RPL_NOUSERS are used. RPL_USERSSTART must be sent - first, following by either a sequence of RPL_USERS - or a single RPL_NOUSER. Following this is - RPL_ENDOFUSERS. - - 200 RPL_TRACELINK - "Link \ - " - 201 RPL_TRACECONNECTING - "Try. " - 202 RPL_TRACEHANDSHAKE - "H.S. " - 203 RPL_TRACEUNKNOWN - "???? []" - 204 RPL_TRACEOPERATOR - "Oper " - 205 RPL_TRACEUSER - "User " - 206 RPL_TRACESERVER - "Serv S C \ - @" - 208 RPL_TRACENEWTYPE - " 0 " - 261 RPL_TRACELOG - "File " - - - The RPL_TRACE* are all returned by the server in - response to the TRACE message. How many are - returned is dependent on the the TRACE message and - - - -Oikarinen & Reed [Page 53] - -RFC 1459 Internet Relay Chat Protocol May 1993 - - - whether it was sent by an operator or not. There - is no predefined order for which occurs first. - Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and - RPL_TRACEHANDSHAKE are all used for connections - which have not been fully established and are either - unknown, still attempting to connect or in the - process of completing the 'server handshake'. - RPL_TRACELINK is sent by any server which handles - a TRACE message and has to pass it on to another - server. The list of RPL_TRACELINKs sent in - response to a TRACE command traversing the IRC - network should reflect the actual connectivity of - the servers themselves along that path. - RPL_TRACENEWTYPE is to be used for any connection - which does not fit in the other categories but is - being displayed anyway. - - 211 RPL_STATSLINKINFO - " \ - \ -