diff --git a/00readme b/00readme new file mode 100644 index 0000000..669ed74 --- /dev/null +++ b/00readme @@ -0,0 +1,7 @@ +From: Carl von Loesch +To: rxirc-l@vmtecqro.qro.itesm.mx (The rxIRC List), + operlist@eff.org (IRC Operchaos List) +Subject: rxIRC 2.0 ready to go - FTP admins invited to copy/mirror! +Date: Mon, 14 Jun 93 15:57:16 CES + +I am hereby releasing rxIRC 2.0. rxIRC is the IRC client for IBM VM systems. diff --git a/intro.helpirc b/intro.helpirc new file mode 100644 index 0000000..6e03409 --- /dev/null +++ b/intro.helpirc @@ -0,0 +1,350 @@ + INTERNET RELAY CHAT + + +Author: Robert D. Blais +Email: + +Revised: 27 February 1993 +Version: 1.10 + +PURPOSE: This document attempts to explain, in simple terms, +what IRC is and in general, how it is used. It is intended to +supply information for new users not familiar with IRC and to +serve as a reference for experienced users. + Since there are many different programs on several different +operating systems, client-specific information has been left out. +Users should refer to the documentation that came with their IRC +program for information specific to using that client. + Users may also wish to read the author's document "Standard +IRC Commands" for information about the commands mentioned in +this document. + +CREDITS: The information contained in this document has been +culled several sources, including the alt.irc group in Usenet +news and from the author's own experience using IRC. In +addition, the following documents proved invaluable in the making +of this document: "Alt.irc.faq" by Helen Rose , +"Internet Relay Chat, a real-time conversational system" by Karl +Kleinpaste , and "How To Behave on IRC" +by Lea Viljanen and Ari Husa +. Thanks to Kelly Derek Deyoe + for providing a list of countries and +their domain extensions. Special thanks to Carl "LynX" von Loesch +for his help and suggestions. + +I. HISTORY + + Internet Relay Chat (IRC) was originally written by Jarkko +Oikarinen in 1988 as a replacement for the +Unix "Talk" program. It's purpose is to allow multiple users to +converse in real-time over the collection of networks known as +Internet. It is based on the functionality of the Bitnet Relay +system but that functionality has been greatly expanded. + From it's humble beginnings in Finland, IRC grew to become +the largest international, relayed conferencing system in the +world. It is available in over 20 countries around the world and +has been host to over 1000 users at one time! Countless thousands +of people, from college students to business executives have used +IRC and new users sign-on every day. + The Internet is primarily for academic use. IRC is a +communications layer of internet, and as such, it's main purpose +is academic use. Many people depend on it as a tool for +exchanging information with colleagues, business associates and +fellow researchers. + +II. CHANNELS + + IRC is divided up into virtual spaces called channels. A +channel is a gathering place where people with a common interest +can get together and discuss whatever that interest may be. A +channel does not exist until someone joins it and ceases to +exist when the last person leaves it. + +A. Channel Names + + All channels on IRC have names. A channel name can be just +about any single "word" of text preceded by a pound sign (#). +For example, #123, #My_channel, and #$$$ are all valid channel +names. Examples of popular channels on IRC include #hottub, +#initgame, and #hotsex. + +B. Creating A Channel + + To create a channel, simply join it either with the /join +or /channel command. For example, to create the channel #Test +you would type /join #Test. + +C. Leaving A Channel + + To leave a channel, issue the /part command. For example, +to leave #Test you would type /part #Test. Some clients will +automatically issue /part for you if you use the /channel +command, so check your program's documentation. + +D. Multiple Channels + + Most IRC client programs allow you to be on several channels +at once. Check your client's documentation for specific +information on using multiple channels. Also, look for +information on the /, /msg, and /query commands. + +E. Channel Operators + + The first person to join a channel is known as the Channel +Operator (ChanOp) and can determine certain aspects of the +channel, such as the number of people allowed on the channel and +whether the channel is public, private, secret, or invite-only. +A ChanOp can also delegate ChanOp privileges to other users on +the channel. Look for information on the /mode command for +specifics about channel modes and ChanOp powers. + +III. NICKNAMES + + All IRC users are identified by unique nicknames. Duplicate +nicknames are not allowed by the IRC servers. + +A. Changing Nicknames + + By default your nickname is your userid, but may be changed +with the /nick command. Many clients also allow you to specify a +default nickname that will be used whenever you sign-on to IRC. +Check your client's documentation for specifics about setting a +default nickname. + +B. Nickserv + + Many people register their nicknames with an on-line service +called Nickserv. If you choose a nickname that is registered to +someone else, you will get a message from Nickserv telling you +who it is registered to. If you get such a message, pick a new +nickname. It is considered very rude to use someone else's +nickname and may cause confusion when other users mistake you for +their friend. + For nickname registration information type the command +/msg nickserv@service.de help. When you register a nickname, +Nickserv will ask you for a password. DO NOT USE YOUR LOGIN +PASSWORD. IRC protocols are not completely secure and other +users may be able to get your Nickserv password. Also, REMEMBER +YOUR NICKSERV PASSWORD. You may need it if you ever want to +change your registered nickname or add a new host site to your +access list. + +IV. IRC OPERATORS + + The IRC Operators (IRCOps) are the people who maintain IRC. +They keep the servers running and up to date, keep the links +connected and routed properly, they answer questions from the +users, and they remove offensive users by way of the /kill +command. IRCOps are indicated by an asterisk (*) next to their +nickname in /who and by the line " has a connection to the +Twilight Zone." in /whois. + The best way to get help or information from IRCOps is to +join the IRCOp channel #Twilight_zone. Once you are on the +channel, state your problem or question in a brief, specific, +polite manner and wait for a reply. Usually you'll get a +response within a few minutes, but since many of the IRCOps have +responsibilities apart from IRC, they aren't always immediately +available. If you don't get a reply in a reasonable amount of +time, try again later. + +V. MESSAGES + + There are generally four types of messages you will see +while using IRC. The four types are informational messages, +public messages, private messages, and notices. Some clients may +also have a fifth type that gives information about things +happening within the program, such as when you add a user to the +/ignore list, but these messages are not normally sent over IRC. + +A. Informational messages. + + Informational messages let you know something in the IRC +environment has changed. When someone joins or leaves your +channel, changes the channel mode or topic, changes their +nickname, or makes some other such change you will see a message +informing you of the change. The format of the message may vary +depending on what client you are running, but in general it will +look something like the following: + +*** Bub joins channel #hottub +*** Mode change: Hoser sets #hottub +o Bub + +B. Public Messages. + + Public messages are seen by everyone on the channel. +Everything you type to a channel shows up as a public message +with your nickname and the channel name displayed in angle +brackets before the message. A public message looks like the +following: + + Hello world! + or + Hello world! + +C. Private Messages. + + Private messages are generally only seen by the person who +they are sent to. The /msg and /query commands are used to send +private messages. Private messages are displayed with the +sender's nickname between asterisks. A private message would +look like the following: + +*Bub* Thanks for Opping me, Hoser. + +D. Notices + + Any automatic response, such as server messages, CTCP +(client to client protocol) replies, and robot replies MUST be in +the form of a notice. Users can also send notices with the +/notice command, but this is not generally necessary. A notice +will generally be shown with the sender's nickname and channel +between dashes and might look like the following: + +-Bubserv:#hottub- Bub sends a beer to Hoser. +-Bubserv:#hottub- /msg Bubserv help for help on using Bubserv. + +VI. SERVERS + + IRC servers are programs that relay the messages and +commands that you type to other servers and users on the network. +When you first compile or use an IRC program, you will probably +have to give it a server to use. You should normally use the +closest (network-wise) server to you. However, some servers +limit what hosts are allowed to connect to them. + Lists of servers are frequently posted in the Usenet news +group alt.irc. If you don't have access to that group and can't +find a server, try one of the following servers and once you get +on, ask an IRCOp which server in your area you should use. + +Open servers by country: + Australia: coombs.anu.edu.au + Canada: ug.cs.dal.ca + Finland: nic.funet.fi + Germany: irc.informatik.tu-muenchen.de + Netherlands: fysak.fys.ruu.nl + U.S.A.: csd.bu.edu + ucsu.colorado.edu + + Information about a specific server can be obtained by using +the /admin, /info, /motd, and /version commands. If you have a +problem with a particular server the /admin command will give you +the email address of the person(s) in charge of it. The other +commands give you information about the server itself, such as +the software version and the MOTD (Message of the Day). + +VII. BEHAVIOR AND ETIQUETTE + + IRC is a good place to learn about other people, places, and +cultures, to exchange information and ideas, and to meet people. +If everyone follows some basic, common-sense rules of behavior +and etiquette, IRC can be an enjoyable and informative way to use +some of your free time. + +A. Language + + English is the most widely spoken language on IRC but it is +not the only language. Often the channel name or topic will give +you some idea of the language spoken on that channel but this is +not always the case. A user's hostname extension usually gives +an indication of where that user is from and thus, the language +he or she is likely to speak. For example, someone whose +user@host name ends in .jp is most likely speaks Japanese, whereas +someone whose user@host name ends in .fi most likely speaks +Finnish. A list of common domain extensions, by country, is shown +below. + + Country Domain Extension +Austria: .at +Australia: .au +Belgium: .be +Canada: .ca +Switzerland: .ch +Chile: .cl +Czechoslovakia: .cs +Germany: .de +Denmark: .dk +Spain: .es +Finland: .fi +France: .fr +Ireland: .ie +Israel: .il +Iceland: .is +Italy: .it +Japan: .jp +Korea: .kr +Mexico: .mx +Netherlands: .nl +Norway: .no +New Zealand: .nz +Poland: .pl +Sweeden: .se +Singapore: .sg +Taiwan: .tw +United Kingdom: .uk +United States: .us +South Africa: .za +Other: .com (Commercial business) + .edu (Educational institution) + .gov (Government organization) + .mil (Military installation) + .org (Non-profit organization) + .net (Network administration) + + It is a good idea to do a /who on a channel before you join +so you can get an idea of what language might be spoken on that +channel. If the channel consists mostly of people from Finland +and you don't speak Finnish, you probably won't find the channel +very interesting. Also, your own channel name or topic should +indicate what language is spoken on your channel, especially if +it is not English. + +B. Dumping and Flooding + + Dumping large amounts of text or graphics to a channel or a +user is considered rude and is not allowed. It is a waste of +bandwidth and can cause anyone on a slow modem connection to be +jammed for several minutes. Also, the text or graphics that you +find amusing is likely to be quite annoying to other users who +are trying to carry on a conversation. + +C. Morality + + Since IRC is composed of users from all over the world, with +many different backgrounds, different levels of maturity, and +different religious and moral standards, a good rule of thumb is +think before you type. If you wouldn't say something in front of +your boss, teachers, parents, or in other social situations, you +shouldn't say it on IRC. By the same token, be tolerant of other +users. Not all of them have the same views and morals as you and +what is offensive to you might not be to them. + +D. General Behavior + + People on IRC have no other way of judging you than by your +actions and messages. Rude, obnoxious, and offensive behavior is +not tolerated and may get you banned from a channel or /killed +from IRC altogether. If your offenses are great enough, your +local system administrators may be notified and you may lose your +computer account or face other disciplinary actions. + Not everyone using IRC is interested in chatting. More +specifically, not everyone on IRC is interested in chatting with +YOU. Some people use IRC as part of their normal work to be +available to colleagues who might need to reach them quickly. +Other people use IRC for discussion of certain topics of interest +to them. If you don't have anything to contribute to the topic +on a particular channel, don't interrupt and try to start a new +topic. Start a new channel to discuss your topic. + If you send a message to someone or invite them to your +channel, don't assume they are interested in talking to you. If +someone doesn't respond, they may be away from their terminal or +may be too busy to reply. If someone indicates that they aren't +interested in talking to you, leave them alone. Badgering +someone or sending them unwanted messages wastes their time and +yours. You're better off finding someone else to chat with. + +-- +NOTE: This document is hereby placed in the public domain. If +you copy it, please attribute the source. If you modify it, +please note who you are, what changes you made and the date of +those changes in the document header. Take the credit you +deserve, but give credit where it is due. Thanks. diff --git a/month.rxirc b/month.rxirc new file mode 100644 index 0000000..d9c1076 --- /dev/null +++ b/month.rxirc @@ -0,0 +1,6 @@ +expr month word(date(),2) +if word(date(),1)/=1 then skip 2 + echo Hey! Today is the 1st of $(month)! + skip 1 + echo Today is just another day of $(month)... +echo You just ran MONTH RXIRC.. :) diff --git a/profile.rxirc b/profile.rxirc new file mode 100644 index 0000000..9ef0ff4 --- /dev/null +++ b/profile.rxirc @@ -0,0 +1,22 @@ +* Default profile for rxIRC users +* +* PF key setup +pf1 IMM /help +pf2 IMM /xamin +pf3 IMM /bye +pf4 IMM /follow +pf5 IMM /reply +pf6 IMM /lastlog +alias ctoggle %k %c pf$k IMM /toggle $k |join $c|part $c +ctoggle 9 #talk +ctoggle 10 #initgame + +* Easy use of services +alias .ni msg nickserv@service.de +alias .no msg noteserv@service.de +alias .w .ni whois +alias .await .no waitfor +alias .del .no delete +alias .list .no list +alias .m .no msg +alias .read .no read diff --git a/rxirc.readme b/rxirc.readme new file mode 100644 index 0000000..e6a2148 --- /dev/null +++ b/rxirc.readme @@ -0,0 +1,85 @@ +Subject: rxIRC 2.0 for VM/CMS available +Newsgroups: bit.listserv.vm-util,alt.irc,de.comm.internet,de.talk.chat +Keywords: IRC rxIRC rexx vm cms internet bitnet rexx/socket lynx + +Introducing rxIRC: + + rxIRC is a client software for VM to connect to the IRC network, the +Internet Relay Chat, which nowadays counts an average of 1200 users online +day and night, from all over the world, therefore being the biggest +international interactive conferencing system on the planet. + + You can make use of this program only if you have access to a machine +with VM/CMS-type operating system with TCPIP extension installed. To find +out you logon and type 'CP QUERY TCPIP', if it replies 'TCPIP - DSC' then +you can make use of this program, otherwise check with your administration. + + rxIRC is a program written in interpreted RexX, a rather easy to learn +language that gives you a chance to add own features if you miss something +or modify things you dislike. rxIRC supports the complete set of standard +IRC client commands plus a bunch of extras and is more or less up to date +with the current state of development of the IRC protocol. + +New features in rxIRC 2.0: + +- now uses RXSOCKET and REXXWAIT +- has extensive BITNet messaging support + (for instance /query +nick queries a bitnet user) +- /alias with parameter handling +- variables: /set, /expr (rexx expressions), /echo +- /if then +- /source , skip , stop (sourcing) +- /pf, /toggle (setup a pf key with alternating commands) +- /localwho, /catalog +- /chop, /unchop, /k(ick), /t(opic) +- /viewlog, /interpret, /applaud +- documentation has doubled its size.. ;) +- :show_time, display time every now and then +- ircII-bold-code displayed with hilighting, :bold_char + +Requirements: + + The TCPIP handling of rxIRC is done with help of RXSOCKET version 2. +You need to have this package installed, or at least the basic modules. +There are some restrictions concerning the use of RXSOCKET: +- The new version is not compatible to the old one, if you have + programs using version 1 they won't work when you install version 2. +- VM TCP/IP version 2 is required. +- rxIRC should run on CMS 3 up to 9 (370, XA, ESA or XC MACHINE modes) + + If you are going to install rxIRC on a big public disk, you probably +want to install the complete REXX/SOCKET package. You can do so by issueing +TELL LISTSERV AT CUNYVM GET RXSOCKET PACKAGE. Beware that you will be sent +the beauty of over 80 files after this! + + If you want to run rxIRC just by yourself, and RXSOCKET isn't available +already (rxIRC tells you so) then merely issue these commands to get the +modules: + TELL LISTSERV AT CUNYVM GET RXSOCKET MODULE + TELL LISTSERV AT CUNYVM GET REXXWAIT MODULE + + +rxIRC 2.0 itself can be obtained from: + + +Europe: ftp nic.funet.fi + mget /pub/unix/irc/rxirc/*.* + +[Home Site] ftp ftp.informatik.uni-oldenburg.de (134.106.1.9) + mget /pub/irc/rxirc/*.* + +America: ftp ftp.iastate.edu + mget /pub/irc/clients/rxirc/2.0/*.* + + ftp slopoke.mlb.semi.harris.com + mget /pub/irc/clients/rxirc/*.* + +Australia: ftp coombs.anu.edu.au + mget /pub/irc/rxirc/*.* + + +[Mexico] TELL LISTSERV AT VMTECQRO GET RXIRC PACKAGE + + +rxIRC installers are invited to join the rxIRC mailing list by sending a +'SUB RXIRC-L ' command to LISTSERV AT VMTECQRO. diff --git a/standard.helpirc b/standard.helpirc new file mode 100644 index 0000000..d6dc4cd --- /dev/null +++ b/standard.helpirc @@ -0,0 +1,390 @@ + + + STANDARD IRC COMMANDS + + +Author: Robert D. Blais +Email: + +Revised: 11 November 1992 +Version: 1.10 + +PURPOSE: This document attempts to explain, in simple terms, the +standard Internet Relay Chat (IRC) commands that all IRC client +programs should support. It is intended to supply information +for new users not familiar with IRC and to serve as a reference +for experienced users. + Since there are many different programs on several different +operating systems, client-specific information has been left out. +Users should refer to the documentation that came with their IRC +program to see what internal commands it supports and what, if +any, variations on the standard commands that client might have. + +NOTATION: The "standard" command character for IRC clients is +the virgule (/) and has been used exclusively in this document. +However, most IRC client programs allow the user to change the +command character to something else. If yours is different, +substitute your command character wherever you see a virgule. + Many of the commands accept arguments and many of the +arguments will vary, depending on exactly what you are doing. +Variable arguments have been listed within angle brackets. If +there are more than one possible type of argument, the choices +are separated by a pipe (|). For example, +indicates that the argument can either be a user's nickname or a +channel name. + Commands marked with an asterisk (*) are propagated across +the entire network and should be used sparingly to save bandwidth +and avoid confusion. + The term "wildcards" is used frequently in this document. +Whenever a command allows wildcards, it means that certain parts +of the command, such as "user" in user@host, can be replaced by +an asterisk (*) and the command will effect the first or possibly +all occurrences that match. As a rule, if you don't know exactly +what effect wildcards will have, don't use them. + +CREDITS: The information contained in this document has been +culled several sources, including the alt.irc group in Usenet +news, the helpserver IRCIIHelp, and from the author's own +experience using IRC and studying and experimenting with the +code for some of the client programs. Special thanks to Carl +"LynX" von Loesch for his help and suggestions. + +AWAY: * + Occasionally you may be away from your terminal for several + minutes but want to remain connected to IRC. The away + command allows you to specify a message stating that you are + away and, optionally, should tell people when you'll be + back. Other users will see the message whenever they send + you a private message or run the whois command on your + nickname. + + Syntax: /away + /away + + is the new message you specify. + To remove an away message, issue the command with no + argument. + +ADMIN: + The admin command gives the name and email address of the + person in charge of the IRC server you or another user is + using. + + Syntax: /admin + /admin + + is the nickname of the person who's server you + want administration information from. If you omit the + nickname you'll get information about your own server. + +CHANNEL: * + The channel command is used to change channels. On some + clients it will part you from the last channel you joined, + but on others it doesn't. + + Syntax: /channel + + is the name of the new channel you wish to join. + +INFO: + The info command gives information about the server + software. + + Syntax: /info + +INVITE: + Occasionally you may want to invite another user to your + channel. The easiest way to do so is with the invite + command. It is also the only way for other users to join a + channel if the channel mode +i is in effect on that channel. + + Syntax: /invite + + is the nickname of the person you are inviting + and is the channel you are inviting them to. + +JOIN: * + Use the join command to join or create a channel. If the + channel is public or you have been invited to it, you'll + join it. If not, you get a message saying that you cannot + join the channel. + + Syntax: /join + + is the channel you wish to join. + +KICK: * + The kick command is used by ChanOps to remove an offending + user from a channel. + + Syntax: /kick + + is the channel the offending user is to be removed + from and is that user's nickname. + +LIST: + Use the list command to get a list of active channels. This + list will show the channel names, number of users on the + channel, and the channel topic, if there is one. If a + channel has mode +s in effect, it's name will not be shown + but the number of users and the channel topic will still be + displayed. + + Syntax: /list + +LINKS: + The links command lists the IRC servers currently connected + to an IRC server. + + Syntax: /links + /links + + is the server whose links you're interested in. If + you omit the server, you'll see the links to your own + server. Wildcards may be used in server names. + +LUSERS: + The lusers command shows how many people are currently on + IRC. It is automatically called when you sign onto IRC. + + Syntax: /lusers + +MODE: * + There are two types of mode commands. Channel mode commands + effect a channel and user mode commands effect only you, + the user. Any user can set user modes at any time, but + you must be a ChanOp to set channel modes. Several modes + can be set at once. (+ or - before the turns modes + on or off, respectively) + + User modes: + + Syntax: /mode + + is your nickname and the possible modes are: + Mode Description + i - Sets you invisible so you don't show up in /who. + w - Allows you to see Wallops (messages to IRCOps.) + s - Allows you to see server messages and /kills. + o - (Available only to IRCOps.) + + Note: some clients have a /umode command for setting + user modes. + + Channel modes: + + Syntax: /mode + + is the channel you wish to set the mode on and + available modes and their arguments are shown below. + + Mode Arguments Description + b - Ban from a channel. may be a + nickname or a nick!user@host name. + Wildcards are allowed if the user@host form + is used. + i - Makes channel invite-only. + l - Limits the number of users on a channel. + is the maximum number of users + allowed. + m - Channel is moderated, so only channel + operators can talk. + n - No MSGs to the channel are allowed from + people not on the channel. + p - Channel is private and people on it won't + show up in /who, /names, or /whois. It will + show up in /list. + s - Channel is secret, so the channel name won't + show up in /list. + t - Topic limit; only the channel operators may + change the topic. + o - Makes a channel operator. + +MOTD: + The MOTD (Message Of The Day) command redisplays the MOTD + that you saw when you signed on to the server or the new one + if it has been changed since you signed on. It can also be + used to show the MOTD on another server. + + Syntax: /motd + /motd + is the nickname of another user or a + server. If wildcards are used in the server name, the MOTD + of the first server to match the mask will be shown. + +MSG: + Use the msg command to send a private message to another + user or to a channel. If you send a private message to a + single user, only that user will see it (hopefully, but IRC + is not very secure so use caution.) If you send it to a + channel, all the users on that channel will see it. + + Syntax: /msg + + is the person or channel you are sending + the message to and is the message you want to + send. + +NAMES: + The names command lists the nicknames of all the users + on a channel or all of the users on IRC (unless they have + set usermode +i). + + Syntax: /names + + is the channel you want to list the users on. If + is omitted, you will see a list of nicknames for + EVERY channel on IRC! + +NICK: * + Use the nick command to change your nickname. + + Syntax: /nick + + is the new nickname you want. + +NOTICE: + The notice command is generally not necessary, but if you + have an important message that you want everyone on the + channel to pay attention to, you might find it useful. It + is also a requirement that all automatic replies, such as + ctcp replies, robot and server replies, etc., be in the form + of a notice. + + Syntax: /notice + + is the person or channel you are sending + to and is the message you want people to see. + +PART: * + Use the part command to leave a channel. + + Syntax: /part + + is the channel you wish to leave. + +QUERY: + Use the query command to start a private conversation with + another user or to converse with a particular channel when + you're on multiple channels. While in a query, all messages + you type *without* using the / or /msg commands, will + only be seen by the person or channel you are in the query + with. + + Syntax: /query + /query + + is the person or channel you wish to + start a query with. To end a query and resume talking to + your channel, issue the command with no argument. + +QUIT: * + Use the quit command to end your IRC session. + + Syntax: /quit + + is optional. If you want to let people know why + you're quitting, you can give a brief reason. + +TIME: + The time command shows the current time at a server. + + Syntax: /time + /time + + If is specified, the time at that server + will be displayed. If no argument is given, it will return + the time at your server. Wildcards may be used in the + server name. + +TOPIC: * + Use the topic command to set a topic line for your channel. + The topic line will be displayed in the channel list. + + Syntax: /topic + + is the channel you're setting the topic for and + is the topic message. + +TRACE: + The trace command displays a list of the server links that + are connected to a particular server. + + Syntax: /trace + /trace + + is the server whose links you want to see. If you + omit the server, the links to your server will be shown. + +VERSION: + The version command will show what version of IRC a server + is running. It can also be used to find out what client + program another user is using. + + Syntax: /version + /version + + If a nickname is specified, it will return the client + version of that user's program. If a server is specified, + it will return the version of IRC running on that server. + If you omit the arguments it will return the version of the + server you are using. + +WHO: + Use the who command to get a list of users on a channel, at + a particular host, or with a common text string in their + name. + + Syntax: /who + + can be text in a user's nickname, + hostname or IRCname, a channel name, or a server name. + Wildcards are allowed. + +WHOIS: + Use the whois command to get specific information about an + IRC user. + + Syntax: /whois + /whois + + is the server the user specified in is + on. may be omitted. + +WHOWAS: + Use the whowas command to get information about a user who + recently left IRC. + + Syntax: /whowas + + is the nickname of the person you want + information about. + +/: + The virgule (/) is used to talk to the current channel when + you are in a query with another user or channel. The + current channel is normally the last channel you joined, + however, some clients allow you to specify which channel is + current when you are on multiple channels. + + Syntax: / + + is the message to be sent to the current channel. + + In addition to the above commands, there are several other +commands that are primarily for the use of IRCOps. Some of the +commands shown below provide some humorous replies when issued by +regular users, proving that IRC coders have a sense of humor. +Other commands give information which is fairly meaningless to +the average user but hard-core users may be interested. Try them +at your own risk. :-) + +CONNECT, DEOP, DIE, HASH, KILL, OPER, PASS, REHASH, RESTART, +SQUIT, STATS. + +-- +NOTE: This document is hereby placed in the public domain. If +you copy it, please attribute the source. If you modify it, +please note who you are, what changes you made and the date of +those changes in the document header. Take the credit you +deserve, but give credit where it is due. Thanks.