Errors-To: ecto-owner@ns1.rutgers.edu Reply-To: ecto@ns1.rutgers.edu Sender: ecto@ns1.rutgers.edu From: ecto@ns1.rutgers.edu To: ecto-request@ns1.rutgers.edu Bcc: ecto-digest-outbound@ns1.rutgers.edu Subject: ecto #940 ecto, Number 940 Sunday, 26 December 1993 Today's Topics: *-----------------* IRC help ======================================================================== This digest is one very long message about IRC. It is long enough that some mailers may chop it off half way through. (or so). If this happens to you and you want this message, let me know and i'll send it in parts or something. jessica ======================================================================== From: lorenz@olymp.wu-wien.ac.at (What about a trip to Uganda!) Subject: IRC help Date: Sat, 25 Dec 93 12:40:13 CUT Hiya!!!! Sorry I am late, but anyway: Have a MERRY CHRISTMAS all, as well as a HAPPY NEW YEAR!! Here you go with 2 more things about irc: the first one is another telnet site (in Austria, Vienna), the scond one is the IRC primer, written by Nap (from France), with some changes made by myself and (unfortunately) German stuff in it as well because I have revised the whole thing for the students at my university who want to use IRC as well...please forgive me.. 1.) telnet tiger.itc.univie.ac.at 6668 no login, no password. 2.) the IRC primer: HIYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA!!!!!!!!!!!! Also, hier ist ein kleines helpfile, dass Euch allen den Einstieg in IRC erleichtern soll. *HIGH-FIVE* to Gerhard Gonter, der alles erst moeglich gemacht hat, ohne ihn gaebe es IRC auf der WU nicht einmal :-) Sollten nach dem Lesen noch Fragen offen bleiben beziehungsweise Details erwuenscht sein, so stehe ich natuerlich jederzeit (<-- email) oder fast jederzeit (<-- IRC) zur Verfgung. Das helpfile ist nur zum Teil ein Produkt meiner bescheidenen Schpfungs- kraft, den Groateil hat Nicholas Pioch (Nap on IRC) geschrieben, ich habe lediglich Teile upgedated beziehungsweise eigene Passagen hinzugefgt, welche speziell fr den olymp server interessant sind. Viel Spaa beim Lesen wnscht Euch Bernhard (Fingwe [meistens] on IRC). Abstract ~~~~~~~~ Have you ever wanted to talk with other computer users in other parts of the world? Well, guess what.You can! The program is called IRC, (Internet Relay Chat), and it is networked much over North America, Asia Europe, and Oceania. This program is a substitution for 'talk', and many other multiple talk programs you might have read about. When you are talking on IRC, everything you type will instantly be transmitted around the world to other users that might be watching their terminals at the time, they can then type something and respond to your messages, and vice versa. I should warn you that the program can be very addictive once you begin to make friends and contacts on IRC, especially when you learn how to discuss in 14 languages... Sehr richtig. Zu viel und zu langes IRC'en kann zu gravierenden Beein- trchtigungen Eurer Leistungen im Studium fhren (Einige Leute im IRC wer- den Euch das besttigen knnen, daher also immer mit Maa IRC'en, mua ja nicht jeder so InterNet schtig werden wie ich ;). Topics of discussion on IRC are varied, just like the topics of Usenet newsgroups are varied. Technical and political discussions are popular, especially when world events are in progress. IRC is also a way to expand your horizons, as people from many countries and cultures are on 24 hours a day. Most conversations are in English, but there are always channels in German, Japanese, French, Finnish, and occasionally other languages. IRC gained international fame during the late Persian Gulf War, when updates from around the world came across the wire, and most people on IRC gathered on a single channel to hear these reports. CONTENTS ~~~~~~~~~~ 1. Getting started 1.1 Clients and Servers 1.2 How to Behave on IRC 1.3 Privacy on IRC 1.4 First Steps 1.5 Screen and Keyboard activity 2. Let's go! 2.1 General Commands 2.2 Communication and Private Conversations 2.3 Channels and Public Conversations 2.4 Channel and User Modes 2.5 Client to Client Protocol 2.6 Network Related Commands 2.7 Quick Reference Panel 2.8 Further into ircII Wizardry 2.9 Sample .ircrc 2.10 Writing Automatons 3. Frequently Asked Questions 3.1 How do I set up an IRC client? 3.2 Which server do I connect to? 3.3 What are good channels to try while using IRC? 3.4 How do I get nifty effects with ircII? 3.5 What if someone tells me to type something cryptic? 3.6 I get strange characters on my screen, what are they? 3.7 What about NickServ? 3.8 I'm being flooded and harassed by a jerk. Help! 3.9 How do I get rid of a ghosted IRC session? 3.10 About KILL usage. 3.11 Where can I find more? 4. Administrativia 4.1 Revision history 4.2 Release sites for the IRCprimer 4.3 Copyright (C) 1993 Nicolas PIOCH 4.4 Credits List of Tables ~~~~~~~~~~~~~~~ Table 1: Editing keys Table 2: Editing commands Table 3: Simple screen activity Table 4: General commands Table 5: Private conversation commands Table 6: Channel commands Table 7: Mode commands Table 8: Channel modes Table 9: User modes Table 10: Client to client commands Table 11: Network related commands Table 12: Setting environment tables Table 13: Environment variables Table 14: Advanced commands Table 15: FTP sites with IRC clients Table 16: Open telnet IRC clients Table 17: Open IRC servers Table 18: Highlighting ircII output Table 19: Nordic countries character translations Table 20: IRC related mailing lists Table 21: IRCprimer release sites 1. GETTING STARTED ================== 1.1 Clients and Servers ~~~~~~~~~~~~~~~~~~~~~~~~ IRC (original code was written by Jarkko Oikarinen) is a multi-user, multi-channel chatting network. It allows people all over the internet to talk to one another in real-time. It is a functional replacement and improvement to 'talk'; 'talk' is an old, primitive, atrocious, minimalist sort of keyboard/screen conversation tool, using a grotesque, machine- dependent protocol (blah!). IRC does everything 'talk' does, but with better protocol, allowing more than 2 users to talk at once, with access across the aggregate Internet, and providing a whole raft of other useful features. Um IRC zu starten. loggt Ihr Euch also am idefix in Euren account ein, und dann tippt Ihr einfach "irc" (klein geschrieben, UNIX ist case-sensitive), und schon geht die Post ab (bezglich obelix weia ich nicht, ob es IRC auch da geben wird, aber wenn, dann startet Ihr es genauso, einfach mit "irc" ;). If you wish to be known by a nickname which is not your login name, type "irc nickname" instead. Each IRC user, ("client"), chooses a nickname. All communication with another user is either by nickname or by the channel that they or you are on (more information about channels later on). Als Beispiel sei hier also "irc Fingwe" erwaehnt, dies startet IRC mit dem nickname Fingwe. The most important thing to remember about IRC is that you have to be willing to explore and learn to use it... Take your time, try not to get flustered, enjoy yourself, and you will soon be making new friends all over the world! IRC is based on a client-server model. Clients are programs that connect to a server, a server is a program that transports data, (messages), from a user client to another. There are clients running on many different systems, (Unix, emacs, VMS, MSDOS, VM...), that allow you to connect to an IRC server. The client which will be spoken of here is the most widespread: ircII, (originally designed by Michael Sandrof). Other clients are similar, and often accept ircII commands. 1.2 How to behave on IRC ~~~~~~~~~~~~~~~~~~~~~~~~~ The most widely understood and spoken language on IRC is English. However, as IRC is used in many different countries, English is by no means the only language. If you want to speak some other language than English, (for example with your friends), go to a separate channel and set the topic to indicate that. On the other hand, you should check the topic before you move to a channel to see if there are any restrictions about language. On a non-restricted channel, please speak a language everybody can understand. If you want to do otherwise, change channels and set the topic accordingly. It's not necessary to greet everybody on a channel personally. Usually a "Hello!" or equivalent is enough. And don't expect everybody to greet you back... On a channel with 20 people that would mean one screenful of hellos. It's sensible not to greet, in order not to be rude to the rest of the channel. If you must say hello to somebody you know, do it with a private message. The same applies to goodbyes. Stimmt nicht ganz. Ihr werdet selbst merken, dass Begruessungen auf Kanaelen sehr wohl persoenlich sind und private messages sich ohnedies von slebst entwicklen, wenn Ihr also in einen Kanal hineingeht und schon bekannt seid, dann kommt es sicher vor, dass jemand, der Euch schon bessser kennt "HHAAALLLLLOO !!!!!! ......." schreibt. Das ist weder unhoeflich noch unerwuenscht, es sei denn es artet in eine Art von flood aus ;) Also note that using your client facilities, (ircII "ON" command for instance), to automatically say hello or goodbye to people is extremely poor etiquette. Nobody wants to receive autogreets. They are not only obviously automatic, but even if you think you are polite you are actually sounding insincere and also interfering with the personal environment of the recipient when using autogreets. If somebody wants to be autogreeted on joining a channel, he will autogreet himself. Voellig richtig. /on join * say Hello $0 ist ein Schwchsinn. Jedesmal, wenn jemand in den Kanal kommt "Hallo ...." zu sagen ohne es zu tippen, ist wirklich nicht die feine Art.... Remember, people on IRC form their opinions about you only by your actions, writings and comments, so think before you type. If you use offensive words, you'll be frowned upon. Do not "dump" to a channel or user, (send large amounts of unwanted information). This is likely to get you kicked off the channel or killed off from IRC. Dumping causes network "burps", connections going down because servers cannot handle the large amount of traffic anymore. Other prohibited actions include: * Harassing another user. Harassment is defined as behavior towards another user with the purpose of annoying them. Fuehrt dazu, dass der betreffende Stoerenfried gekillt wird (kill'en bedeutet, dass der client des users von seinem server abgehaengt wird.). Eine andere Moeglichkeit bestuende jedoch in dem recht effektiven "ignore" command (siehe spaeter). * Annoying a channel with constant beeping. Macht eh fast keiner, wenn jemand wirklich nerven will, findet er/sie andere Wege... * Any behavior reducing the functionality of IRC. Zum Beispiel (siehe ebenfalls spaeter): mode-floods, massdeops, floods... 1.3 Privacy on IRC ~~~~~~~~~~~~~~~~~~~ You should always keep in mind that messages you send to someone over IRC are passed along all the servers between you and and the person you are writing to. When you're sending a letter to someone, any postman on the way could open it and read its contents... Well, it's the same on the network. Any IRC-Admin could compile its server in "debug" mode and log whatever messages are transmitted through his node, (it has already been done), so a good thumb rule is not to trust the servers. Habe ich nicht gemacht, also keine Sorge diesbezueglich :-) +-------------------------------------------+ | IRC IS NOT A SECURE WAY OF COMMUNICATION! | +-------------------------------------------+ Stimmt, aber wer macht sich schon die Muehe (und wer hat schon die Zeit), sich stundenlang logfiles anzusehen, wer was gesagt hat und welche Konsequenzen sich daraus ergeben. Bringt ja niemandem wirklich was. How to establish direct communications between clients will be explained later, (see DCC CHAT in section 2.5). This should be used when you wouldn't want anybody else on IRC to intercept your private messages. 1.4 First Steps ~~~~~~~~~~~~~~~~ Note: ircII, the client most people are using, has most of this information online. Und zwar in der Form von sogenannten (ro)bots. Wenn also niemand persoenlich Hilfe geben kann, dann macht eifach folgendes: /msg help_uk help oder /msg help_uk msg. Das fuehrt dazu, dass Ihr a) einen Uberblivck ueber die verfuegbaren Themen oder b) Hilfe zu dem Befehl "msg" erhaltet. Hat ein Befehl Parameter (zum Beispiel dcc), dann zeigt ein /msg help_uk dcc chat Hilfe fuer konkret den Parameter "chat" des Befehls dcc an. Statt help_uk koennt Ihr auch "help_us" oder "help_eu" versuchen :-), ich glaube aber, dass die uk-Hilfe am oeftesten online ist... +------------------------------------------------+ | All ircII commands begin with a "/" character. | +------------------------------------------------+ The slash is the default command character. Commands are not case sensitive, and can be abbreviated to their first letters: "/SI" and "/sign " stand for /SIGNOFF and will both end your IRC session, (more in section 2.1). Anything that does not begin with "/" is assumed to be a message to someone and will be sent to your current channel, or to a person you are QUERYing, (the QUERY command will be detailed later on, maybe even section 2.2). Seid Ihr Euch nicht sicher ueber die exakte Schreibweise, so hilft Euch folgendes weiter: /w und der folgende output zeigt Euch alle Kommandos, welche mit "w" beginnen :-) (/a alle mit a usw...;) /W *** Commands: *** WAIT WALL WALLOPS *** WHICH *** WHILE WHO WHOIS *** WHOWAS *** WINDOW *** Aliases: *** W This is an example. Your screen may show more aliases, and less commands than shown here, or less aliases and more commands - in other words "your mileage may vary"... 1.5 Screen and Keyboard activity ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IRC is a full-screen utility. It takes over the screen, with the bulk of activity happening in the top (N-2) lines, a status line, (vaguely emacs- like), on the next to last line, and your input being entered on the last line. When typing commands at ircII, you have a minimalist line-editing facility in an emacs style. Table 1: Editing keys ---------------------- Key Effects ~~~ ~~~~~~~ ^P recalls previous command line ^N recalls next command line ^F moves forward one character ^B moves backward one character ^A moves the cursor to the beginning of the line ^E moves the cursor to the end of the line ^D deletes the character under the cursor ^K kills from the cursor to the end ^Y reinserts the last stretch of killed text ^U clears the whole line ^L redraws the screen Table 2: Editing commands -------------------------- Keyword Action ~~~~~~~ ~~~~~~ ! recalls previous commands for re-editing HISTORY displays the command history LASTLOG lists the most recent messages CLEAR puts some white space on your screen The ! command is used to recall previous commands in your command history for re-execution. The ! command is unique in that when it is used, it leaves the matching history entry in the input line for re-editing. You can specify a history entry either by its number in the history list, or by a match with a given wildcard expression. For instance, "/!10" will put entry 10 in the history list into the input line. "/!/MSG" will search the history for a line beginning with a /MSG, (a "*" is implied at the end). /![|] Recalls previous commands for re-editing. | kommt von der Programmiersprache C und bedeutet soviel wie "oder", das heisst also, das Ihr entweder die number oder die mask eingeben muesst :) The command history can be dumped using: /HISTORY [] Displays the command history on the screen. You can specify the number of history entries you wish to view as well. Almost everything happens in the upper bulk of the screen. This includes both messages from other users as well as the output of the control commands. Normal messages from other users appear with the originating nickname in . Private messages arrive with the originating nickname in *asterisks*. Messages you send to everyone appear with a preceding "> " whereas messages you send privately to another user appear with "-> *nickname*". Other output (invitations from other users to join channels, and so forth), appears interspersed with other activity on the screen. Table 3: Simple screen activity -------------------------------- What is displayed What you typed Sender Recipients ~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~ ~~~~~~ ~~~~~~~~~~ > Morning people Morning, people You Channel hello some1else Channel -> *some1else* hi! /msg some1else hi! You some1else (only) *some1else* wassup? some1else You (only) Last ircII outputs can be recalled with: /LASTLOG [| []] Displays the contents of the lastlog. This is a list of the most recent messages that have appeared on the screen, useful if you inadvertantly miss messages. If no arguments are given, the entire lastlog is displayed. If the first argument is a number, it determines how many log entries to show. Otherwise it is searched for in every lastlog entry. The second argument determines how many lines back to start display from. Example: /LASTLOG > Public message I send to all in the channel Public message from some1else *some1else* Private message sent to me by some1else -> *some1else* Private message I send to some1else Finally, if your screen gets garbage from a 'talk', 'write', 'wall' or any other form of primitive communication (smirk), hit ^L to redraw it, or CLEAR it. /CLEAR Clears the screen. 2. LET'S GO! ============ 2.1 General Commands ~~~~~~~~~~~~~~~~~~~~~~ Table 4: General commands -------------------------- Keyword Action ~~~~~~~ ~~~~~~ NICK changes your nickname QUIT exits your IRC session, (same as BYE, SIGNOFF and EXIT) HELP prints help on the given command WHOIS displays information about someone WHOWAS displays information about someone who just left AWAY leaves a message saying you're not paying attention /NICK [] Changes your nickname to whatever you like. Everyone who wants to talk to you sees this name - also, at the moment, nicknames are limited to 9 characters max. Your nickname will be the same as your login name by default. You can also set an environment variable, IRCNICK, the value of which will be used instead. Nickname clashes are not allowed; this is enforced by the servers. If your intended nickname clashes with someone else's as you enter IRC, you will not be able to enter until you change it to something else. Environment variables funktionieren nicht immer, am idefix habe ich es noch nicht ausprobiert. Es ist aber ohnedies genauso einfach moeglich, wenn Ihr in Euere .ircrc (siehe spaeter) einen Eintrag macht der folgendermassen aussieht: /nick your_preferred_nick Dies startet irc dann wie der Befehl "irc y_p_n", nur dass es Euch die ewige Tipperei erspart. /NICK Nappy *** Nap is now known as Nappy /QUIT [] Exits your IRC session. You can also use BYE, SIGNOFF and EXIT. If a reason is supplied, it is displayed to other people on your channels. /QUIT Lunch Time! *** Signoff: Nappy (Lunch Time!) idefix> (oder wie immer das prompt dort aussieht ;) /WHOIS [] Shows information about someone. /WHOIS Fingwe *** Fingwe is lorenz@olymp.wu-wien.ac.at (Work + IRC - that rhymes!) *** on channels: @#EU-Opers @#vienna @#talk #romance #hotsex (<-selten ;) *** on IRC via server olymp.wu-wien.ac.at ([137.208.8.30 6666] Austria, Vienna (Europe?)) *** Fingwe is an IRC Operator *** Fingwe has been idle 10 second(s) Im Falle, dass ein user gerade "away" (s. spaeter) ist, kommt noch eine Zeile hinzu, mit der betreffenden away-message. Die idle-time Anzeige erscheint ueberdies nur dann, wenn der user denselben server benutzt wie der/diejenige, welcher das Kommando /whois verwendet hat. /WHOIS Nappy *** Nappy: No such nickname Sometimes WHOIS won't help you much, because the person you want to know more about just left IRC or changed nick. However, you can use WHOWAS to get this information for a while: Fuer wie lange dieses "for a while" ist, ist server abhaengig, olymp ist auf 800 seconds engestellt. /WHOWAS [[] ] Shows information about who used the given nickname last, even if no one is currently using it. /WHOWAS Lenz *** Lenz was strasser@micromegas.wu-wien.ac.at (Big Mama) *** on channel *private* *** on IRC via server olymp.wu-wien.ac.at (.....) *** Signoff: Mon Nov 15th 20:10:22 Very often, an unsuccessful call to WHOIS will lead you to try WHOWAS. That's why ircII allows you to "/SET AUTO_WHOWAS ON"; that way, a "*** : No such nickname" message will automagically generate a "/WHOWAS ". Try typing "/msg help_uk help set auto_whowas, um mehr herauszufinden :-) Am olymp funktioniert das nicht. Liegt also entweder am client oder am server, ich vermute eher ersteres, da der server fehlerlos compiliert hat, manche clients aber nicht immer 100%ig kompatibel sind. /AWAY [] Leave a message explaining that you are not currently paying attention to IRC. Whenever someone sends you a MSG or does a WHOIS on you, they automatically see whatever message you set. Using AWAY with no parameters marks you as no longer being away. /AWAY Gone to get a cup of coffee. *** You have been marked as being away /AWAY *** You are no longer marked as being away 2.2 Communication and Private Conversation ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Table 5: Private conversation commands -------------------------------------- Keyword Action ~~~~~~~ ~~~~~~ MSG sends a private message QUERY starts a private conversation NOTICE sends a private message NOTIFY warns you of people logging in or out IRC IGNORE removes output from specific people off your screen You can use the MSG command, (usually "M" is an alias for it), to send someone a message that only that person can read. /MSG | Send a private message to specified nickname. /MSG Fingwe This message is for Nap only. -> *Fingwe* This message is for Nap only. On my screen will appear: *YourNick* This message is for Nap only. If you want to send a private message to more than one person, you can specify a list of nicknames separated by commas, (no spaces). /MSG Nap,Sorg This message for both Nap and Sorg. -> *Nap* This message for both Nap and Sorg. -> *Sorg* This message for both Nap and Sorg. Two special case nicknames are defined. If the nickname is "," (a comma), the message is sent to the last person who sent you a MSG. If the nickname is "." (a period), the message is sent to the last person to whom you sent a message. You can have a private conversation by only using /MSG. However, typing "/MSG " or "/MSG . " gets cumbersome. That's where the /QUERY command comes in handy. /QUERY [|] Starts a private conversation with . All text you type that would normally be sent to your channel now goes to the supplied nickname in the form of MSGs. To cancel a private conversation, use QUERY with no arguments. /QUERY Nap *** Starting conversation with Nap Blahblahblah -> *Nap* Blahblahblah /QUERY *** Ending conversation with Nap There is also another command to send messages, called NOTICE. Unlike MSGs, NOTICEs are surrounded by '-' when printed, and no automated responses, (such as generated by IGNORE or an automaton), will be sent in reply. Services, (robots), on IRC often use this form of interaction. /NOTICE | Sends a private message to the specified . /NOTICE Fingwe Better use /MSG instead of /NOTICE. -> -Fingwe- Better use /MSG instead of /NOTICE. On my screen will appear: -YourNick- Better use /MSG instead of /NOTICE. As you begin to make new friends over IRC, you'll want to mark certain nicknames such that you will be warned when they signon or off. /NOTIFY [[-]] Adds or removes to the list of people you'll be warned when they enter or quit IRC (in ircII versions prior to 2.2, too many people in the NOTIFY list cause excessive slowness). /NOTIFY Fingwe AlcBottle Chaotix *** Signon by Fingwe detected /NOTIFY *** Currently present: Fingwe *** Currently absent: AlcBottle Chaotix Der client, den Ihr verwendet ist version 2.2.9, also keine Sorge bezueglich zu vieler notified nicks (ich habe circa 20 nicks in meiner notify Liste, und es werden staendig mehr, aber von geringerer speed ist nichts zu merken :-). Wichtig ist beim notify Kommando, dass *nur* der nick registriert wird, und das es oft vorkommt, dass verschiedene Personen den gleichen nick benutzen, kann dies oft zu Verwirrungen fuehren, wenn Ihr gleich munter drauflos-messaged, aber jemand ganz anderer hinter dem betreffenden nick steckt. Zu diesem Zwecke entweder immer ein /whois nick machen, um festzustellen, ob der/diejenige wirklich der/diejenige ist, mit dem Ihr Euch unterhalten wollt oder einscript sleber schreiben oder von mir eine fertige Kopie verlangen ;) Eventually, you may wish some day not to see messages from a specific user on your screen. This may happen when someone is dumping large amounts of garbage, or if someone is harassing you. The proper response to such a behavior is to IGNORE that person. IGNORE is a very powerful command, and can be used in many ways. However the basic usage of this tool is the following. /IGNORE [| [[-]]] Suppresses output from the given people from your screen. IGNORE can be set by nickname or by specifying a userid@hostname format. Wildcards may be used in all formats. Output that can be ignored includes MSGs, NOTICEs, PUBLIC messages, INVITEs, ALL or NONE. Preceding a type with a "-" indicates removal of ignoring of that type of message. /IGNORE *@olymp.wu-wien.ac.at ALL *** Ignoring ALL messages from *@olymp.wu-wien.ac.at Fuer den Fall, dass Euch mein Geplapper nimmer interessiert :) /IGNORE *** Ignorance list: *** *@olymp.wu-wien.ac.at ALL /IGNORE *@olymp.wu-wien.ac.at NONE *** *@olymp.wu-wien.ac.at removed from ignorance list 2.3 Channels and Public Conversations ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On IRC, there are a lot of places where you can "hang out"; those places are called 'channels'. You can compare a channel to a conversation among a group of people: you see/hear everything that is said, and you can reply to anything that's said. What you type is received by everyone who's willing to listen - and everyone who is late will not hear what was said before, unless repeated by one of the ones who were there. (Who said "real life" :) All channels on IRC have names: a "#" sign followed by some kind of text- string, like "#C++" or "#Asians" or "#EU-Opers". Usually, the name of the channel will indicate the type of conversation that's going on in there. Don't count on it, though. Wie wahr, wie wahr. Weder #sex, noxh #hotsex noch #romance enthalten meistens Themen, welche den channel-name beruecksichtigen. Anders mag es sein mit channels wie #lesbian (aber bitte, dass weiss *ich* doch nicht :). Table 6: Channel commands -------------------------- Keyword Action ~~~~~~~ ~~~~~~ LIST lists channels, number of users, topic NAMES shows the nicknames of the users on each channel JOIN sets your current channel, (same as CHANNEL) WHO gives a listing of users INVITE sends an invitation to another user LEAVE leaves a channel, (same as PART) KICK gets rid of someone on a channel TOPIC changes the topic of the channel ME sends anything about you to a channel or QUERY DESCRIBE sends anything about you to a person or channel Every channel has certain characteristics, called channel modes. These will also be explained below. Recall the NAMES and LIST commands; they will show you the names of the existing channels. /LIST [[] ] Lists all current "channels", number of users, and topic. The displayed list may be quite long, so you can limit it using flags. "/LIST -MIN n" for instance removes channels with less than 'n' users of the output. Example: /LIST -MIN 5 *** #aussies 5 *** #amiga 5 Daily Amiga Silence...join&enjoy *** #hottub 21 Imagine sky, high above... *** #tuebingen 11 Happy Borthday CHUCK!!! *** #Christian 6 Jesus! *** #Twilight_ 15 The Oper Bar & Grill *** #initgame 5 More players needed!!!!!!!!!!!! *** #Taiwan 8 Welcome good friends. *** #espanol 6 EMERGENCIA SE Necesitan Mujeres! *** #sherwood 7 *** #francais 6 on apprend le japonais (japanese welcome) Channel names duerfen laenger als 9 Buchstaben sein, aber es werden nicht mehr angezeigt, um eine solchen Kanal zu joinen, muesst Ihr seinen richti- gen Namen herausfinden, also zum Beispiel /list twilight* *** #Twilight_Zone .... Dann wisst Ihr, dass Ihr mit /join #twilight_zone in den Kanal hinein- kommt. /NAMES [[] ] Shows the nicknames of all users on each "channel", (these may be very long. Remember to filter them with "-MIN n" or "-MAX n"). In der Regel sind immer 1500-3200 user am IRC (peaks: unter der Woche, von 8pm-6am, throughs: Wochenende). Das heisst, dass einen ganz schoene Flut von Namen bei enem /names alleine auf Euch zukommt. Das kann dazu fuehren, dass Euch der server raussschmeisst oder der cleint steckenbleibt. Mehr als 8000 Zeichen client flood erlaubt kein server (olymp hat 8000), und wenn Ihr Pech habt und 8000 als einzige(r) sendet, ohne dass jemand anderer am server taetig ist (kommt selten vor jedoch), fliegt Ihr raus, abgesehen davon, dass /names nicht wirklich etwas bringt....:-) /NAMES -MIN 5 Pub: #twilight> Mycroft @sojge scorpio @Troy @Avalon @Nap phone Merlinus Lumberjak @tzoper Pub: #espanol Cacique Bonjovi leopardo Carina Miguel Cisco r2 Pub: #amiga @gio @Radix @xterm @mama @AmiBot Pub: #aussies @Bleve @GrayElf @Insomniac @Morkeleb @titus Pub: #hottub baby @Aldur KnightOrc @Toasty Gwydion @Belkira @Aiken Edge @Spockobot @Nada @ZBot @Aurik @anna @RedBaron @Katzen @esashi IceWolf @Eniigma @Digger @TheHeck To join in the conversation on a certain channel you may use the JOIN command. /JOIN [] Sets your current channel to the supplied channel. /JOIN #Twilight_Zone *** Blubber has joined channel #Twilight_Zone *** Topic: The Gernsback Continuum *** Users on #Twilight_Zone: Nap msa tober phone @julia @SirLance igh @Daemon @Avalon @Waftam @Trillian @tzoper The CHANNEL command has the same effects. Note that if no parameters are given, your current channel is displayed. Upon entering a channel, you are given useful details about it: list of users talking in that channel, topic... Joining a channel does not cause you to leave your previous channel unless NOVICE is set to ON. Once in a channel, you may wish to get a detailed list of the people IRCing inside. That's where the WHO command comes in handy: /WHO [|] Gives a listing of users. "/WHO *" for the list of users in your current channel. /WHO #Twilight_Zone Channel Nickname S User@Host (Name) #Twilight_ Fingwe H* BigMama@micromegas.wu-wien.ac.at (Big Mama) #Twilight_ msa H msa@tel1.tel.vtt.fi (Markku Savela) #Twilight_ tober H ircuser@kragar.eff.org (tober) #Twilight_ phone H mrgreen@munagin.ee.mu.OZ.AU (Third row...) #Twilight_ julia G*@ julie@turing.acs.Virginia.EDU (Future...) #Twilight_ SirLance G*@ lancelot@tdsb-s.mais.hydro.qc.ca (Sir Lan..) #Twilight_ igh G igh@micom1.servers.unsw.EDU.AU (igh) #Twilight_ Daemon G*@ frechett@spot.Colorado.EDU (-=Runaway D.-=) #Twilight_ Avalon H*@ avalon@coombs.anu.edu.au (Avalon...) #Twilight_ Waftam G*@ danielce@munagin.ee.mu.OZ.AU (Daniel C.) #Twilight_ Trillian G*@ hrose@rocza.eff.org (I turn to stone when..) #Twilight_ tzoper H*@ tzoper@azure.acsu.buffalo.edu (/msg tzoper) The first field is the current channel, then nickname, status, real name (in internet user@host form), and a small witty comment you can set yourself with the environment variable IRCNAME, (this will be detailed in section 2.8). Status indicates if a user is "H"ere or "G"one, (see AWAY), if IRCop ("*"), and/or chanop ("@"). It is also possible, when you are already on a channel, to ask someone to join your channel. The command is called INVITE. /INVITE [] Invites another user to a channel. If no channel is specified, your current channel is used. Das ist server/client -abhaengig. Ohne channel Spezifizierung kann auch: *** No channel supplied (oder so aehnlich) vorkommen. /INVITE Lenz *** Inviting Nap to channel #Twilight_Zone If you receive an INVITE message, you can type "/JOIN - INVITE" to join the channel to which you were last invited, or simply "/JOIN ". To leave a channel, just issue a LEAVE command, (PART has the same effects): /LEAVE Leave a channel. /LEAVE #Twilight_Zone *** FIngwe has left #Twilight_Zone Auch hier gibts einenalias, der Euch erlaubt, mit /lv den channel zu verlassen, ohne den channel name anzugeben. Well, you guessed it, if there is a way to invite someone on a channel, there's also the possibility to KICK someone out of it, for example if this person is behaving like a jerk, annoying people or flooding the channel with unwanted information: /KICK [] Kicks named user off a given channel. Only 'channel operators' are privileged to use this command. /KICK #Twilight_Zone Target *** Target has been kicked off channel #Twilight_Zone by Fingwe /alias k kick $C $0 $1 $2 $3 $4 $5 $6 $7 $8 $9 ware ein einfacher alias, mit derm Ihr den folgenden Effekt erzielen koennt: /k Fingwe get outa here, loser *** Fingwe has been kicked off channel #Twilight_Zone by (get outa here, loser) Channels have topics, that indicate the current topic of conversation. You can change this topic on a channel with the TOPIC command. /TOPIC [[] ] Changes the topic for the channel. Eine channel Angabe ist nur dann noetig, wenn Ihr auf mehr als einem Kanal seid :-) /TOPIC The silent channel. *** Nap has changed the topic on channel #EU-Opers to The silent channel. At times, you may want to send a description of what you are doing or how you are feeling or just anything concerning you to the current channel or query. It is absolutely good style to not forget the period at the end of the sentence! Najo, den Punkt am Ende sieht man eigentlich selten, aber ich bin ja stark kurzsichtig, also vielleicht...:) /ME Tells the current channel or query about what you are doing. /ME opens up the fridge. * Fingwe opens up the fridge. You can also use your own nickname as command, i.e. you can type the line with a preceeding slash: /Fingwe reaches out for the orange juice. * Fingwe reaches out for the orange juice. The same goal can be achieved towards a specific nickname using: /DESCRIBE | Sends anything concerning you to the or you pass as first argument. (Note: The look of the result depends on each client version, and might not be exactly the same as in the examples shown here.) These commands make use of CTCP, a client-to-client protocol crafted to perform specific actions, but not understood by all clients, (more about CTCP in section 2.5). If you get an error message, your description may not have arrived properly. 2.4 Channel and User Modes ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Channels can have additional constraints, which can be set by the MODE command. To understand this, recall that the first person to JOIN a channel effectively creates it and is initially "in charge" of the channel, ("Channel Operator" or "chanop"). He/She can subsequently add those constraints, make other people chanops at leisure. Hier scheiden sich jetzt ungluecklicherweise die Geister. Natuerlich ist es wahr, dass derjenige, der als erster den Kanal join'ed, auch als einzi- ger channel operator ist, nud mehr oder weniger frei verfuegen kann, wer hineindarf, wer noch channelop wird usw. ABER: Alleine plaudert sichs recht schwer, und aus Gruenden, welche ich spaeter noch erwaehnen werde, ist es sinnvoll, mehr als nur einen channelop zu haben. Im uebrigen - und dies ist oftmals Thema zahlreicher Kontroversen - bin ich der Ansicht, dass channels nicht besitzt werden koennen. Zumindest nicht bei einzelnen Personen auf dem Kanal mehr als durch andere auf dem Kanal. Es gibt einige Leuterln am IRC, die meinen, sie haetten ein An- refcht auf bestimmte Ka- naele und koennten tun und lassen (nicht nur mit dem Kanal, sondern auch mit anderen), was ihnen so in den Sinn kommt. Sowas ist in meinen AUgen aeusserts laestig und user dieser Sorte verursachen nicht selten grosse Probleme, wenn sich andere in Ruhe unterhalten wollen, es aber nicht koen- nen, weil sie staendig gekickt werden usw...:( Sollte irgenjemand Probleme mit solchen Leuten haben, dann ist es das vernuenftigste, enteweder einen anderen channalop zu bitten, diesen Unsinn zu beenden oder gleich einen IRC-Op zu kontaktieren. Und nocheinmal: Channels are not owned. Jeder, solange er nicht alle be- laestigt, hat ein Recht, in dem Kanal zu sein und sich zu amuesieren. Ich betone das so ausdruecklich, weil in letzter Zeit oft Probleme in dieser Richtung aufgetaucht sind. Wenn jemand anderer Meinung ist, steht dies natuerlich jedem frei (was sonst), aber speziell fuer grosse channels wie #talk oder #england ist das Oeffentlichkeitsprin- zip eine der obersten Regeln :-) Table 7: Mode commands ----------------------- Keyword Action ~~~~~~~ ~~~~~~ MODE changes channel or user mode Public is the default mode for a channel. When someone is on a public channel, he can be seen by all other users, (if his own user mode permits this, siehe +i user mode). Anyone can notice users on a public channel and join such a conversation. Private means that, although anyone can see members of such a channel, you can't tell what channel they are on unless you are already on that channel with them. They just appear as "Prv: *" in LIST or NAMES. Since the number of potential channels is in the billions, this is quite some security - all you give away is the acknowledgement that you're IRCing. If you are on a secret channel, someone who is not on the same channel can't even see that you are there. Your name does not show up in a LIST of active users. The only indication of your presence is that, when entering IRC, all new users are told that there are "NNNNN users on XXX servers and that bbb channels have been formed". If someone checks on all users and finds less than NNNNN of them, he knows that other people are hiding on secret channels. But a secret channel user still cannot be found except by brute- force checking through all channels, a hopeless proposition in the face of the huge number of possible channel names. Security through obscurity finally means something. /MODE | [[+|-] []] Allows channel operators to change channel mode, or any user to change their personal mode, (don't use this command too often, it floods the net with worthless information). Vollkommen richtig. ZU intensives Benutzen von mode-changes verursacht in der Regel lags und splits...(siehe spaeter). /MODE #Twilight_Zone +m *** Mode change "+m" on channel #Twilight_Zone by Fingwe /MODE Fingwe -i *** Mode change "-i" for user Fingwe by olymp.wu-wien.ac.at And this is how to give 'chanop' status to someone on the channel /MODE #Twilight_Zone +o sojge *** Mode change "+o sojge" on channel #Twilight_Zone by Fingwe A + or - sign determines whether the mode should be added or deleted. Channels can be moderated (only chanops can talk), secret, private, with a limited number of users, anonymous, invite-only, topic-limited, with a list of banned users... The MODE command also allows you to modify your personal parameters, your "user mode". You can check your usermode with the command "/MODE " or sometimes "/UMODE". Note that user mode +i may be the default on some servers, in order to protect privacy of users. This should not be seen as a problem, since any user can change his/her personal mode whatever defaults a server may set. Am olymp ist die default setting -i, das heisst nicht invisible. Das ist mit Absicht so gehalten, weil es selbst bei +i Mittel und Wege gibt herauszufinden, wer denn jetzt eigentlich auf dem server herumschwirrt. Ich persoenlich halte +i nicht fuer sehr sinnvoll, wenn jemand nicht gesehen werden moechte, dann kann er seinen mode slebst auf +i setzten oder in einen +p oder +s Kanal hineingehen... Table 8: Channel modes ----------------------- Als Beispiel verwende ich immer den Kanal #talk. ModeChar Effects on channels ~~~~~~~~ ~~~~~~~~~~~~~~~~~~~ b ban somebody, in "nick!user@host" form /mode #talk +b Fingwe!*@* bannet alle user, welche den nickname Fingwe verwenden. /mode #talk +b *!lorenz@* bannt alle user, deren userid lorenz ist, ohne Ruecksicht auf nick oder host. /mode #talk +b *!lorenz@olymp.wu-wien.ac.at bannt alle user, deren userid lorenz *und* host olymp.wu-wien.ac.at ist (in der Regel eh nur einer :-) (sehr effektiv in der Regel) /mode #talk +b *!*@* bannt alle. nicht nett. ;) /mode #talk +b Fingwe!lorenz@olymp.wu-wien.ac.at bannt Fingwe, sofern er userid lorenz und host olymp...hat. /mode #talk +b *!*lorenz@*.wu-wien.ac.at bannt alle user mit dem domain wu-wien.ac.at und userid *lorenz, das heisst alorenz, gdsfglorenz usw.... /mode #talk +b *!*@*.at bannt alle Oesterreicher. /mode #talk -b *!*@*.at unbann'd alle Oesterreicher :-) i channel is invite-only /mode #talk +i l channel is limited, users allowed max /mode #talk +l 30 m channel is moderated, (only chanops can talk) Sehr effektiv fuer den Fall, dass ein *nicht*channelop den Kanal flooded. Sobald der mode auf +m gesetzt ist, kann niemand, der nicht channelop ist, irgendetwas auf dem Kanal sagen. n external /MSGs to channel are not allowed /msg #talk hallo geht dann nicht mehr, wenn man nicht selbst gerade auf #talk ist. o makes a channel operator /mode #talk +o Fingwe p channel is private s channel is secret t topic limited, only chanops may change it Table 9: User modes -------------------- ModeChar Effects on nicknames ~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~ i makes yourself invisible to anybody that does not know the exact spelling of your nickname o IRC-operator status, can only be set by IRC-ops with OPER s receive server notices Fuer non IRC-Ops nicht zu empfehlen. Erzeugt nur eine Flut von uninteressanten (in der Regel) messages. w receive wallops (abused and deprecated) Wie wahr. Ist auch nicht zu empfehlen. 2.5 Client to Client Protocol ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /CTCP [] Allows you to perform certain client specific actions on the network. /CTCP Fingwe VERSION *** CTCP VERSION reply from Fingwe: ircII 2.2 *IX ircII 2.2, SL0 The one you thought you'd never see. This can be used to get information about how long a person has been idle: /CTCP Fingwe Finger *** CTCP FINGER reply from Fingwe: Irgenein Text - blabla (user@host) Idle 0 seconds Table 10: Client to Client Commands ------------------------------------ Keyword Action ~~~~~~~ ~~~~~~ CTCP performs certain client specific actions DCC handles direct connections to remote clients DCC SEND initiates a file transfer DCC GET accepts a file transfer DCC CLOSE ends a DCC connection or offer DCC LIST shows current DCC connections DCC CHAT initiates a secure chat between two clients There are many other CTCP commands, and new ones are introduced all the time. There is a mechanism for you to find out what you can use: CTCP CLIENTINFO. To find out about your own client services, execute a CLIENTINFO on yourself. /CTCP Fingwe CLIENTINFO *** CTCP CLIENTINFO reply from Fingwe: SED VERSION CLIENTINFO USERINFO ERRMSG FINGER TIME ACTION DCC UTC PING :Use CLIENTINFO to get more specific information. However the client-to-client protocol has a very powerful feature: Allowing two people to exchange files. To send small text files, electronic mail is probably the best solution, (don't rely on the user@host given by the WHOIS command to send mail. For people registered on NickServ, you can "/MSG NickServ@Service.de WHOIS nick" to get their E-mail address) (NickServ, nicht nickserv, zusammen mit NoteServ der einzige case-sensitive nick am IRC). However, ircII provides you a way to establish Direct Client Connections ("DCC") to perform functions like sending and receiving files. If NickA wants to send a file to NickB, then NickA should type: /DCC SEND NickB filename On NickB's screen will appear: *** DCC SEND (filename) request received from NickA If he, (NickB), wants to get the file, he just needs to type: /DCC GET NickA filename A few seconds later *** DCC GET connection with NickA established *** DCC GET filename connection to NickA completed will inform both users that data transfer has been successfully completed. Here's a quick overview of the subject: /DCC [] Handles direct connections to remote clients. The behavior of DCC is determined by the specified . /DCC SEND Initiates a file transfer by direct client connection. /DCC GET ^ccepts a file transfer by direct client connection. The sender must first have offered the file with DCC SEND. /DCC CLOSE [] Ends an unwanted DCC connection or offer. The , and must be the same as those shown by "/DCC LIST". If the arguments are not supplied, the oldest connection of the specified type is closed. /DCC LIST Shows current /DCC connections with their types, status and nicknames involved. However, if someone asks you to send him a file, DON'T do it unless you EXACTLY know what you are doing. For instance, NEVER send the password (nicht lache, ist schon passiert...) file of your system to anybody. This could grant crackers illegal access to your machines, and put you and your system administrator in much trouble. DCC also allows two clients to establish a direct client connection for chat. This is a secure form of communication, since messages are not sent through the IRC network. /DCC CHAT Initiates a direct client connection chat to the given nick, who must repond with DCC CHAT. Once established, messages are sent over with "/MSG =Nickname ...". 2.6 Network Related Commands ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you encounter any problem, contact your local IRC- Administrator or an IRC-Operator. An IRC-Admin is a person who has access to all files concerning 'ircd' (the server program). An IRC-Operator or "IRC-op" is a person who has privileges given to him by an IRC-Admin and tries to maintain a fast reliable IRC network. Information on how you can find out who he/she is, can be found below. Each time you are prompted for a server name, remember you can supply the nickname of someone being connected on that server instead. This may be useful at times... Table 11: Network related commands ----------------------------------- Keyword Action ~~~~~~~ ~~~~~~ ADMIN displays information about a server LINKS shows the servers on the IRC network SERVER switches your primary server MOTD displays the server message-of-the-day USERS prints users logged on the server machine DATE shows server current date and time TIME shows server current date and time LUSERS gives a brief listing of users, servers and operators TRACE shows the server connections of the given server STATS shows some irc server usage statistics INFO shows useless information about IRC VERSION shows client and server version number Mit Aunahme von /server werden alle server names (oder zumindest die meisten, so auch olymp) hostmasked, das heisst im Regelfall genuegt dann olymp* statt olymp.wu-wien.ac.at .... /ADMIN [] Displays the administrative details about the given server. If no server is supplied, the server you are connected to is used. /ADMIN olymp* ### Administrative info about olymp.wu-wien.ac.at ### University of IRConomics (Route 6666), Vienna, Austria (Europe?) ### Bernhard Lorenz (Fingwe on IRC), lorenz@isis.wu-wien.ac.at ### Admin Quitting - Brain dumped /LINKS [[] ] Shows a list of servers currently connected to the IRC network. If is given, /LINKS asks the given for a list of servers matching the given expression, (this list can get very long!). Stimmt. Fuer oesterreichische links also /links *at verwenden, ansonsten gibts wieder eine flood ;) /LINKS *po* *** nova.unix.portal.com 7 Cupertino California, USA *** poe.acc.Virginia.EDU 6 University of Virginia 2.7.1f *** polaris.utu.fi 9 University of Turku, Finland *** polaris.ctr.columbia.edu 6 Columbia University, New York City *** csd.postech.ac.kr 4 POSTECH Computer Science Dept. *** cdc853.cdc.polimi.it 2 Polytechnic of Milan, Italy *** poly.polytechnique.fr 0 Ecole Polytechnique, Paris, FRANCE /links *at *** itc.univie.ac.at 4 disuns2.epfl.ch *** uni-linz.ac.at 2 itc.univie.ac.at *** olymp.wu-wien.ac.at 0 olymp.wu-wien.ac.at /SERVER [| []] Switches your primary server to the supplied at the specified . If no port number is given, the default port number is used (normally 6667). Nicht vergessen, olymp ist auf port 6666, wenn jemand am undernet interessiert ist, dann ist port 6667 zu empfehlen ;-) /SERVER olymp.wu-wien.ac.at 6666 *** Connecting to port 6666 of server olymp.wu-wien.ac.at *** Welcome to the Internet Relay Network, Troll *** Your host is olymp.wu-wien.ac.at, running version 2.8.16 *** This server was created Sun Nov 14 1993 at 19:16:10 MET Occasionally, you can switch servers faster than the IRC network can send out the information that you have left your previous server. So don't be surprised if you are told your nickname is already in use... Just wait a moment and set it with /NICK again. Nicht nur das. Oftmals kommt auch ein *** You have been rejected by server ... (was einem Kill durch einen ser- ver gleichhkommt, passiert aber in der Regel nur bei splits, siehe spae- ter). /MOTD [] Gives the Message-Of-The-Day for the named server. If no server is given, your server is used. *** HIYA ....... *** ..... *** End of MOTD command. /USERS [] Shows the users logged into the machine where the server is running, (it's up to the server administrator to implement this feature or not. It may not work on some machines). Ich hatte es installiert, habs aber beim letzten compile vergessen. Sollte ich irgendwann dazukommen, werde ichs implementieren, aber im Grunde gehts ja niemandenwirklich etwas an, oder ;) /USERS *** UserID Terminal Host *** strasser ttyp9 olymp.wu-wien.ac.at *** gonter co olymp.wu-wien.ac.at *** root ttys1 olymp.wu-wien.ac.at *** lorenz ttyq1 olymp.wu-wien.ac.at /DATE [] /TIME [] Shows the current time of day and date. If a server is specified, the time of day and date are reported from that server. DATE and TIME are identical. Ich glaub der olymp geht eine Stunde nach :-) /LUSERS Gives a brief listing of the number of servers, operators and users matching the given , as seen from the specified . /LUSERS *** There are 2412 users and 560 invisible on 135 servers *** 72 users have connection to the twilight zone *** There are 987 channels *** I have 11 clients and 1 server /TRACE [] Shows the server connections of the given . /TRACE *** Serv Class[20] ==> 134S 3102C itc.univie.ac.at[131.130.39.27] *** Oper Class[5] ==> Fingwe[olymp.wu-wien.ac.at] *** Class 20 Entries linked: 1 *** Class 5 Entries linked: 1 *** Class 4 Entries linked: 8 *** Class 3 Entries linked: 2 *** Class 1 Entries linked: 1 /STATS c|i|k|l|m|u|y [] Shows some irc server usage statistics. /STATS u *** Server Up 12 days, 12:28:44 /stats c olymp* C:131.130.39.27::itc.univie.ac.at:6667:20 N:..... C:CISMhp.UNiv-Lyon1.Fr::....:6667:18 N:....... C:seal.micro.edu....... usw... Zeigt alles links an, die vom olymp aus theoretisch erreicht werden koenn- ten. /stats i olym* I:*.at::*.at:6666:5 I:*.de::*.de:6666:5 usw.... Zeigt alle hosts an, welche den olymp server verwenden koennen. Es exi- stieren keine Restriktionen, aber verschiedene Laender werden verschieden behandelt, um im Falle von lags keine Netzwerkverzoegerungen zu verursa- chen. /stats k zeigt die K: lines, das heisst alle user, nicks oder hosts, die partout NICHT am server erlaubt sind. /stats y zeigt die connection classes an (hier ist der Unterschied in den verschiedenen Laendern, je weiter weg, umso oefter wird gecheckt, ob der betreffende client auch noch wirklicch funktioniert...wenn nicht, fliegt er raus, automatisch). Fuer mehr Informationen zu /stats bin ich natuerlich gerne bereit, aber eine ausfuehrlichere Beschreibung wuerde den Rahmen dieser Einfuehrung noch weiter sprengen. /INFO [] Shows information about the IRC creators, debuggers, slaves and a lot of other people who no longer have much to do with IRC. /VERSION Shows the ircII version number and the version number of the server. /VERSION *** Client: ircII 2.2 *** Server olymp.wu-wien.ac.at: 2.8.16 2.7 Quick Reference Panel ~~~~~~~~~~~~~~~~~~~~~~~~~ Keyword Action ------- ------ ! recalls previous commands for re-editing ADMIN displays information about a server AWAY leaves a message saying you're not paying attention CLEAR puts some white space on your screen CTCP performs certain client specific actions DATE shows server current date and time DCC handles direct connections to remote clients DESCRIBE sends anything about you to a person or channel HELP prints help on the given command HISTORY displays the command history IGNORE removes output from specific people off your screen INFO shows useless information about IRC INVITE sends an invitation to another user JOIN sets your current channel KICK gets rid of someone on a channel LASTLOG lists the most recent messages LEAVE leaves a channel LINKS shows servers on the IRC network LIST lists channels, number of users, topic LUSERS gives a brief listing of users, servers and operators ME sends anything about you to a channel or QUERY MODE changes channel mode MOTD displays the server message-of-the-day MSG sends a private message NAMES shows the nicknames of users on each channel NICK changes your nickname NOTICE sends a private message NOTIFY warns you of people logging in or out IRC QUERY starts a private conversation QUIT exits your IRC session SERVER switches your primary server STATS shows some irc server usage statistics TIME shows server current date and time TOPIC changes the topic of the channel TRACE shows the server connections of the given machine USERS prints users logged on the server machine VERSION shows client and server version number WHO gives a listing of users WHOIS displays information about someone WHOWAS displays information about someone who just left 2.8 Further into ircII Wizardry ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Note: This part should be reserved for experienced IRC'ers. Because ircII is not a simple client program, but an Operating System, its programming language is just as simple as you could expect (it's horrendous), but if you want to get into it, here's a little note for you... There are a few Unix environment variables you can set in your shell configuration file, but you need to find out your shell name before that. "echo $SHELL" should give you a hint. tcsh meistens. am olymp glaub ich bourne. Table 12: Setting environment variables ---------------------------------------- Shell type Shell name Command ~~~~~~~~~~ ~~~~~~~~~~ ~~~~~~~ Bourne shells sh $ VARNAME="value" ; export VARNAME ksh $ export VARNAME="value" bash $ export VARNAME="value" C-shells csh % setenv VARNAME "value" tcsh > setenv VARNAME "value" Table 13: Environment variables -------------------------------- Name Effects ~~~~ ~~~~~~~ HOME where your home directory is IRCNAME any lunacy you want instead of your real name zum Beispiel (Get a Life - Only IRC is Real)... (text that appears between parentheses in a WHOIS) IRCNICK your default IRC nickname IRCPATH a directory path to LOAD scripts IRCRC a file to use instead of your $HOME/.ircrc IRCSERVER a default server list for ircII TERM your terminal type vt100 in der Regel (oder 102) The command character, (usually "/"), is only necessary when you type commands interactively, when you program things it is no more needed, it used to be though. Table 14: Advanced commands --------------------------- Keyword Action ~~~~~~~ ~~~~~~ # same as COMMENT except for the lenght @ performs variable expressions ALIAS creates command aliases ASSIGN creates user variables (expandable with $) BIND binds a keystroke sequence to a function CD changes ircII working directory COMMENT does nothing, but very useful. Strange, uh? Very. ECHO displays all of its arguments EXEC allows you to start subprocesses FLUSH flushes all pending output from the server IF standard boolean expression checker LOAD loads an ircII command script file ON sets up actions to occur when certain events happen REDIRECT forwards the output from a command SAVE saves all ircII settings into a file SAY same as sending text to a channel SEND same as sending text to a channel SET sets a variable to a given value SLEEP suspends ircII for a few seconds TYPE simulates keystrokes WAIT waits for all server output to finish WHILE another control command to make loops WINDOW lets you manipulate multiple "windows" in ircII XECHO like ECHO, but takes flag arguments If you want to type to the channel from within an ALIAS or on BINDing, you have to use SAY or SEND. The ";" has a special meaning in ALIASes, BINDings and ONs: it's treated as command separator, that means you can execute multiple commands in a row separated by semicolons. The semicolons are not considered separators when you use them interactively, (to be able to type ";-)"), and within an ircII script file. You can escape the meaning of ";" in an ALIAS with "\;". When you use ircII on a (semi)regular basis, you will discover that every time you start the program you will issue the same initialization sequence. If that is the case, I have good news for you: you don't have to do that anymore! ircII will, at startup, load a file called ".ircrc", (full path: $HOME/.ircrc). It will treat each line in that file as if you typed it manually. Also einfach ein file names .ircrc in Euer home dir stellen :-) For example, if the content of your .ircrc file is: /JOIN #Twilight_Zone then each time you will start IRC, you will join this channel. Advanced commands may come in handy if you need them. Feel free to browse in ircII online help to find out more about them. A few of them are probably worth learning... Fuer solche Arten von Kommandos koennt Ihr mir mail schicken oder mich am IRC selbst ansprefchen, ich schreibe diese Dinger nicht selbst, aber ande- re produzieren laufend herrliche Sachen :-) 2.9 Sample .ircrc ~~~~~~~~~~~~~~~~~~ Hier ist ein Teil meines .ircrc files, hoffe, es vermittelt ein paar Ideen :-) Alles, was nach dem eigentlich Befehl steht sollte nicht im .ircrc file stehen, in den meisten Faellen sind die Befehle ohnedies selbstredend, und Comments sind nur bei wirklich komplizierten scripts zu empfehlen :-) nick your_nick set NOVICE off Comment sorgt dafuer, dass Ihr mehr als nur einen Kanal joinen koennt set AUTO_WHOWAS on Comment geht irgendwie nicht :| alias w whois comment nur noch /w nick statt /whois nick alias q query alias m msg alias n notice alias j join alias lv leave $C alias o mode $C +ooo alias d mode $C -ooo alias k kick $C alias mo mode $C comment um irgendeinen mode zu veraendern. Sollten dies Dinger nicht funktionieren, dann schick ich Euch enie 100%ig funktionierende Version, es ist wieder einmal sehr vm client abhaengig... 2.10 Writing automatons ~~~~~~~~~~~~~~~~~~~~~~~~ An automaton, (also called robot or service), is a program that is connected to the IRC network to provide services. Many people try to set that up with a few ircII commands like: on ^msg "% help" notice $0 This is LameBot 1.0 However, you should know that setting up an automaton using ircII ON facilities is quick and dirty, and should be reserved for robots that rely on ircII specific features such as DCC (file servers for instance). Writing a program in C, perl or any decent programming language should take longer in the beginning, but your efforts will be rewarded. You can download skeletons of such programs on some ftp sites that keep IRC related stuff (check in the Frequently Asked Questions part). Although most robots-writers believe they have created a "smart thing", 99% of the robots online happen to be a nuisance to the IRC community, because a few simple rules were not respected by their owners. The main idea is that robots should neither be seen nor heard: Ich persoenlich neige dazu, 99% der bots als Mist zu betrachten, sie ueberfluten tatsaechlich IRC sinnloserweise, wer braucht schon 10 bots auf einem einzigen Kanal? ABer ich bin dagegen, dass sie +i gesetzt werden. Mir ist die Begruendung fuer +i schleierhaft, es gibt einen Haufen bots, die nur dazu da sind, channels zu ueberfluten oder Leute zu kicken und bannen, und wenn man dann mit /trace wissen will, woher die kommen, sieht man sie nicht, weil sie +i sind. Sinnlos, man kann sie dann naemlich nicht einmal mehr killen, und dann ist die Hoelle los. * automatons should be clearly identified as such, having "bot", "serv" or "srv" in their nickname. * they should use NOTICES to communicate with the rest of the world, and not reply to NOTICES they get. * they should be able to always be killed (craziness is a frequent disease among robots). * they should be able to be killed remotely by their owner via IRC. * they should not give access to their owner's real files, (bandits have already been able to crack people's accounts through their robots). * they should not send messages to channels (unless the channel is dedicated to that robot (Anm.: #poker, #initgame, #eliza)). * they should not flood channels with MODE changes. Basically, if you have such a command as: on -JOIN "Lamer #BotTub" mode #BotTub +o Lamer then you are wrong. Because this is what you will get: *** Lamer (clueless@where.the.hell) has joined channel #bottub *** Mode change "+o Lamer" on channel #bottub by LameBot *** Mode change "+o Lamer" on channel #bottub by StupidSrv *** Mode change "+ooo Lamer Lamer Lamer" on channel #bottub by FloodServ *** Mode change "+o Lamer" on channel #bottub by Dumbbot And this will get boring very soon, so don't be surprised if such robots get banned from most channels. A good kludge is to wait until someone asks explicitly the robot to be opped on a channel. Schoen waers. Mittlerweile siehts auf #talk in etwas so aus (und keiner kuemmert sich darum, obwohl es einigne auf die Nerven geht): *** Blabla (wer@is.denn.das) has joined channel #talk *** Mode change "+o Blabla" on channel #talk by Silvara *** Mode change "+o Blabla" on channel #talk by Audrey *** Mode change "+o Blabla" on channel #talk by MadBot *** Mode change "+o Blabla" on channel #talk by Kirash *** Mode change "+o Blabla" on channel #talk by Paladine *** Mode chande "-o Blabla" on channel #talk by Pawwis *** Mode change "+b *!wer@is.denn.das" on channel #talk by Pawwis *** Blabla has been kicked off channel #talk by Pawwis (lamer.) Leicht uebertrieben, aber solche Sachen haeufen sich :( Reduziert die Moeglichkeit, sinnvolle Gespraeche inmitten der zahllosen bots zu fuehren auf einklaegliches Minimum... This could be: on -MSG "Lamer op me on #BotTub" mode #BotTub +o Lamer If you don't respect rules 2 and 6 above, this may happen too: *** TalkBot (clueless@where.the.hell) has joined channel #bottub Hi TalkBot! Hello LameBot! How are you? *** Mode change "+o TalkBot" on channel #bottub by LameBot Fine thanx. Thank you for the op, LameBot. No problem, TalkBot. *** Signoff: Talkbot (ircserver.irc.edu where.the.hell) *** TalkBot (clueless@where.the.hell) has joined channel #bottub *** Mode change "+o TalkBot" on channel #bottub by where.the.hell *** Mode change "+o LameBot" on channel #bottub by TalkBot *** Mode change "+o TalkBot" on channel #bottub by LameBot Thank you for the op, LameBot. No problem, TalkBot. ... See? Remember the golden rule: Schoen, gell? Braucht man gar nimmer selbst kommuniziren, machen eh alles die robots fuer uns... 3. FREQUENTLY ASKED QUESTIONS ============================= 3.1 How do I set up an IRC client? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gar nicht, weil Gerhard Gonter schon alles erledigt hat und den client fuer alle am Idefix zugaenglich gemacht hat, was nicht nur toll ist, son- dern auch Platz spart :-) Table 16: Open telnet clients ------------------------------ Europe telnet ircclient.itc.univie.ac.at 6668 telnet ......co.uk weiss leider nicht genau, wie der heisst. telnet micromegas.wu-wien.ac.at, login:irc, passwd:garnix geschlossen, aber an sich braucht ja auf der WU eh niemand einen public client... 3.2 Which server do I connect to? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It's usually best to try and connect to one geographically close, even though that may not be the best. You can always ask when you get on IRC. Here's a list of servers available for connection: olymp.wu-wien.ac.at 6666 is der beste und schnellste im ganzen IRC (objek- tiv gesehen: olymp ist *einer* der schnellsten, ohne Frage :-) Table 17: Open IRC servers --------------------------- olymp.wu-wien.ac.at 6666 131.130.39.27 6667 uni-linz.ac.at 6667 csa.bu.edu 6667 (US) irc-2.mit.edu 6667 (US) Und noch ca. 140 andere :-) This is by no means, a comprehensive list, but merely a start. Connect to the closest of these servers and join the channel #Twilight_Zone or, if you are in Europe, #EU-Opers. When you are there, immediately ask what you want. Don't say "I have a question" because then everyone will ignore you until you say it a few times, and then they'll jump down your throat and rip your lungs out. No one knows if he can answer your question until you ask it. Sehr fein ausgedrueckt, leider wahr :( 3.3 What are good channels to try while using IRC? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ #Hottub and #initgame are almost always teeming with people. #Hottub is meant to simulate a hot tub, and #initgame is a non- stop game of "inits" (initials). Just join the fun and find out! (German users may try channels named after German university towns...) #talk, #england, #romance sind die Kanaele, die noch zu empfehlen sind, mehr als #hottub oder #initgame vielleicht (meiner Meinung nach). Many IRC Operators are in #Twilight_Zone, while European Operators concentrate in #EU-Opers... So if you join an Operator channel and don't hear much talking, don't worry, it's not because you joined, Operators don't talk much on such channels anyways! Ausser, wenn die Stunde schon fortgeschritten ist (manchmal :-) 3.4 How do I get nifty effects with ircII? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You can highlight messages you send using control chars: parts of text surrounded by control-b (^B) will appear in video reverse to most ircII users for instance. However the appearance of such effects relies on the terminal abilities of the user you're writing to. In some cases keys are already bound to something. For instance, ^B is normally bound to BACKWARD_CHARACTER, so you will need to define a "quote- character" key: just enter "/BIND ^W QUOTE_CHARACTER" then "/BIND ^W^B SELF_INSERT" and it may work... Ist alles client abhaengig. ctrl-b ist bold (highlighted) ctrl-v ist gelb (inverse) ctrl-_ ist rot (underlined) auf der AIX genuegt /bind ^b self_insert und schon funktiojniert bold :) 3.5 What if someone tells me to type something cryptic? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NEVER type anything anyone tells you to without knowing what it is. There is a problem with typing a certain command with the ircII client that gives anyone immediate control of your client, (and thus can alter your account environment also). Look in the ircII on-line help each time you can. Na ja, ganz so schlimm ist es auch nicht. Aber hin und wieder werden schon Scherze getriben, so ist zum Beispiel des oefteren als topic "/sign netball to play netball" zu finde...nix netball, beendet einfach irc, das ist alles...;) 3.6 I get strange characters on my screen, what are they? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IRC has quite a lot of people from Scandinavian countries, }{|][\ are letters in their alphabet (IRC is supposed to support the ISO Latin-1 8-bit character set, but your client must be able to display them...) This has been explained on IRC about a thousand and one times, so read the following, do not ask it on IRC: Table 19: Nordic countries character translations -------------------------------------------------- Character Description ~~~~~~~~~ ~~~~~~~~~~~ [, { 'a' with two dots over it ], } 'a' with a small circle above it \, | 'o' with two dots over it, or a dash ("/") through it ("[", "]", and "\" = upper case) In addition to that, Japanese IRC'ers use a special ANSI escape control sequences to transmit their Kanji alphabet. This may also look funny if you get some of it... Here's a sample: [$B$?$K$7[$B;$m$K# (nice, uh?) Very. 3.7 What about NickServ? ~~~~~~~~~~~~~~~~~~~~~~~~~ To quote from NickServ's help text, NickServ's purpose is to help avoiding nickname confusions on IRC. There's no such thing as "nickname ownership", however NickServ sends a warning to anyone else who signs on with your nickname. If you don't use IRC for 10 weeks, your nickname registration expires for reuse. Only a NickServ operator can change your NickServ password. To find out which NickServ operators are on-line, send /MSG NickServ@Service.de OPERWHO Nicknames with a "*" next to them are online at the time. 3.8 I'm being flooded or harassed by a jerk. HELP! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If somebody is behaving like a jerk on IRC, like dumping to a channel Mb's of garbage, then he should be KICKed and eventually banned from the channel, (see "/HELP MODE" for details). If it's a matter of personal harassment, then you should set a proper IGNORE on that person, (preferably on his userid@hostname). Remember you can use wildcard expressions for IGNORE. More about this in section 2.2. 3.9 How do I get rid of a ghosted IRC session? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Sometimes you may have a "ghosted" IRC session, a process still running on your machine you would like to get rid of, but can't control anymore to issue a QUIT command. Going back to a unix shell, try listing your processes: ("ps -x" system) PID TT STAT TIME COMMAND 2345 ttys6 S 1:12 irc ......... idefix:> kill -9 2345 Und weg ist der ghost. Getting an Operator to kill the ghost is almost never necessary, just sign on as another nickname and wait for the "Ping timeout" or "Bad link" message, then you can change your nick back... 3.10 About KILL usage. ~~~~~~~~~~~~~~~~~~~~~~~ KILL is a command restricted to IRC-Operators to deal with protocol errors heavily reducing the IRC network functionality. It's to be used with extreme caution, if at all. If you op someone on a channel, you take the consequences. If someone joins #Whatever, you op them, then they kick everyone and lock the channel with some "Mode change +ib *!*@*", then suffer it: it's your fault, don't go whining to an IRC-op to fix it. If a channel is locked, you should start a new one. Stimmt in Prinzip, aber wer ist schon gerne auf #talk2 an Stelle von #talk etc.? Oftmals hackern diese Leute auch ops, und dann kann man ja nicht mehr von "selbst schuld sprechen". Man muss den betreffenden user ja nicht gleich killen, ein bisschen Diplomatie wirkt oft Wunder :-) Effective methods to deal with obnoxious people are IGNORE, KICK and various MODEs on channels, such as +i and/or +b. If you have been abusively killed by an IRC-Operator, abusing his power to gain illegal channel-operator status for instance, yell! Mail a log to his server IRC-Administrator, (see ADMIN), join #Twilight_Zone or #EU-Opers for European-related problems, and explain what happened. Die europaeischen "kill-rules" sid restriktiver als die amerikanischen, in der Regel finden sich die europaeischen opers in den untersten Raengen der kills, die US-Opers haben mehr die Einstellung (obwohl man natuerlich nicht generalisieren darf), dass killen ja sehr lustig sein kann. Schade, denn killen ist genauso belastend fuer das Netz wie lags etc. 3.11 Where can I find more? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Should your question not be listed above, you may want to check the "Frequently Unasked Questions", (FUQ) list, which will be shipping real soon now, featuring replies to: Are there any good FTP sites? (1) How do I join a channel? How do I become an IRCop? lamer1: siehe Fussnote lamer2: no comment lamer3: O: line oder set up your own server (die Chancen, einen weiteren server in Wien aufzustelllen sind in etwa -10%, da jetzt in Wien bereits 2 server existieren (eine unglaubliche Ansammlung relativ zum uebrigen Netz gesehen und sogar noch ein drotter im Entstehen zu sein scheint ;). Und was O: lines betrifft, so glaube ich kaum, dass da etwas zu machen ist... If you have access to Usenet News, (usually through a program called rn, trn, xrn or nn), you may want to join alt.irc debates, flamings and whinings. You can also join various IRC related mailing lists. "Operlist" discusses current (and past) server code, routing and protocol. Mail operlist- request@eff.org to join. Another mailing list, ircd-three@eff.org exists to discuss protocol revisions for the 3.0 release of ircd, currently in planning. Mail ircd-three- request@eff.org to be added to that. There is also low-traffic mailing- lists for ircII vmsirc and irchat clients. Table 20: IRC related mailing lists ------------------------------------ E-mail for subscriptions What's being talked about ~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~ operlist-request@eff.org Server code, routing and protocol. ircd-three-request@eff.org ircd 3.0 protocol listserv@grasp1.univ.lyon1.fr European IRC-Operators mailing list dl2p+@andrew.cmu.edu ircII mailing list vmsirc-request@vax1.elon.edu VMS IRC mailing list irchat-request@cc.tut.fi irchat mailing list ((1) 129.0.0.1 but you already know that.) Nein, noch nie ausprobiert. Ich habs mir erst jetzt aufgeschrieben. Wahrscheinlich diverse binaries ;) 4.3 Copyright (C) 1993 Nicolas PIOCH ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This manual is free; 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 manual 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 manual; if not, write to the Moegllich. Irgendwo auf meinem olymp account liegt glaub ich so was. Wenns jemand tatsaechlich interessiert (fuer den Fall, dass er/sie ein eigenenes helpfile herausbringen will, dann sollte man vielleicht doch einen Blick drauf werfen.) Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. 4.4 Credits ~~~~~~~~~~~~ Eine Menge Leute, die ihren Teil zu diesem Script beigetragen haben. Paris, February 21, 1993, Ecole Polytechnique, Nicolas PIOCH. Das war also der erste (groesste) Teil des helpfiles. Jetzt moechte ich slebst noch ein paar Kleinigkeiten hinzufuegen, die Neuerungen und eventuell interessante Dinge enthalten, vor allem auch ein bisschen einen Blick hinter die Kulissen werfen sollen. Was tun gegen stoerende user? WIe bereits erwaehtn ist eine gute Methode, den betreffenden dodel einfach zu ignorieren mit /ignore *!user@host all Nicht immer fuehrt dies jedoch zum gewuenschten Effekt, da einerseits hacker in der Lage sind, andere accounts zu benutzen oder ein superuser einfach einen anderen account anlegt usw..(kommt alles vor). In solch einem Fall ist es am sinnvollsten, einen IRC-Oper zu kontaktieren, der sich der Sache dann "liebevoll" annimmt. Ist ein user auf einem Kanal stoerend, so kann man entweder versuchn, ihn zu verbannen oder aber den mode auf +m zu setzen. Nachdem dann nur noch channelops sprechen koennen, ist es sinnvoll, allen jene ops zu geben, die noch keine haben (mit Ausanahme des Stoerenfriedes natuerlich). Besonders effektiv ist diese Massnahme bei floodbots, welche einfach irgendeinen channel joinen, um dann sinnloses Zeug zu verbreiten. Ad Netsplits und servers Jeder server muss an mndestens einem server dranhaengen, damit Ihr ueber- haupt mit anderen Leuten, die nicht auf Eurem server sind, kommunizieren koennt. Im Falle von olymp* ist das in der Regel der server auf der Uni Wien, itc.univie.ac.at (131.130.39.27), allerdings routen wir auch oft ueber Frankreich (Eurecom8.Cica.Fr, Lyon, oder Paris), links in die Schweiz und Schweden sind - so hoffe ich - im Entstehen. Auch nach Linz gibt es ein Link, aber Herp und ich haben noch nicht herausgefunden, was an den config lines falsch ist, das kan also noch dauern. Wenn Ihr also auf einem channel seid und ploetzlich eine ganze Reihe *** Signoff: nickname (itc.univie.ac.at olymp.wu-wien.ac.at) kommt, dan heisst das, dass das Netz (das link zwischen olmymp und der Uni Wien) kaputt ist. In 99% aller Faelle ist das nicht unsere Schuld, Uni Wien ist im Moment instabil, da eine buggy version dort laeuft. Die Folge dieses netsplits ist jedenfalls, dass nur noch die Leute vom olymp* server anwesend sind. Spaetestens nach 5 Minuten jedoch wird ein anderes Link aktiviert, nach Frankreich, sodass ein split im schlimmsten Fall 5-10 Minuten dauert. Wenn ich personelich anwesend bin, dann ist der split in 1 Minute vorbei, da ich das Netz selber natuerlich schneller zu- sammenhaengen kann als das das config file tut. Ueblicherweise sind es aber nicht itc<-->olymp, die splitten, sondern ir- gendwelche Riesenserver in den USA oder ein groesserer europaeischer ser- ver. Auch da kann man etwas tun, wird aber oftmals nicht so sehr ge- schaetzt... Das Netz ist dann in 2 Teile gesplittet, eines mit circa 400, das andere mit beispielsweis 1400 usern, und bis alle zurueck sind, kann es ein Weil- chen dauern, obwohl die meisten US server schnelle automatische links ha- ben. Zu netsplits kann es dann kommen, wenn der mainframe, auf welchem der ser- ver laeuft, gerade ueberlastet ist oder der server zu viele Informationen auf einmal verarbeiten muss (zu viele mode changes, flooding, etc). Nach einem Netsplit dauert es immer ein wenig, bis alle Leute, die "signed off" haben, wieder etwas auf dem Kanal sagen (obwohl sie offensichtlich laengst zurueck sind). Dies ist eine Folge von lags, die immer waherend netsplits auftreten und auch haeufig als Vorbote derselben angeshen werden koennen (/ping nickname liefert eine Information ueber das lag. Leute in Oesterreich sollten eine ctcp ping reply von 0 oder 1 Sekunde liefern, ansonsten in etwa 3-6 Sekunden). Man kann das "Zurueckkehren" des Netzes leicht daran erkennen, das ploetz- lich eine wahre Flut (megascroll ;) von mode changes (ueblicherweise +o und +b) ueber den Bildschirm rast. Dies ist mehr oder weniger als catchup point zu verstehen, also der Zeitpunkt, zu dem das Netz wieder einigermas- sen zusammen haelt. Bevor jedoch nicht 100%ig sicher ist, dass kein lag mehr herrscht, sollte man sich mit mode changes (insbesondere +o) sehr zurueckhalten, da dies oft zu sogenannten "desyncs" fuehren kann, das heisst mode changes, welche eigentlich gar keine mode changes sind. Mei- stens schickt dann irgendein IRC-Oper oder bot eine automatische Nach- richt, dass Ihr desynched seid und den Kanal verlassen solltet oder IRC ueberhaupt neu starten muesst. Nicht immer sind dies Nachrichten ni Ord- nung, es kann natuerlich genauso gut sein, dass der bot selbst out of sync ist, aber ein stupider IRC-Op (der nach Moeglichkeit on top der kill Liste stehen will) gibt darauf nicht sehr viel und killt Euch. Es ist natuerlich unangenehm, wenn ein netsplit passiert, aber dennoch ist es sinnvoller, auf dem eigenen server zu bleiben anstatt hin und her zu huepfen, aufgrund der Tatsache, dass es leciht zu "Nickname collisions" kommen kann. Ein Beispiel kan das verdeutlichen: Fingwe ist auf server olymp.wu-wien.ac.at und er stellt fest, dass die US Leute immer langsamer werden (ping replies dauern laenger und laenger), und tatesaechlich passiert der split jetzt: *** Signoff: nickname (eff.org csa.bu.edu) (mehr oder weniger 80% der Leute auf dem Kanal). Kluger Fingwe denkt sich, wenn ich auf die andere Seite des Netztes wechsle, bin ich vom Split nur zu 20% betroffen, alsdo macht er: /win new server eff.org mit dem Effekt, dass Fingwe jetzt auf 2 servern gleichzeitig ist, naemlich olymp (im unteren Fenster) und eff.org (im oberen Fenster). Nachdem ja des Netz gesplittet ist (also eigentlich 2 Netze bestehen), kann Fingwe 2x auf IRC sein, einmal im europaeischen Netz und einmal im amerikanischen. Nach circa 2 Minuten aber aktiviert csa.bu.edu sein auto-connect zu einem ande- ren server und das Netz kommt wieder zusammen, und ploetzlich sind 2 Fingwe's da. Wenn man Glueck hat, wird nur ein Fingwe-Prozess durch einen server gekillt, aber oft gehn beide drauf, und nicht nur einmal, da ja, wie bereits erwaehnt, nach einem netsplit immer eine Zeit lang ein lag besteht und somit der lagged server noch gar nicht weiss, dass Fingwe gar nicht mehr auf eff.org ist, sondern ohnedies laengst gekillt wurde. Statt- dessen geht das killen munter weiter (20x, oefter, kommt alles vor), bis schliesslich nach ein paar Minuten wieder genug Ruhe eingekehrt ist. Es ist also wirklich vernuenftiger (und hilft, das Netz zu stabilisieren), auf einem server zu bleiben, anstelle wild herumzuhuepfen :-) Beliebte channels: #talk : hier wird alles geplaudert, Tiefsinniges, smalltalk, usw. #england: wie #talk, aber vorwiegend UKler, US ud Australier :-) #hottub: wie #talk #romance: wie #talk, aber nicht ganz so hektisch :-) #sex und #hotsex sind eher fad, nicht wirklich zu empfehlen, aber NetSex ist ja bekanntlich immer noch safe ;) Na ja, ausprobieren... #pub : ein Kanal wie #talk, sehr beliebt mittlerweile :) #chat : wie #talk alle asiatischen channel ssind auch immer gut fuer Plauderei, also zum Beispiel: #taiwan, #asians, #taipei, #hk, #chinese ....:) Das UnderNet: Auch das gibt es hier (unsere WU ist sehr progressiv! ;) Das UnderNet ist eine Alternative zum normalen IRC, das Ihr besucht, wenn Ihr "irc" am idefix eingebt. Abgesehen davon, dass meistens nicht mehr als 40-100 Leute anwesend sind, ist es ein sehr ruhiger und erholsamer Platz zum Plaudern. #wasteland #chat sind die beiden meistbesuchten channels dort. Ihr koennt es ja jederzeit ausprobieren: /server Vienna.AT.EU.UnderNet.org 6667 oder /server 137.208.8.30 6667 und schon geht die Post ab :-) So, ich glaube, das war jetzt eine recht ausfuehrliche Einfuehrung, und ich hoffe, es war fuer jeden etwas dabei! Viel Spass Euch allen beim IRCen, und nicht vergessen, falls es Fragen geben sollte, mailt mir oder fragt am IRC...:-) Happy and addictive IRCing, Bernhard / Fingwe (oder AlcBottle, EvilChaos usw...:-) ======================================================================== The ecto archives are on hardees.rutgers.edu in ~ftp/pub/hr. There is an INDEX file explaining what is where. Feel free to send me things you'd like to have added. -- jessica (jessica@ns1.rutgers.edu)