|[Home] [Credit Search] [Category Browser] [Staff Roll Call]||The LINUX.COM Article Archive|
|Originally Published: Friday, 21 September 2001||Author: David Mckee|
|Published to: learn_articles_firststep/General||Page: 1/1 - [Std View]|
Linux.com Beginners Week: How to Get Ahead on IRC
Linux.com regular volunteer "LinuxWolf" sends us this very nicely written piece on the basics of IRC chatting and use. Experts will know this stuff already, but if you are new to IRC or have yet to join us on, say Linux.com Live!, this is a great primer.
IRC is an acronym for Internet Relay Chat. Some people call it Internet real-time chat, but that's not correct. While chat does take place in real-time (instantaneous) to the user, it is not really, as the messages are relayed from one server to another until they appear on your screen. There are also JAVA based chats, like you see on Yahoo, and other "instant" chat programs, but we are going to focus on traditional IRC. I am going to show you some of the basics commands all users of IRC should know, like CHANSERV and NICKSERV.
Now, unlike how a lot of people may think, most IRC servers are not run by multi-million dollar corporations. Yes, Yahoo, AOL and others have their own chat networks and in some cases their own clients, but we are going to focus on "underground" IRC (like OpenProjects.net) and clients such as X-Chat, Kvirc, BitchX on Linux or Unix. There is Pirch and Mirc for Windows users and clients for almost any platform you can imagine, but for each the same kinds of instructions apply since IRC is client/server.
It's important to understand that on IRC, unlike Yahoo chat, a network like openprojects is not a huge corporation, but users just like you. They have decided to take a group of their computers and link them all together so you can chat. They are based all over the world, as a matter of fact most IRC server admins or IRCop's have never even met face-to-face. What is very important to understand about most networks on IRC is that they are about community, even if nobody knows what anybody else looks like.
Many IRC communities are very strong and offer a powerful "home" for those involved in them. This is why some respect is needed for both the servers OP's and guests. A lot of guests assume because they have a computer and connection, it is their right to be on a network or a channel. Well, I hate to burst the bubble but it is not your right. You, like me or many of your friends are operating on an individual's personal computer, the network operator. They have every right to say what and who is or is not allowed on their network, so a little respect and a very few rules are needed. I know that will upset some people, but it is the truth: we are not paying to use their services or bandwidth. So a little common courtesy is needed and expected when it comes to IRC.
/join irc.server.domain. For OPN it would be
/server irc.openprojects.net. You type that into what is often called the server window, or console window, or status window. You can add that server to your IRC client if you do not see it in your list manually, doing so is usually in the preferences or settings of the IRC client, and is fairly self-explanatory.
/MOTD. it will display the MOTD only and not all of the other connection stats.
Now as I mentioned all servers and even channels vary on rules (I will deal with channels in a later section) . Some of the most common activities servers will not allow are: Warez, heavy MP3 trading, HaXoR activity, this can include using Bots/war-scripts. PORN on some networks is prohibited period, some have rules just about child-porn, as they should have! The MOTD is where you will find this out. In closing this part of the tutorial let me remind you that there is no reason for saying "I didn't know the rules", and if you break the rules nobody will care if that's what you say. Always read the MOTD when you join a network, especially if it is your first time. But never take for granted that reading it once is enough, rules and networks change constantly. What is allowed today could be taboo tomorrow. That is how communities work in the real world, too.
One of the best things about IRC is channels. You name it, there is a good chance you will find a channel dedicated to it. Here are some suggestions when joining a channel you are not familiar with.
/msg nick <your message>. This would open a new window to that user, with your text message in it.
/noticeis similar, though in this case a lot of IRC-clients will display the message in that user's status window. Other clients like BitchX will display the message in that users channel window, but only they can see it. You can tell by the color of the text, it will be (perhaps) purple to indicate it is a private message.
A small note here on the use of these two commands. A lot of guests in channels do not like it when others use these commands. When you do this without asking the person first, it is like inviting yourself to a private party. Always ask in the channel first if you may msg the person. If they say sure, then fine, but if they say no, then respect their privacy and don't message them privately.
Port Scans: This is frowned on in pretty much any channel, and most networks. While if a person you know asks you to do so, it is fine, running a NMAP, or other types of portscans on users in a channel can result in you being banned instantly. In a worse case scenario if you persist, you could risk being banned from that IRC network completely. I have seen entire domains banned from networks because of such activity by users of a particular ISP. Always remember that what you do on a server, also reflects on other people that share the same ISP as you.
Scripts and Bots: This is always a tough call when I have been asked about them. As a new person I do not suggest you run a bot or any scripts, I will explain why in a moment. Now some IRC networks have no problem with guests running a bot or a script in a channel. In #linuxhelp, for example, "Info" is what's called an information bot, "google" is also a bot. Both serve very useful information to guests in #linuxhelp. However, the bot's have the founder of the channel's permission to be there, and are run by them. Now some channels have no problem with a guest running their own bot, others are adamant you do not. If your just joining a channel ask one of the op's if you may bring your bot in. Never bring your bot into a channel without asking first, most have strict rules on this.
Scripts are the same really, as that is all a bot really is, but can vary widely. Like bots a user running a script in a channel can cause a lot of problems. Don't get me wrong, I have run many a script in my years on IRC, I even wrote a few I use for personal use. The biggest problem with scripts, especially for a person who is new to IRC is this: If you did not write the script yourself, you have no real idea of how it works, or what it is doing. You could be sending constant PING requests to all users of a channel, or perhaps blurting out useless information and almost flooding a channel. You may not even be aware it is doing it, and when questioned, you have no idea how to shut it off. So don't run bots or scripts unless you know how to control them, and have permission to use them in a channel.
I am only going to deal with the very basic commands of the most used services. On a lot of networks that offer services you can get help with them by typing
/msg services_name help.
NICKSERV: In my opinion Nickserv is the most useful, and powerful of the services you will see. While CHANSERV controls a channel, who get's op'ed in it and so on, the fact is unless you have a registered nickname, you can't even have a personal channel that is always around. So technically you can't even attempt to register your channel till you have your nickname. NICKSERV keeps track of all registered nicknames on a given IRC network. You may have even seen NICKSERV in action when you first logged onto a new IRC network. If you try use a nickname that another user has registered and set Protection and Kill on. You probably where greeted by NICKSERV saying " This nick is registered, if you own it. Please type
/msg nickserv identify password. If you don't know the password for that nickname then it is NICKSERV that drops your connection to that network. So how do you register a nickname and turn on that kewl function you may ask? Well here we go, these are the most basic commands you will use to interact with NICKSERV.
/msg nickserv register password
Yes nickserv knows what nick you're using and if it is taken, also don't use "password" as your password, heh. When you installed Linux you choose unique passwords for your users account and root account, here the same rules apply. Your password should consist of both uppercase and lowercase letters, mixed with numerals. An example of a good one is As#ht016P, a bad one would be 111770. But whatever you do, DO NOT use the user or root password for your computer: EVER! Make the password unique but something you will remember. There are numerous reasons for this, which go beyond the scope of this article. To make it so only you may use the nickname you have choose type the following:
/msg nickserv set secure on
/msg nickserv set kill on
this can vary from network to network. Remember you can get help by typing
/msg nickserv help set as set is the command you want help with. As I said before, this also applies to any command with any service, you would just alter the services name and command.
Your nickname is now registered, and protected. If anyone, including you tries use that nickname and does not know the password, NICKSERV will drop their connection after 60 seconds.
CHANSERV: Chanserv works very closely with NICKSERV as I mentioned earlier. You cannot register a channel, or add people to your op's list, unless you have registered your nick. CHANSERV will not accept a request to register a channel unless your nick is registered. So here we go, let's register a channel.
We will call ours "#foo" Now pay attention to that STATUS window I mentioned at the start, this is where any error msgs will appear. Type:
/msg chanserv register #foo <a password> >description-of-channel<
Please note that each network is different, some also require an e-mail address, or a description of the channel, so watch that status window for error messages. Voila! You are now the proud owner of #foo, chanserv will de-op any person that enters the channel that's not an op you appointed, even when nobody is there. Like with nickserv you can get help the same way and with same syntax as before, all services use the same format for asking for help.
MEMOSERV: This will be short and sweet as few IRC networks offer this service, it also has few commands. Memoserv allows you to send a short message to anyone with a registered nick, even if they are offline. Most IRC networks that offer Memos have a limit of 256 characters including punctuation. So make your memo short and sweet. The syntax to send a memo is:
/msg memoserv send <persons_nick> your message for them"
Thats it. When they next log on to the IRC server they will be greeted by a message saying " You have a memo from" and they will get instructions on how to read it, delete it and so on. Some users disable the ability to get memo's. There is nothing you can do if that person has the memo option set to OFF.
David "LinuxWolf" Mckee: I am your stereotype WEB GEEK, though using Linux only about nine months. I have been using computers for about 10 yrs, 20 if you count my coCo2 days. I have used the web for about 10 years and IRC for over 7. I used to run a BBS in Vancouver, BC Canada. I became involved with IRC in its infancy. I can mostly be found in #Linuxhelp and #linux.com-live! I run a small home based business in Vancouver that focuses on the home-user, SO/HO people, and was a beta tester for the @home network when it was first released in Vancouver.