The following are examples of valid IRC messages:. When the last parameter is prefixed with a colon character, the value of that parameter will be the remainder of the message including space characters. Some messages also include a prefix before the command and the command parameters. The presence of a prefix is indicated with a single leading colon character. The prefix is used to indicate the origin of the message.
For example, when a user sends a message to a channel, the server will forward that message to all the users in the channel, and will include a prefix to specify the user that sent that message originally. We will explain the use of prefixes in more detail in the next section. The IRC protocol includes a special type of message called a reply.
When a client sends a command to a server, the server will send a reply except in a few special commands where a reply should not be expected. Replies are used to acknowledge that a command was processed correctly, to indicate errors, or to provide information when the command performs a server query e. The command will be a three-digit code.
About Projects chidb chirc chiTCP chirouter chistributed chisubmit. You are not expected to read all of these documents. More specifically: We recommend you do read all of [RFC] , as it will give you a good sense of what the IRC architecture looks like.
A reply is a message with the following characteristics: It always includes a prefix. Before joining any IRC channels, you should understand basic manners online. Good manners on IRC are as important as good manners when visiting someone in real life. Often a channel has more than one conversation going at a time.
The nick is followed by a colon or a comma, and then the comment. Most IRC clients also understand this rule, and notify you if someone uses your name this way. Another reason this rule is helpful is you cannot assume others are looking at IRC at the same time as you.
They may be away from their computer, or working on something else. When you address comments, the notification will be waiting for the other person to return. That person can then reply to you. Some communities or channels have their own rules and guidelines. Some channels have operators, or ops , who monitor the channel to make sure things are going well. They may take action if someone is being rude or abusing the channel.
Take the time to read them before joining any conversations. Doing so will avoid problems or misunderstandings, just like house rules when you visit someone. If you know the name of the channel you want to join, type it in the provided box and select OK. It shows you a list of networks and channels you have joined, a conversation window, and a list of nicks in the current channel.
Note the conversation starts with a topic for the channel. In this case, the hexchat channel topic includes several pieces of information, including the home page for the project and a link to the documentation. Sometimes you may see rules for the channel in the topic as well.
Before you type anything, remember: anything you type will be sent to the channel. The slash tells your client you are typing an IRC command and not a comment for the channel. Many commands can be run through the menu in the app window, or by right-clicking an object such as a network, channel, or nick. This post was originally published in January This post was originally published in January Save.
Paul W. Frields has been a Linux user and enthusiast since , and joined the Fedora Project in , shortly after launch. He was a founding member of the Fedora Project Board, and has worked on docsc, websites, advocacy, toolchain, and package maintenance. He currently lives with his wife and two children in Virginia where he also runs a recording studio 5thdom.
I use IRC here and there and this helps clear up somethings. One question I have is about displaying your actual IP address. Is masking your IP address important? Ultimately, I do not think it is a major area of concern — I never used a mask originally and I never ran into a problem where someone was able to compromise my privacy or security with it.
The only reason I have a cloak now is because I have one of the cool Fedora ones, e. If you want a Fedora cloak, anyone with a Fedora account can apply for one! You should never automatically as by remote events or commands send a message or notice in response to a notice sent to you.
As you start to meet people on IRC, you will want to add certain nicknames to your notify list such that you will be notified when they sign on or off IRC. The day will come when you decide not to see or hear a specific person on your screen.
This can be achieved using the ignore command. If people are flooding channels with useless text or they are otherwise harassing you, a wise response is to ignore those person.
Ignore can be set to a nickname or by specifying a user host format. You can use all kind of wildcards. 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 language other than English, eg. Similarly, you should check the topic when you join 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 is not necessary to greet everybody on a channel personally. Usually one "Hello" or equivalent is enough. Also, don't expect everybody to greet you back. On a channel with 20 people that would mean one screenful of hellos.
It makes sense not to greet everyone, 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. Also note that using your client's facilities to automatically say hello or goodbye to people is extremely poor etiquette.
Nobody wants to receive auto-greets. They are not only obviously automatic but, while you may think you are being polite, you are actually conveying yourself as insincere. If somebody wants to be auto-greeted when they join a channel, they will auto-greet themselves. 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" send large amounts of unwanted information to a channel or user.
This is likely to get you kicked off the channel or killed off from IRC. Dumping causes network "burps", causing connections to go down because servers cannot handle the large amount of traffic. Other prohibited actions include:. Harassment is defined as behavior towards another user with the purpose of annoying them. Channel operators are the 'rulers' of a particular channel. This means they can kick you out of their channel for any reason.
If you don't like this, you complain to them or start your own channel and become a channel operator there yourself. They cannot fix channel problems. They cannot kick someone out of a channel for you.
IRCops have better things to do than interfere in channel affairs. A channel is automatically created as soon as the first person joins it. If you join a channel and you find your name as the only one there, you just created that channel. Channels on IRC are dynamic in the sense that anyone can create a new channel, and a channel disappears when the last person leaves it. Every IRC network has its own set of popular channels. Most clients will display the list of channels in a new window and you can change its display to sort channels by the number of users.
Just join one of those channels to find out what happens on them. Besides chat channels, there also exist channels specialized towards helping other users. Examples are help, windows, irchelp, and mirc. You can also do this for smaller numbers. Even very crowded channels can be silent, so if you join a channel and don't hear much talking, it may be because you joined, but just because the people on that channel are doing other things.
Some networks support registered nicknames. This means that they allow you to set a password on a nickname so that you own it. Only the person who knows that password will be able to use it. There are, literally, millions of possible channel names, so if someone is on your usual channel, just go to another. The answer to this question is the current channel operators and them alone. Given the dynamic nature of channels, channel operators do not need to have a reason to kick you off.
They decide what goes on in the channel. It is their channel. Complaining either to IRC operators or to the system administrators about being kicked or banned from a channel will not result in action. IRC operators do not meddle with channel politics - that's the job of channel operators.
If you should get banned or kicked from a channel, you are always free to start your own channel and decide what is appropriate content there. Imagine channels as houses. The owner of the house can decide to share ownership with someone else and can decide to prevent any individual from entering his house. In your own house, you call the shots. Feel free to create your own channel, and set up your own rules for it. Channel operators are the owners of their respective channels. If you are a channel operator, keep this in mind when giving out channel operator powers.
Do not give out channel operator status to everyone. This causes the possibility of mass-kicking or otherwise harassing by unknown ops and the channel can be left without any channel operators. However, always make sure to give ops to enough people so that all of the channel operators don't unexpectedly disappear and leave the channel without any operators.
If no ops are on your channel you have one option. You can ask everyone to leave and rejoin the channel. This is a good way to get channel operator status back. This does not work on large channels or ones with bots, for obvious reasons. On some networks, you can register a channel so that you own it and can maintain control over it as far as who gets channel operator status and how that privilege is governed.
A "bot" is short for "robot". It is normally a script run from a client or a separate program in perl, C, and sometimes more obscure languages.
Bots are normally not needed on IRC. A bot generally tries to "protect" a channel from takeovers or performs other functions. It is important to know that some IRC servers ban all bots. Some bots provide useful features and can be entertaining. Contrary to these bots, you will find many bots performing useless 'carekeeping' of channels, harassing and boring people and sometimes created with the sole purpose to produce garbage. You can imagine that these bots are disliked by the IRC community.
In this context it is good to advise you to never, ever take bot code,. If you feel you just have to run a bot, at least learn the programming. Some networks support a nickname registration service called NickServ. This allows users to register and own nicknames.
Some networks support a channel registration service called ChanServ. This allows users to register and own channels. If you use the LIST command, the server generates a list of all channels and quickly sends that list to you.
But, because the data throughput is finite, the entire output of the LIST command is queued in a buffer on the server. At some point that buffer is overrun, and the server, detecting this 'reached maxsendq' , disconnects you. This mechanism is designed to disconnect people who generate more characters per second than any 'normal' person uses for normal conversations. It is a server protection mechanism, but unfortunately the server does not recognize that the data stream you caused is simply the result of your harmless LIST command, and disconnects you.
In most IRC clients, you can filter the channels list to show only channels with a minimum and a maximum number of people. You can also specify a text string so that your client will only list channels with that string in their name or topic.
However, for the problem described, this may not always help. Some servers always send you the entire channels list and your client takes care of the filtering. So, asking for a partial list to prevent you from disconnecting won't make any difference. It is unfortunate, but there is nothing you can do to prevent this from happening.
It is just one of the all-too-many IRC oddities. Try using some other server, as many are more forgiving. Netsplits are unfortunately a routine part of IRC life. The above message means that NickName, who was on a channel with you, was on a different server from you and this server split off from the part of the net you are on. A B C. Let's say that you are on server D, and server A splits from server B. In this case, you will see all users on the servers B, C and E, "sign off".
Note that netsplits are all from the point of view of the user. After a netsplit rejoins people might ask where you went -- because from their perspective, you split off.
The only thing you can do during a netsplit is wait for the net to merge itself. Changing your server during a netsplit is a Bad Idea, because you are likely to have your nickname collided. A "split" often occurs due to faults in the underlying physical network. It can also occur due to other reasons, such as if the machine on which the IRC server runs crashes, or if it is too overloaded to handle connections as happens on bigger nets, or if an IRC operator willfully disrupts the connection between two servers to achieve better routing server - server connections.
After a netsplit, a net-join begins and on both halves of the merging network, and people that existed with the same nicknames can be killed. This can happen frequently with popular nicknames. This phenomena is called a Nick Collision. As soon as a Nick Collision is detected in general both persons involved will be disconnected killed from their IRC servers. Nick Collisions can be caused on purpose by people who just want to harass others or try to take over their channel.
In general, this behavior is considered very abusive and can easily lead to a K-line. After a netsplit, during the net-join process, servers on both sides of the split try to update all kinds of information they may have missed. New users, their nicknames, the channels they are on and most of the channel settings are exchanged. The servers involved in the split will also make sure on both sides of the split on all channels the same channel operators are set.
This process is called server-opping. Server-ops show like:. Server-ops are famous for its use in malicious behaviour.
People can use net-splits to get operator status on a channel on one side of the split and on the moment of net-join de-op the rightful channel operators.
0コメント