text:
12 September, 2006@12:00 am
0 comments
As someone who grew up on Too $hort's early albums – from Born To Mack to Shorty The Pimp, you kind of always know what to expect from the Oaktown legend. Of course, this also makes the average attention span of a $hortdog fan last about five albums. By then, you've had your share. So for someone who hasn't bought a record from Short in over ten years, this is somewhat of a familiar experience.
But the more things change, the more they stay the same, as is in the case of his latest effort, Blow The Whistle. With heavy pressure from today's major labels, keeping your production in house is almost impossible, so gone are the trademark beats from longtime collaborator Ant Banks, instead traded for selections from Lil' Jon, Jazze Pha, Will.I.Am, and other producers of the "now sound".
The album begins with the unsurprising "Call Her A Bitch", which is exactly what it sounds like it is, as $hort carries on the long-standing tradition of making "shit" and "bitch" rhyme, in an excessive introduction that lets listeners know he hasn't changed his political stance (on hoes) over the years. He sounds rejuvenated however when teamed up with executive producer Lil' Jon on "Blow The Whistle", an excellent almost-Hyphy anthem where $hort brags "I heard 93 rappers say 'bitch' like me / two singers and ten comedians / and I'm still gonna yell it every time you see me then." "Burn Rubber Part 2″ comes next, with a moving Lil' Jon beat attached to it, yet $hort's uninspiring hook leaves it feeling a bit flat – at least in comparison to the original version. The surprising "Keep Bouncing" finds $hort rhyming alongside Snoop Dogg and producer Will.I.Am over an unquestionably raw collection of drums and samples from A Tribe Called Quest and Black Eyed Peas. The Lil' Jon produced "Money Maker" is an obvious club-banger, complete with the producer's trademark keys, low base, and handclap snares, while Pimp C and Rick Ross help inspire some gratuitous ass-shaking.
The album seems pretty solid from the jump, but hits a ridiculous brick wall midway through, thanks to a series of Jazze Pha produced tracks. One right after another, this 5 song set of "Strip Down", "Nothing Feels Better", "Sophisticated", "Playa", and "16 Hoes" runs the album into the ground, each Jazze fizzled out with awfully crooned hooks, skating rink synth, and done-to-death "Ladies and Gentlemen!" mating calls. Listening to the first five seconds of each track in a row is a disturbing example of how disposable this shit is.
But things get back on track when Lil' Jon steps back in the studio with $hort on the Dogg Pound featured "Sadity". For the sake of argument it could be said that this track is interchangeable with any other Lil' Jon beat, but Dogg Pound's forgotten gangsta style and catchy hook help carry this song. The album's best track, "I Want Your Girl" follows, produced by hyphy movement producer Droop-E, with show-stealing moments from E-40, Dollar Will, and Mr. F.A.B, not to mention that ridiculous beat. Unfortunately, the album's last two tracks are duds - both produced by Jon – "It's Time To Go" and "Shake It Baby". The latter is Jon's attempt at "crunk rock", which is nothing more than a typical Lil' Jon beat with some lame guitar stabs over it, while $hort struggles through the track. It's certainly no "Let's Go" (Trick Daddy & Lil Jon).
It's nice to see a high profile producer like Lil' Jon take on a project from a living legend like this, and with the Bay Area's new resurgence thanks to the hyphy movement, $hort will probably drag in some new fans as well. It definitely has it's moments - much more than some of his recent LP's probably have had - but at the end of the day, this is just another Too $hort record.
- Raekwon Sets A Release Date For "F.I.L.A." Album
- BUSH: A Snoop Odyssey Produced By Pharrell Williams [Preview]
- Drake – "If You're Reading This It's Too Late" Surprise Album on iTunes Now
- Action Bronson "Mr. Wonderful" Cover Art and Tracklist
- Juicy J "Blue Dream & Lean 2″ Mixtape Cover Art & Release Date Revealed
- MF Grimm "MF Love Songs" Cover Art + Tracklist
- Lord Hakim – "Brass Knucklez" (feat. Vast Aire & Phizz Ed)
- IAMSU! – "Hella Good" (feat. Tyga)
- DJ Kay Slay – "I Declare War" (feat. Styles P, Sheek Louch, Vado, Raekwon, & Rell)
- Maverick Sabre – "We Don't Wanna Be" (feat. Joey Bada$$)
- Cannibal Ox – "Blade: Art of Ox" (feat. Artifacts & U-God; prod. Black Milk)
- Asher Roth – "Blow Your Head" (prod. Nottz)
- It's Time To Say Goodbye...
Commented on by Yungplex
- It's Time To Say Goodbye...
Commented on by geedubbleyoo
- Fat Trel - "In My Bag" (feat. Wale)
Commented on by Katae
- Kanye West's "Runaway": What Does It All Mean?
Commented on by fidgar
- Sole Vs. El-P: Part One - Sole
Commented on by Reno Yakavetta
- It's Time To Say Goodbye...
Commented on by Atom


text:
Win Big for Schuyler Hospital at November Splendor
Last year, November Splendor broke records for attendance, prize donations and sponsorships. This years event scheduled for Friday, November 15, 2013, at the Harbor Hotel in Watkins Glen, beginning at 6 p.m. is on track to raise the bar again.
Attendees at the annual cocktail attire dinner dance can get in to win one of seventeen raffle packages, and six live auction packages with a total value of over $14,000! All items are donated by generous businesses in the community and around the region.
New packages include: Wine Lovers package with a wine rack, wine, winery tour, tickets to both Deck the Halls and the Finger Lakes Wine Festival, and a B&B stay for Deck the Halls weekend. For the Guys includes tools and more tools, oil changes, golf and survival meals for your hunting or hiking adventures. On the Water includes a kayak and paddle, kayak tour, and a full-day motor boat rental. Home Exteriors includes a landscaping / hardscaping package valued at over $1,200, plus a full-day compact equipment rental. Boys Get Active includes tickets to Wonderworld at Destiny USA, a bicycle and helmet, sports equipment and a glider ride. Girls Day Out includes A Day at American Girl Place package in New York City, travel money, and a Broadway Show.
Bring cash, check or credit and make sure to get in on some amazing raffle packages, and an exciting Live Auction headed up again this year by auctioneer Matt Hayden. Raffle tickets will be available up until winners are drawn at 10 p.m.
Last years event nearly sold out at 240 attendees, so reserve your tickets for $85.00 each at www.schuylerhospital.org, or call (607) 210-1950.
For just $129 (village view) or $149 (lake view), reserve your room with the Watkins Glen Harbor Hotel no later than November 1, 2013. Let them know you are with the Schuyler Health Foundation dinner.
Ladies if youre still looking for a dress, JBK Bridal and Prom in Montour Falls is offering a 15% discount! Be sure to mention that you are shopping for November Splendor.
Dance the night away with a new band this year Atlas, from the Rochester area. Check them out at www.atlasband.com
All proceeds benefit the 2013 Family of Friends Campaign to benefit Schuyler Hospital and the Seneca View Skilled Nursing Facility.
For more information, contact the Schuyler Health Foundation at (607) 210-1950 or firstname.lastname@example.com
blog comments powered by Disqus <<< Back to the FingerLakes1.com Homepage | News Desk | Sports Page | Living Section | Business | Technology
FingerLakes1.com Network SITE MAP

subset: commoncrawl


text:
Network Working Group C. Kalt Request for Comments: 2812 April 2000 Updates: 1459 Category: Informational
Internet Relay Chat: Client Protocol
Status of this Memo
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
The IRC protocol itself enables several possibilities of transferring data between clients, and just like with other transfer mechanisms like email, the receiver of the data has to be careful about how the data is handled. For more information on security issues with the IRC protocol, see for example http://www.irchelp.org/irchelp/security/.
The IRC (Internet Relay Chat) protocol is for use with text based conferencing; the simplest client being any socket program capable of connecting to the server.
This document defines the Client Protocol, and assumes that the reader is familiar with the IRC Architecture [IRC-ARCH].
Table of Contents
- Labels …………………………………………….. 3 1.1 Servers ………………………………………… 3 1.2 Clients ………………………………………… 3 1.2.1 Users ……………………………………… 4 126.96.36.199 Operators ……………………………… 4 1.2.2 Services …………………………………… 4 1.3 Channels ……………………………………….. 4
- The IRC Client Specification …………………………. 5 2.1 Overview ……………………………………….. 5 2.2 Character codes …………………………………. 5 2.3 Messages ……………………………………….. 5
Kalt Informational [Page 1] RFC 2812 Internet Relay Chat: Client Protocol April 2000
2.3.1 Message format in Augmented BNF ................... 6
2.4 Numeric replies ........................................ 8
2.5 Wildcard expressions ................................... 9
3. Message Details …………………………………….. 9 3.1 Connection Registration ………………………….. 10 3.1.1 Password message ……………………………. 10 3.1.2 Nick message ……………………………….. 10 3.1.3 User message ……………………………….. 11 3.1.4 Oper message ……………………………….. 12 3.1.5 User mode message …………………………… 12 3.1.6 Service message …………………………….. 13 3.1.7 Quit ………………………………………. 14 3.1.8 Squit ……………………………………… 15 3.2 Channel operations ………………………………. 15 3.2.1 Join message ……………………………….. 16 3.2.2 Part message ……………………………….. 17 3.2.3 Channel mode message ………………………… 18 3.2.4 Topic message ………………………………. 19 3.2.5 Names message ………………………………. 20 3.2.6 List message ……………………………….. 21 3.2.7 Invite message ……………………………… 21 3.2.8 Kick command ……………………………….. 22 3.3 Sending messages ………………………………… 23 3.3.1 Private messages ……………………………. 23 3.3.2 Notice …………………………………….. 24 3.4 Server queries and commands ………………………. 25 3.4.1 Motd message ……………………………….. 25 3.4.2 Lusers message ……………………………… 25 3.4.3 Version message …………………………….. 26 3.4.4 Stats message ………………………………. 26 3.4.5 Links message ………………………………. 27 3.4.6 Time message ……………………………….. 28 3.4.7 Connect message …………………………….. 28 3.4.8 Trace message ………………………………. 29 3.4.9 Admin command ………………………………. 30 3.4.10 Info command ……………………………….. 31 3.5 Service Query and Commands ……………………….. 31 3.5.1 Servlist message ……………………………. 31 3.5.2 Squery …………………………………….. 32 3.6 User based queries ………………………………. 32 3.6.1 Who query ………………………………….. 32 3.6.2 Whois query ………………………………… 33 3.6.3 Whowas …………………………………….. 34 3.7 Miscellaneous messages …………………………… 34 3.7.1 Kill message ……………………………….. 35 3.7.2 Ping message ……………………………….. 36 3.7.3 Pong message ……………………………….. 37 3.7.4 Error ……………………………………… 37
Kalt Informational [Page 2] RFC 2812 Internet Relay Chat: Client Protocol April 2000
- Optional features …………………………………… 38 4.1 Away …………………………………………… 38 4.2 Rehash message ………………………………….. 39 4.3 Die message …………………………………….. 39 4.4 Restart message …………………………………. 40 4.5 Summon message ………………………………….. 40 4.6 Users ………………………………………….. 41 4.7 Operwall message ………………………………… 41 4.8 Userhost message ………………………………… 42 4.9 Ison message ……………………………………. 42
- Replies ……………………………………………. 43 5.1 Command responses ……………………………….. 43 5.2 Error Replies …………………………………… 53 5.3 Reserved numerics ……………………………….. 59
- Current implementations ……………………………… 60
- Current problems ……………………………………. 60 7.1 Nicknames ………………………………………. 60 7.2 Limitation of wildcards ………………………….. 61 7.3 Security considerations ………………………….. 61
- Current support and availability ……………………… 61
- Acknowledgements ……………………………………. 61
- References ………………………………………… 62
- Author's Address …………………………………… 62
Full Copyright Statement .................................. 63
- Labels
This section defines the identifiers used for the various components of the IRC protocol.
1.1 Servers
Servers are uniquely identified by their name, which has a maximum length of sixty three (63) characters. See the protocol grammar rules (section 2.3.1) for what may and may not be used in a server name.
1.2 Clients
For each client all servers MUST have the following information: a netwide unique identifier (whose format depends on the type of client) and the server which introduced the client.
Kalt Informational [Page 3] RFC 2812 Internet Relay Chat: Client Protocol April 2000
1.2.1 Users
Each user is distinguished from other users by a unique nickname having a maximum length of nine (9) characters. See the protocol grammar rules (section 2.3.1) for what may and may not be used in a nickname.
While the maximum length is limited to nine characters, clients SHOULD accept longer strings as they may become used in future evolutions of the protocol.
18.104.22.168 Operators
To allow a reasonable amount of order to be kept within the IRC network, a special class of users (operators) is allowed to perform general maintenance functions on the network. Although the powers granted to an operator can be considered as 'dangerous', they are nonetheless often necessary. Operators SHOULD be able to perform basic network tasks such as disconnecting and reconnecting servers as needed. In recognition of this need, the protocol discussed herein provides for operators only to be able to perform such functions. See sections 3.1.8 (SQUIT) and 3.4.7 (CONNECT).
A more controversial power of operators is the ability to remove a user from the connected network by 'force', i.e., operators are able to close the connection between any client and server. The justification for this is very delicate since its abuse is both destructive and annoying, and its benefits close to inexistent. For further details on this type of action, see section 3.7.1 (KILL).
1.2.2 Services
Each service is distinguished from other services by a service name composed of a nickname and a server name. As for users, the nickname has a maximum length of nine (9) characters. See the protocol grammar rules (section 2.3.1) for what may and may not be used in a nickname.
1.3 Channels
Channels names are strings (beginning with a '&', '#', '+' or '!' character) of length up to fifty (50) characters. Apart from the requirement that the first character is either '&', '#', '+' or '!', the only restriction on a channel name is that it SHALL NOT contain any spaces (' '), a control G (^G or ASCII 7), a comma (','). Space is used as parameter separator and command is used as a list item separator by the protocol). A colon (':') can also be used as a delimiter for the channel mask. Channel names are case insensitive.
Kalt Informational [Page 4] RFC 2812 Internet Relay Chat: Client Protocol April 2000
See the protocol grammar rules (section 2.3.1) for the exact syntax of a channel name.
Each prefix characterizes a different channel type. The definition of the channel types is not relevant to the client-server protocol and thus it is beyond the scope of this document. More details can be found in "Internet Relay Chat: Channel Management" [IRC-CHAN].
- The IRC Client Specification
2.1 Overview
The protocol as described herein is for use only with client to server connections when the client registers as a user.
2.2 Character codes
No specific character set is specified. The protocol is based on a set of codes which are composed of eight (8) bits, making up an octet. Each message may be composed of any number of these octets; however, some octet values are used for control codes, which act as message delimiters.
Regardless of being an 8-bit protocol, the delimiters and keywords are such that protocol is mostly usable from US-ASCII terminal and a telnet connection.
Because of IRC's Scandinavian origin, the characters {}|^ are considered to be the lower case equivalents of the characters []\~, respectively. This is a critical issue when determining the equivalence of two nicknames or channel names.
2.3 Messages
Servers and clients send each other messages, which may or may not generate a reply. If the message contains a valid command, as described in later sections, the client should expect a reply as specified but it is not advised to wait forever for the reply; client to server and server to server communication is essentially asynchronous by nature.
Each IRC message may consist of up to three main parts: the prefix (OPTIONAL), the command, and the command parameters (maximum of fifteen (15)). The prefix, command, and all parameters are separated by one ASCII space character (0x20) each.
Kalt Informational [Page 5] RFC 2812 Internet Relay Chat: Client Protocol April 2000
The presence of a prefix is indicated with a single leading ASCII colon character (':', 0x3b), which MUST be the first character of the message itself. There MUST be NO gap (whitespace) between the colon and the prefix. The prefix is used by servers to indicate the true origin of the message. If the prefix is missing from the message, it is assumed to have originated from the connection from which it was received from. Clients SHOULD NOT use a prefix when sending a message; if they use one, the only valid prefix is the registered nickname associated with the client.
The command MUST either be a valid IRC command or a three (3) digit number represented in ASCII text.
IRC messages are always lines of characters terminated with a CR-LF (Carriage Return - Line Feed) pair, and these messages SHALL NOT exceed 512 characters in length, counting all characters including the trailing CR-LF. Thus, there are 510 characters maximum allowed for the command and its parameters. There is no provision for continuation of message lines. See section 6 for more details about current implementations.
2.3.1 Message format in Augmented BNF
The protocol messages must be extracted from the contiguous stream of octets. The current solution is to designate two characters, CR and LF, as message separators. Empty messages are silently ignored, which permits use of the sequence CR-LF between messages without extra problems.
The extracted message is parsed into the components
The Augmented BNF representation for this is:
message = [ ":" prefix SPACE ] command [ params ] crlf
prefix = servername / ( nickname [ [ "!" user ] "@" host ] )
command = 1*letter / 3digit
params = *14( SPACE middle ) [ SPACE ":" trailing ]
=/ 14( SPACE middle ) [ SPACE [ ":" ] trailing ]
nospcrlfcl = %x01-09 / %x0B-0C / %x0E-1F / %x21-39 / %x3B-FF
; any octet except NUL, CR, LF, " " and ":"
middle = nospcrlfcl *( ":" / nospcrlfcl )
trailing = *( ":" / " " / nospcrlfcl )
SPACE = %x20 ; space character
crlf = %x0D %x0A ; "carriage return" "linefeed"
Kalt Informational [Page 6] RFC 2812 Internet Relay Chat: Client Protocol April 2000
1) After extracting the parameter list, all parameters are equal
whether matched by
2) The NUL (%x00) character is not special in message framing, and
basically could end up inside a parameter, but it would cause
extra complexities in normal C string handling. Therefore, NUL
is not allowed within messages.
Most protocol messages specify additional semantics and syntax for the extracted parameter strings dictated by their position in the list. For example, many server commands will assume that the first parameter after the command is the list of targets, which can be described with:
target = nickname / server msgtarget = msgto ( "," msgto ) msgto = channel / ( user [ "%" host ] "@" servername ) msgto =/ ( user "%" host ) / targetmask msgto =/ nickname / ( nickname "!" user "@" host ) channel = ( "#" / "+" / ( "!" channelid ) / "&" ) chanstring [ ":" chanstring ] servername = hostname host = hostname / hostaddr hostname = shortname *( "." shortname ) shortname = ( letter / digit ) *( letter / digit / "-" ) *( letter / digit ) ; as specified in RFC 1123 [HNAME] hostaddr = ip4addr / ip6addr ip4addr = 13digit "." 13digit "." 13digit "." 13digit ip6addr = 1hexdigit 7( ":" 1*hexdigit ) ip6addr =/ "0:0:0:0:0:" ( "0" / "FFFF" ) ":" ip4addr nickname = ( letter / special ) *8( letter / digit / special / "-" ) targetmask = ( "$" / "#" ) mask ; see details on allowed masks in section 3.3.1 chanstring = %x01-07 / %x08-09 / %x0B-0C / %x0E-1F / %x21-2B chanstring =/ %x2D-39 / %x3B-FF ; any octet except NUL, BELL, CR, LF, " ", "," and ":" channelid = 5( %x41-5A / digit ) ; 5( A-Z / 0-9 )
Kalt Informational [Page 7] RFC 2812 Internet Relay Chat: Client Protocol April 2000
Other parameter syntaxes are:
user = 1( %x01-09 / %x0B-0C / %x0E-1F / %x21-3F / %x41-FF ) ; any octet except NUL, CR, LF, " " and "@" key = 123( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F ) ; any 7-bit USASCII character, ; except NUL, CR, LF, FF, h/v TABs, and " " letter = %x41-5A / %x61-7A ; A-Z / a-z digit = %x30-39 ; 0-9 hexdigit = digit / "A" / "B" / "C" / "D" / "E" / "F" special = %x5B-60 / %x7B-7D ; "[", "]", "", "`", "", "^", "{", "|", "}"
1) The
2) <hostname> has a maximum length of 63 characters. This is a
limitation of the protocol as internet hostnames (in
particular) can be longer. Such restriction is necessary
because IRC messages are limited to 512 characters in length.
Clients connecting from a host which name is longer than 63
characters are registered using the host (numeric) address
instead of the host name.
3) Some parameters used in the following sections of this
documents are not defined here as there is nothing specific
about them besides the name that is used for convenience.
These parameters follow the general syntax defined for
2.4 Numeric replies
Most of the messages sent to the server generate a reply of some sort. The most common reply is the numeric reply, used for both errors and normal replies. The numeric reply MUST be sent as one message consisting of the sender prefix, the three-digit numeric, and the target of the reply. A numeric reply is not allowed to originate from a client. In all other respects, a numeric reply is just like a normal message, except that the keyword is made up of 3 numeric digits rather than a string of letters. A list of different replies is supplied in section 5 (Replies).
Kalt Informational [Page 8] RFC 2812 Internet Relay Chat: Client Protocol April 2000
2.5 Wildcard expressions
When wildcards are allowed in a string, it is referred as a "mask".
For string matching purposes, the protocol allows the use of two special characters: '?' (%x3F) to match one and only one character, and '*' (%x2A) to match any number of any characters. These two characters can be escaped using the character '' (%x5C).
The Augmented BNF syntax for this is:
mask = *( nowild / noesc wildone / noesc wildmany )
wildone = %x3F
wildmany = %x2A
nowild = %x01-29 / %x2B-3E / %x40-FF
; any octet except NUL, "*", "?"
noesc = %x01-5B / %x5D-FF
; any octet except NUL and "\"
matchone = %x01-FF
; matches wildone
matchmany = *matchone
; matches wildmany
a?c ; Matches any string of 3 characters in length starting with "a" and ending with "c"
a*c ; Matches any string of at least 2 characters in length starting with "a" and ending with "c"
Message Details
On the following pages there are descriptions of each message recognized by the IRC server and client. All commands described in this section MUST be implemented by any server for this protocol.
Where the reply ERR_NOSUCHSERVER is returned, it means that the target of the message could not be found. The server MUST NOT send any other replies after this error for that command.
The server to which a client is connected is required to parse the complete message, and return any appropriate errors.
If multiple parameters is presented, then each MUST be checked for validity and appropriate responses MUST be sent back to the client. In the case of incorrect messages which use parameter lists with comma as an item separator, a reply MUST be sent for each item.
Kalt Informational [Page 9] RFC 2812 Internet Relay Chat: Client Protocol April 2000
3.1 Connection Registration
The commands described here are used to register a connection with an IRC server as a user as well as to correctly disconnect.
A "PASS" command is not required for a client connection to be registered, but it MUST precede the latter of the NICK/USER combination (for a user connection) or the SERVICE command (for a service connection). The RECOMMENDED order for a client to register is as follows:
1. Pass message
2. Nick message 2. Service message
3. User message
Upon success, the client will receive an RPLWELCOME (for users) or RPLYOURESERVICE (for services) message indicating that the connection is now registered and known the to the entire IRC network. The reply message MUST contain the full client identifier upon which it was registered.
3.1.1 Password message
Command: PASS
The PASS command is used to set a 'connection password'. The optional password can and MUST be set before any attempt to register the connection is made. Currently this requires that user send a PASS command before sending the NICK/USER combination.
Numeric Replies:
PASS secretpasswordhere
3.1.2 Nick message
Command: NICK
NICK command is used to give user a nickname or change the existing one.
Kalt Informational [Page 10] RFC 2812 Internet Relay Chat: Client Protocol April 2000
Numeric Replies:
NICK Wiz ; Introducing new nick "Wiz" if session is still unregistered, or user changing his nickname to "Wiz"
:email@example.com NICK Kilroy ; Server telling that WiZ changed his nickname to Kilroy.
3.1.3 User message
Command: USER
The USER command is used at the beginning of connection to specify the username, hostname and realname of a new user.
Numeric Replies:
USER guest 0 * :Ronnie Reagan ; User registering themselves with a username of "guest" and real name "Ronnie Reagan".
USER guest 8 * :Ronnie Reagan ; User registering themselves with a username of "guest" and real name "Ronnie Reagan", and asking to be set invisible.
Kalt Informational [Page 11] RFC 2812 Internet Relay Chat: Client Protocol April 2000
3.1.4 Oper message
Command: OPER
A normal user uses the OPER command to obtain operator privileges.
The combination of
Numeric Replies:
OPER foo bar ; Attempt to register as an operator using a username of "foo" and "bar" as the password.
3.1.5 User mode message
Command: MODE
The user MODE's are typically changes which affect either how the client is seen by others or what 'extra' messages the client is sent.
A user MODE command MUST only be accepted if both the sender of the message and the nickname given as a parameter are both the same. If no other parameter is given, then the server will return the current settings for the nick.
The available modes are as follows:
a - user is flagged as away;
i - marks a users as invisible;
w - user receives wallops;
r - restricted user connection;
o - operator flag;
O - local operator flag;
s - marks a user for receipt of server notices.
Additional modes may be available later on.
Kalt Informational [Page 12] RFC 2812 Internet Relay Chat: Client Protocol April 2000
The flag 'a' SHALL NOT be toggled by the user using the MODE command, instead use of the AWAY command is REQUIRED.
If a user attempts to make themselves an operator using the "+o" or "+O" flag, the attempt SHOULD be ignored as users could bypass the authentication mechanisms of the OPER command. There is no restriction, however, on anyone `deopping' themselves (using "-o" or "-O").
On the other hand, if a user attempts to make themselves unrestricted using the "-r" flag, the attempt SHOULD be ignored. There is no restriction, however, on anyone `deopping' themselves (using "+r"). This flag is typically set by the server upon connection for administrative reasons. While the restrictions imposed are left up to the implementation, it is typical that a restricted user not be allowed to change nicknames, nor make use of the channel operator status on channels.
The flag 's' is obsolete but MAY still be used.
Numeric Replies:
MODE WiZ -w ; Command by WiZ to turn off reception of WALLOPS messages.
MODE Angel +i ; Command from Angel to make herself invisible.
MODE WiZ -o ; WiZ 'deopping' (removing operator status).
3.1.6 Service message
Command: SERVICE
The SERVICE command to register a new service. Command parameters specify the service nickname, distribution, type and info of a new service.
Kalt Informational [Page 13] RFC 2812 Internet Relay Chat: Client Protocol April 2000
Numeric Replies:
SERVICE dict * .fr 0 0 :French Dictionary ; Service registering itself with a name of "dict". This service will only be available on servers which name matches ".fr".
3.1.7 Quit
Command: QUIT
Parameters: [
A client session is terminated with a quit message. The server acknowledges this by sending an ERROR message to the client.
Numeric Replies:
QUIT :Gone to have lunch ; Preferred message format.
:email@example.com QUIT :Gone to have lunch ; User syrk has quit IRC to have lunch.
Kalt Informational [Page 14] RFC 2812 Internet Relay Chat: Client Protocol April 2000
3.1.8 Squit
Command: SQUIT
The SQUIT command is available only to operators. It is used to disconnect server links. Also servers can generate SQUIT messages on error conditions. A SQUIT message may also target a remote server connection. In this case, the SQUIT message will simply be sent to the remote server without affecting the servers in between the operator and the remote server.
Numeric replies:
SQUIT tolsun.oulu.fi :Bad Link ? ; Command to uplink of the server tolson.oulu.fi to terminate its connection with comment "Bad Link".
:Trillian SQUIT cm22.eng.umd.edu :Server out of control ; Command from Trillian from to disconnect "cm22.eng.umd.edu" from the net with comment "Server out of control".
3.2 Channel operations
This group of messages is concerned with manipulating channels, their properties (channel modes), and their contents (typically users). For this reason, these messages SHALL NOT be made available to services.
All of these messages are requests which will or will not be granted by the server. The server MUST send a reply informing the user whether the request was granted, denied or generated an error. When the server grants the request, the message is typically sent back (eventually reformatted) to the user with the prefix set to the user itself.
Kalt Informational [Page 15] RFC 2812 Internet Relay Chat: Client Protocol April 2000
The rules governing how channels are managed are enforced by the servers. These rules are beyond the scope of this document. More details are found in "Internet Relay Chat: Channel Management" [IRC- CHAN].
3.2.1 Join message
Command: JOIN
Parameters: (
The JOIN command is used by a user to request to start listening to the specific channel. Servers MUST be able to parse arguments in the form of a list of target, but SHOULD NOT use lists when sending JOIN messages to clients.
Once a user has joined a channel, he receives information about all commands his server receives affecting the channel. This includes JOIN, MODE, KICK, PART, QUIT and of course PRIVMSG/NOTICE. This allows channel members to keep track of the other channel members, as well as channel modes.
If a JOIN is successful, the user receives a JOIN message as confirmation and is then sent the channel's topic (using RPLTOPIC) and the list of users who are on the channel (using RPLNAMREPLY), which MUST include the user joining.
Note that this message accepts a special argument ("0"), which is a special request to leave all channels the user is currently a member of. The server will process this message as if the user had sent a PART command (See Section 3.2.2) for each channel he is a member of.
Numeric Replies:
JOIN #foobar ; Command to join channel #foobar.
JOIN &foo fubar ; Command to join channel &foo using key "fubar".
Kalt Informational [Page 16] RFC 2812 Internet Relay Chat: Client Protocol April 2000
JOIN #foo,&bar fubar ; Command to join channel #foo using key "fubar" and &bar using no key.
JOIN #foo,#bar fubar,foobar ; Command to join channel #foo using key "fubar", and channel #bar using key "foobar".
JOIN #foo,#bar ; Command to join channels #foo and #bar.
JOIN 0 ; Leave all currently joined channels.
:email@example.com JOIN #Twilightzone ; JOIN message from WiZ on channel #Twilightzone
3.2.2 Part message
Command: PART
The PART command causes the user sending the message to be removed from the list of active members for all given channels listed in the parameter string. If a "Part Message" is given, this will be sent instead of the default message, the nickname. This request is always granted by the server.
Servers MUST be able to parse arguments in the form of a list of target, but SHOULD NOT use lists when sending PART messages to clients.
Numeric Replies:
PART #twilightzone ; Command to leave channel "#twilightzone"
PART #oz-ops,&group5 ; Command to leave both channels "&group5" and "#oz-ops".
:email@example.com PART #playzone :I lost ; User WiZ leaving channel "#playzone" with the message "I lost".
Kalt Informational [Page 17] RFC 2812 Internet Relay Chat: Client Protocol April 2000
3.2.3 Channel mode message
Command: MODE
The MODE command is provided so that users may query and change the characteristics of a channel. For more details on available modes and their uses, see "Internet Relay Chat: Channel Management" [IRC- CHAN]. Note that there is a maximum limit of three (3) changes per command for modes that take a parameter.
Numeric Replies:
The following examples are given to help understanding the syntax of the MODE command, but refer to modes defined in "Internet Relay Chat: Channel Management" [IRC-CHAN].
MODE #Finnish +imI !@*.fi ; Command to make #Finnish channel moderated and 'invite-only' with user with a hostname matching *.fi automatically invited.
MODE #Finnish +o Kilroy ; Command to give 'chanop' privileges to Kilroy on channel #Finnish.
MODE #Finnish +v Wiz ; Command to allow WiZ to speak on #Finnish.
MODE #Fins -s ; Command to remove 'secret' flag from channel #Fins.
MODE #42 +k oulu ; Command to set the channel key to "oulu".
MODE #42 -k oulu ; Command to remove the "oulu" channel key on channel "#42".
Kalt Informational [Page 18] RFC 2812 Internet Relay Chat: Client Protocol April 2000
MODE #eu-opers +l 10 ; Command to set the limit for the number of users on channel "#eu-opers" to 10.
:firstname.lastname@example.com MODE #eu-opers -l ; User "WiZ" removing the limit for the number of users on channel "#eu- opers".
MODE &oulu +b ; Command to list ban masks set for the channel "&oulu".
MODE &oulu +b !@* ; Command to prevent all users from joining.
MODE &oulu +b !@.edu +e *!@*.bu.edu ; Command to prevent any user from a hostname matching *.edu from joining, except if matching *.bu.edu
MODE #bu +be !@.edu *!@*.bu.edu ; Comment to prevent any user from a hostname matching *.edu from joining, except if matching *.bu.edu
MODE #meditation e ; Command to list exception masks set for the channel "#meditation".
MODE #meditation I ; Command to list invitations masks set for the channel "#meditation".
MODE !12345ircd O ; Command to ask who the channel creator for "!12345ircd" is
3.2.4 Topic message
Command: TOPIC
The TOPIC command is used to change or view the topic of a channel.
The topic for channel
Kalt Informational [Page 19] RFC 2812 Internet Relay Chat: Client Protocol April 2000
Numeric Replies:
:firstname.lastname@example.com TOPIC #test :New topic ; User Wiz setting the topic.
TOPIC #test :another topic ; Command to set the topic on #test to "another topic".
TOPIC #test : ; Command to clear the topic on #test.
TOPIC #test ; Command to check the topic for #test.
3.2.5 Names message
Command: NAMES
Parameters: [
By using the NAMES command, a user can list all nicknames that are
visible to him. For more details on what is visible and what is not,
see "Internet Relay Chat: Channel Management" [IRC-CHAN]. The
If no
If the
Wildcards are allowed in the
Kalt Informational [Page 20] RFC 2812 Internet Relay Chat: Client Protocol April 2000
NAMES #twilightzone,#42 ; Command to list visible users on #twilightzone and #42
NAMES ; Command to list all visible channels and users
3.2.6 List message
Command: LIST
Parameters: [
The list command is used to list channels and their topics. If the
If the
Wildcards are allowed in the
Numeric Replies:
LIST ; Command to list all channels.
LIST #twilightzone,#42 ; Command to list channels #twilightzone and #42
3.2.7 Invite message
Command: INVITE
The INVITE command is used to invite a user to a channel. The
Kalt Informational [Page 21] RFC 2812 Internet Relay Chat: Client Protocol April 2000
Only the user inviting and the user being invited will receive notification of the invitation. Other channel members are not notified. (This is unlike the MODE changes, and is occasionally the source of trouble for users.)
Numeric Replies:
:email@example.com INVITE Wiz #Dust
; Message to WiZ when he has been
invited by user Angel to channel
INVITE Wiz #TwilightZone ; Command to invite WiZ to #Twilightzone
3.2.8 Kick command
Command: KICK
The KICK command can be used to request the forced removal of a user
from a channel. It causes the
The server MUST NOT send KICK messages with multiple channels or users to clients. This is necessarily to maintain backward compatibility with old client software.
Numeric Replies:
Kalt Informational [Page 22] RFC 2812 Internet Relay Chat: Client Protocol April 2000
KICK &Melbourne Matthew ; Command to kick Matthew from &Melbourne
KICK #Finnish John :Speaking English ; Command to kick John from #Finnish using "Speaking English" as the reason (comment).
:email@example.com KICK #Finnish John ; KICK message on channel #Finnish from WiZ to remove John from channel
3.3 Sending messages
The main purpose of the IRC protocol is to provide a base for clients to communicate with each other. PRIVMSG, NOTICE and SQUERY (described in Section 3.5 on Service Query and Commands) are the only messages available which actually perform delivery of a text message from one client to another - the rest just make it possible and try to ensure it happens in a reliable and structured manner.
3.3.1 Private messages
Command: PRIVMSG
PRIVMSG is used to send private messages between users, as well as to
send messages to channels.
Numeric Replies:
Kalt Informational [Page 23] RFC 2812 Internet Relay Chat: Client Protocol April 2000
:firstname.lastname@example.com PRIVMSG Wiz :Are you receiving this message ? ; Message from Angel to Wiz.
PRIVMSG Angel :yes I'm receiving it ! ; Command to send a message to Angel.
PRIVMSG firstname.lastname@example.com :Hello ! ; Command to send a message to a user on server tolsun.oulu.fi with username of "jto".
PRIVMSG email@example.com :Are you a frog? ; Message to a user on server irc.stealth.net with username of "kalt", and connected from the host millennium.stealth.net.
PRIVMSG kalt%millennium.stealth.net :Do you like cheese? ; Message to a user on the local server with username of "kalt", and connected from the host millennium.stealth.net.
PRIVMSG email@example.com :Hello ! ; Message to the user with nickname Wiz who is connected from the host tolsun.oulu.fi and has the username "jto".
PRIVMSG $*.fi :Server tolsun.oulu.fi rebooting. ; Message to everyone on a server which has a name matching *.fi.
PRIVMSG #*.edu :NSFNet is undergoing work, expect interruptions ; Message to all users who come from a host which has a name matching *.edu.
3.3.2 Notice
Command: NOTICE
The NOTICE command is used similarly to PRIVMSG. The difference between NOTICE and PRIVMSG is that automatic replies MUST NEVER be sent in response to a NOTICE message. This rule applies to servers
Kalt Informational [Page 24] RFC 2812 Internet Relay Chat: Client Protocol April 2000
too - they MUST NOT send any error reply back to the client on receipt of a notice. The object of this rule is to avoid loops between clients automatically sending something in response to something it received.
This command is available to services as well as users.
This is typically used by services, and automatons (clients with either an AI or other interactive program controlling their actions).
See PRIVMSG for more details on replies and examples.
3.4 Server queries and commands
The server query group of commands has been designed to return information about any server which is connected to the network.
In these queries, where a parameter appears as
These messages typically have little value for services, it is therefore RECOMMENDED to forbid services from using them.
3.4.1 Motd message
Command: MOTD
Parameters: [
The MOTD command is used to get the "Message Of The Day" of the given
server, or current server if
Wildcards are allowed in the
Numeric Replies: RPLMOTDSTART RPLMOTD RPLENDOFMOTD ERRNOMOTD
3.4.2 Lusers message
Command: LUSERS
Parameters: [
The LUSERS command is used to get statistics about the size of the
IRC network. If no parameter is given, the reply will be about the
whole net. If a
Kalt Informational [Page 25] RFC 2812 Internet Relay Chat: Client Protocol April 2000
concern the part of the network formed by the servers matching the
mask. Finally, if the
Wildcards are allowed in the
Numeric Replies:
3.4.3 Version message
Command: VERSION
Parameters: [
The VERSION command is used to query the version of the server
program. An optional parameter
Wildcards are allowed in the
Numeric Replies:
VERSION tolsun.oulu.fi ; Command to check the version of server "tolsun.oulu.fi".
3.4.4 Stats message
Command: STATS
Parameters: [
The stats command is used to query statistics of certain server. If
A query may be given for any single letter which is only checked by the destination server and is otherwise passed on by intermediate servers, ignored and unaltered.
Wildcards are allowed in the
Kalt Informational [Page 26] RFC 2812 Internet Relay Chat: Client Protocol April 2000
Except for the ones below, the list of valid queries is implementation dependent. The standard queries below SHOULD be supported by the server:
l - returns a list of the server's connections, showing how
long each connection has been established and the
traffic over that connection in Kbytes and messages for
each direction;
m - returns the usage count for each of commands supported
by the server; commands for which the usage count is
zero MAY be omitted;
o - returns a list of configured privileged users,
u - returns a string showing how long the server has been
It is also RECOMMENDED that client and server access configuration be published this way.
Numeric Replies:
STATS m ; Command to check the command usage for the server you are connected to
3.4.5 Links message
Command: LINKS
Parameters: [ [
With LINKS, a user can list all servernames, which are known by the server answering the query. The returned list of servers MUST match the mask, or if no mask is given, the full list is returned.
Numeric Replies:
Kalt Informational [Page 27] RFC 2812 Internet Relay Chat: Client Protocol April 2000
LINKS *.au ; Command to list all servers which have a name that matches *.au;
LINKS *.edu *.bu.edu ; Command to list servers matching *.bu.edu as seen by the first server matching *.edu.
3.4.6 Time message
Command: TIME
Parameters: [
The time command is used to query local time from the specified
server. If the
Wildcards are allowed in the
Numeric Replies:
Examples: TIME tolsun.oulu.fi ; check the time on the server "tolson.oulu.fi"
3.4.7 Connect message
Command: CONNECT
The CONNECT command can be used to request a server to try to
establish a new connection to another server immediately. CONNECT is
a privileged command and SHOULD be available only to IRC Operators.
If a
The server receiving a remote CONNECT command SHOULD generate a WALLOPS message describing the source and target of the request.
Numeric Replies:
Kalt Informational [Page 28] RFC 2812 Internet Relay Chat: Client Protocol April 2000
CONNECT tolsun.oulu.fi 6667 ; Command to attempt to connect local server to tolsun.oulu.fi on port 6667
3.4.8 Trace message
Command: TRACE
Parameters: [
TRACE command is used to find the route to specific server and
information about its peers. Each server that processes this command
MUST report to the sender about it. The replies from pass-through
links form a chain, which shows route to destination. After sending
this reply back, the query MUST be sent to the next server until
TRACE command is used to find the route to specific server. Each
server that processes this message MUST tell the sender about it by
sending a reply indicating it is a pass-through link, forming a chain
of replies. After sending this reply back, it MUST then send the
TRACE message to the next server until given server is reached. If
If the destination given by
Wildcards are allowed in the
Numeric Replies:
If the TRACE message is destined for another server, all
intermediate servers must return a RPL_TRACELINK reply to indicate
that the TRACE passed through it and where it is going next.
Kalt Informational [Page 29] RFC 2812 Internet Relay Chat: Client Protocol April 2000
A TRACE reply may be composed of any number of the following
numeric replies.
TRACE *.oulu.fi ; TRACE to a server matching *.oulu.fi
3.4.9 Admin command
Command: ADMIN
Parameters: [
The admin command is used to find information about the administrator
of the given server, or current server if
Wildcards are allowed in the
Numeric Replies:
ADMIN tolsun.oulu.fi ; request an ADMIN reply from tolsun.oulu.fi
ADMIN syrk ; ADMIN request for the server to which the user syrk is connected
Kalt Informational [Page 30] RFC 2812 Internet Relay Chat: Client Protocol April 2000
3.4.10 Info command
Command: INFO
Parameters: [
The INFO command is REQUIRED to return information describing the server: its version, when it was compiled, the patchlevel, when it was started, and any other miscellaneous information which may be considered to be relevant.
Wildcards are allowed in the
Numeric Replies:
INFO csd.bu.edu ; request an INFO reply from csd.bu.edu
INFO Angel ; request info from the server that Angel is connected to.
3.5 Service Query and Commands
The service query group of commands has been designed to return information about any service which is connected to the network.
3.5.1 Servlist message
Command: SERVLIST
Parameters: [
The SERVLIST command is used to list services currently connected to the network and visible to the user issuing the command. The optional parameters may be used to restrict the result of the query (to matching services names, and services type).
Numeric Replies:
Kalt Informational [Page 31] RFC 2812 Internet Relay Chat: Client Protocol April 2000
3.5.2 Squery
Command: SQUERY
The SQUERY command is used similarly to PRIVMSG. The only difference is that the recipient MUST be a service. This is the only way for a text message to be delivered to a service.
See PRIVMSG for more details on replies and example.
SQUERY irchelp :HELP privmsg ; Message to the service with nickname irchelp.
SQUERY email@example.com :fr2en blaireau ; Message to the service with name firstname.lastname@example.com.
3.6 User based queries
User queries are a group of commands which are primarily concerned with finding details on a particular user or group users. When using wildcards with any of these commands, if they match, they will only return information on users who are 'visible' to you. The visibility of a user is determined as a combination of the user's mode and the common set of channels you are both on.
Although services SHOULD NOT be using this class of message, they are allowed to.
3.6.1 Who query
Command: WHO
Parameters: [
The WHO command is used by a client to generate a query which returns
a list of information which 'matches' the
Kalt Informational [Page 32] RFC 2812 Internet Relay Chat: Client Protocol April 2000
If the "o" parameter is passed only operators are returned according
to the
Numeric Replies:
WHO .fi ; Command to list all users who match against ".fi".
WHO jto* o ; Command to list all users with a match against "jto*" if they are an operator.
3.6.2 Whois query
Command: WHOIS
Parameters: [
This command is used to query information about particular user.
The server will answer this command with several numeric messages
indicating different statuses of each user which matches the mask (if
you are entitled to see them). If no wildcard is present in the
If the
Wildcards are allowed in the
Numeric Replies:
Kalt Informational [Page 33] RFC 2812 Internet Relay Chat: Client Protocol April 2000
WHOIS wiz ; return available user information about nick WiZ
WHOIS eff.org trillian ; ask server eff.org for user information about trillian
3.6.3 Whowas
Command: WHOWAS
Whowas asks for information about a nickname which no longer exists.
This may either be due to a nickname change or the user leaving IRC.
In response to this query, the server searches through its nickname
history, looking for any nicks which are lexically the same (no wild
card matching here). The history is searched backward, returning the
most recent entry first. If there are multiple entries, up to
Wildcards are allowed in the
Numeric Replies:
WHOWAS Wiz ; return all information in the nick history about nick "WiZ";
WHOWAS Mermaid 9 ; return at most, the 9 most recent entries in the nick history for "Mermaid";
WHOWAS Trillian 1 .edu ; return the most recent history for "Trillian" from the first server found to match ".edu".
3.7 Miscellaneous messages
Messages in this category do not fit into any of the above categories but are nonetheless still a part of and REQUIRED by the protocol.
Kalt Informational [Page 34] RFC 2812 Internet Relay Chat: Client Protocol April 2000
3.7.1 Kill message
Command: KILL
The KILL command is used to cause a client-server connection to be closed by the server which has the actual connection. Servers generate KILL messages on nickname collisions. It MAY also be available available to users who have the operator status.
Clients which have automatic reconnect algorithms effectively make this command useless since the disconnection is only brief. It does however break the flow of data and can be used to stop large amounts of 'flooding' from abusive users or accidents. Abusive users usually don't care as they will reconnect promptly and resume their abusive behaviour. To prevent this command from being abused, any user may elect to receive KILL messages generated for others to keep an 'eye' on would be trouble spots.
In an arena where nicknames are REQUIRED to be globally unique at all times, KILL messages are sent whenever 'duplicates' are detected (that is an attempt to register two users with the same nickname) in the hope that both of them will disappear and only 1 reappear.
When a client is removed as the result of a KILL message, the server SHOULD add the nickname to the list of unavailable nicknames in an attempt to avoid clients to reuse this name immediately which is usually the pattern of abusive behaviour often leading to useless "KILL loops". See the "IRC Server Protocol" document [IRC-SERVER] for more information on this procedure.
The comment given MUST reflect the actual reason for the KILL. For server-generated KILLs it usually is made up of details concerning the origins of the two conflicting nicknames. For users it is left up to them to provide an adequate reason to satisfy others who see it. To prevent/discourage fake KILLs from being generated to hide the identify of the KILLer, the comment also shows a 'kill-path' which is updated by each server it passes through, each prepending its name to the path.
Numeric Replies:
Kalt Informational [Page 35] RFC 2812 Internet Relay Chat: Client Protocol April 2000
NOTE: It is RECOMMENDED that only Operators be allowed to kill other users with KILL command. This command has been the subject of many controversies over the years, and along with the above recommendation, it is also widely recognized that not even operators should be allowed to kill users on remote servers.
3.7.2 Ping message
Command: PING
The PING command is used to test the presence of an active client or server at the other end of the connection. Servers send a PING message at regular intervals if no other activity detected coming from a connection. If a connection fails to respond to a PING message within a set amount of time, that connection is closed. A PING message MAY be sent even if the connection is active.
When a PING message is received, the appropriate PONG message MUST be
sent as reply to
Numeric Replies:
PING tolsun.oulu.fi ; Command to send a PING message to server
PING WiZ tolsun.oulu.fi ; Command from WiZ to send a PING message to server "tolsun.oulu.fi"
PING :irc.funet.fi ; Ping message sent by server "irc.funet.fi"
Kalt Informational [Page 36] RFC 2812 Internet Relay Chat: Client Protocol April 2000
3.7.3 Pong message
Command: PONG
PONG message is a reply to ping message. If parameter
Numeric Replies:
PONG csd.bu.edu tolsun.oulu.fi ; PONG message from csd.bu.edu to tolsun.oulu.fi
3.7.4 Error
Command: ERROR
The ERROR command is for use by servers when reporting a serious or fatal error to its peers. It may also be sent from one server to another but MUST NOT be accepted from any normal unknown clients.
Only an ERROR message SHOULD be used for reporting errors which occur with a server-to-server link. An ERROR message is sent to the server at the other end (which reports it to appropriate local users and logs) and to appropriate local users and logs. It is not to be passed onto any other servers by a server if it is received from a server.
The ERROR message is also used before terminating a client connection.
When a server sends a received ERROR message to its operators, the message SHOULD be encapsulated inside a NOTICE message, indicating that the client was not responsible for the error.
Kalt Informational [Page 37] RFC 2812 Internet Relay Chat: Client Protocol April 2000
ERROR :Server *.fi already exists ; ERROR message to the other server which caused this error.
NOTICE WiZ :ERROR from csd.bu.edu — Server *.fi already exists ; Same ERROR message as above but sent to user WiZ on the other server.
Optional features
This section describes OPTIONAL messages. They are not required in a working server implementation of the protocol described herein. In the absence of the feature, an error reply message MUST be generated or an unknown command error. If the message is destined for another server to answer then it MUST be passed on (elementary parsing REQUIRED) The allocated numerics for this are listed with the messages below.
From this section, only the USERHOST and ISON messages are available to services.
4.1 Away
Command: AWAY
Parameters: [
With the AWAY command, clients can set an automatic reply string for any PRIVMSG commands directed at them (not to a channel they are on). The server sends an automatic reply to the client sending the PRIVMSG command. The only replying server is the one to which the sending client is connected to.
The AWAY command is used either with one parameter, to set an AWAY message, or with no parameters, to remove the AWAY message.
Because of its high cost (memory and bandwidth wise), the AWAY message SHOULD only be used for client-server communication. A server MAY choose to silently ignore AWAY messages received from other servers. To update the away status of a client across servers, the user mode 'a' SHOULD be used instead. (See Section 3.1.5)
Numeric Replies:
Kalt Informational [Page 38] RFC 2812 Internet Relay Chat: Client Protocol April 2000
AWAY :Gone to lunch. Back in 5 ; Command to set away message to "Gone to lunch. Back in 5".
4.2 Rehash message
Command: REHASH
Parameters: None
The rehash command is an administrative command which can be used by an operator to force the server to re-read and process its configuration file.
Numeric Replies:
REHASH ; message from user with operator status to server asking it to reread its configuration file.
4.3 Die message
Command: DIE
Parameters: None
An operator can use the DIE command to shutdown the server. This message is optional since it may be viewed as a risk to allow arbitrary people to connect to a server as an operator and execute this command.
The DIE command MUST always be fully processed by the server to which the sending client is connected and MUST NOT be passed onto other connected servers.
Numeric Replies:
DIE ; no parameters required.
Kalt Informational [Page 39] RFC 2812 Internet Relay Chat: Client Protocol April 2000
4.4 Restart message
Command: RESTART
Parameters: None
An operator can use the restart command to force the server to restart itself. This message is optional since it may be viewed as a risk to allow arbitrary people to connect to a server as an operator and execute this command, causing (at least) a disruption to service.
The RESTART command MUST always be fully processed by the server to which the sending client is connected and MUST NOT be passed onto other connected servers.
Numeric Replies:
RESTART ; no parameters required.
4.5 Summon message
Command: SUMMON
The SUMMON command can be used to give users who are on a host running an IRC server a message asking them to please join IRC. This message is only sent if the target server (a) has SUMMON enabled, (b) the user is logged in and (c) the server process can write to the user's tty (or similar).
If no
If summon is not enabled in a server, it MUST return the ERR_SUMMONDISABLED numeric.
Numeric Replies:
Kalt Informational [Page 40] RFC 2812 Internet Relay Chat: Client Protocol April 2000
SUMMON jto ; summon user jto on the server's host
SUMMON jto tolsun.oulu.fi ; summon user jto on the host which a server named "tolsun.oulu.fi" is running.
4.6 Users
Command: USERS
Parameters: [
The USERS command returns a list of users logged into the server in a format similar to the UNIX commands who(1), rusers(1) and finger(1). If disabled, the correct numeric MUST be returned to indicate this.
Because of the security implications of such a command, it SHOULD be disabled by default in server implementations. Enabling it SHOULD require recompiling the server or some equivalent change rather than simply toggling an option and restarting the server. The procedure to enable this command SHOULD also include suitable large comments.
Numeric Replies:
Disabled Reply:
USERS eff.org ; request a list of users logged in on server eff.org
4.7 Operwall message
Command: WALLOPS
The WALLOPS command is used to send a message to all currently connected users who have set the 'w' user mode for themselves. (See Section 3.1.5 "User modes").
Kalt Informational [Page 41] RFC 2812 Internet Relay Chat: Client Protocol April 2000
After implementing WALLOPS as a user command it was found that it was often and commonly abused as a means of sending a message to a lot of people. Due to this, it is RECOMMENDED that the implementation of WALLOPS allows and recognizes only servers as the originators of WALLOPS.
Numeric Replies:
:csd.bu.edu WALLOPS :Connect '*.uiuc.edu 6667' from Joshua ; WALLOPS message from csd.bu.edu announcing a CONNECT message it received from Joshua and acted upon.
4.8 Userhost message
Command: USERHOST
The USERHOST command takes a list of up to 5 nicknames, each separated by a space character and returns a list of information about each nickname that it found. The returned list has each reply separated by a space.
Numeric Replies:
USERHOST Wiz Michael syrk ; USERHOST request for information on nicks "Wiz", "Michael", and "syrk"
:ircd.stealth.net 302 yournick :email@example.com ; Reply for user syrk
4.9 Ison message
Command: ISON
The ISON command was implemented to provide a quick and efficient means to get a response about whether a given nickname was currently on IRC. ISON only takes one (1) type of parameter: a space-separated list of nicks. For each nickname in the list that is present, the
Kalt Informational [Page 42] RFC 2812 Internet Relay Chat: Client Protocol April 2000
server adds that to its reply string. Thus the reply string may return empty (none of the given nicks are present), an exact copy of the parameter string (all of them present) or any other subset of the set of nicks given in the parameter. The only limit on the number of nicks that may be checked is that the combined length MUST NOT be too large as to cause the server to chop it off so it fits in 512 characters.
ISON is only processed by the server local to the client sending the command and thus not passed onto other servers for further processing.
Numeric Replies:
ISON phone trillian WiZ jarlek Avalon Angel Monstah syrk ; Sample ISON request for 7 nicks.
The following is a list of numeric replies which are generated in response to the commands given above. Each numeric is given with its number, name and reply string.
5.1 Command responses
Numerics in the range from 001 to 099 are used for client-server connections only and should never travel between servers. Replies generated in the response to commands are found in the range from 200 to 399.
"Welcome to the Internet Relay Network
"Your host is <servername>, running version <ver>"
"This server was created <date>"
"<servername> <version> <available user modes>
<available channel modes>"
- The server sends Replies 001 to 004 to a user upon
successful registration.
Kalt Informational [Page 43] RFC 2812 Internet Relay Chat: Client Protocol April 2000
"Try server <server name>, port <port number>"
- Sent by the server to a user to suggest an alternative
server. This is often used when the connection is
refused because the server is already full.
":*1<reply> *( " " <reply> )"
- Reply format used by USERHOST to list replies to
the query list. The reply string is composed as
reply = nickname [ "*" ] "=" ( "+" / "-" ) hostname
The '*' indicates whether the client has registered
as an Operator. The '-' or '+' characters represent
whether the client has set an AWAY message or not
":*1<nick> *( " " <nick> )"
- Reply format used by ISON to list replies to the
query list.
"<nick> :<away message>"
":You are no longer marked as being away"
":You have been marked as being away"
- These replies are used with the AWAY command (if
allowed). RPL_AWAY is sent to any client sending a
PRIVMSG to a client which is away. RPL_AWAY is only
sent by the server to which the client is connected.
Replies RPL_UNAWAY and RPL_NOWAWAY are sent when the
client removes and sets an AWAY message.
"<nick> <user> <host> * :<real name>"
"<nick> <server> :<server info>"
"<nick> :is an IRC operator"
Kalt Informational [Page 44] RFC 2812 Internet Relay Chat: Client Protocol April 2000
"<nick> <integer> :seconds idle"
"<nick> :End of WHOIS list"
"<nick> :*( ( "@" / "+" ) <channel> " " )"
- Replies 311 - 313, 317 - 319 are all replies
generated in response to a WHOIS message. Given that
there are enough parameters present, the answering
server MUST either formulate a reply out of the above
numerics (if the query nick is found) or return an
error reply. The '*' in RPL_WHOISUSER is there as
the literal character and not as a wild card. For
each reply set, only RPL_WHOISCHANNELS may appear
more than once (for long lists of channel names).
The '@' and '+' characters next to the channel name
indicate whether a client is a channel operator or
has been granted permission to speak on a moderated
channel. The RPL_ENDOFWHOIS reply is used to mark
the end of processing a WHOIS message.
"<nick> <user> <host> * :<real name>"
"<nick> :End of WHOWAS"
- When replying to a WHOWAS message, a server MUST use
the replies RPL_WHOWASUSER, RPL_WHOISSERVER or
ERR_WASNOSUCHNICK for each nickname in the presented
list. At the end of all reply batches, there MUST
be RPL_ENDOFWHOWAS (even if there was only one reply
and it was an error).
Obsolete. Not used.
"<channel> <# visible> :<topic>"
":End of LIST"
- Replies RPL_LIST, RPL_LISTEND mark the actual replies
with data and end of the server's response to a LIST
command. If there are no channels available to return,
only the end reply MUST be sent.
Kalt Informational [Page 45] RFC 2812 Internet Relay Chat: Client Protocol April 2000
"<channel> <nickname>"
"<channel> <mode> <mode params>"
"<channel> :No topic is set"
"<channel> :<topic>"
- When sending a TOPIC message to determine the
channel topic, one of two replies is sent. If
the topic is set, RPL_TOPIC is sent back else
"<channel> <nick>"
- Returned by the server to indicate that the
attempted INVITE message was successful and is
being passed onto the end client.
"<user> :Summoning user to IRC"
- Returned by a server answering a SUMMON message to
indicate that it is summoning that user.
"<channel> <invitemask>"
"<channel> :End of channel invite list"
- When listing the 'invitations masks' for a given channel,
a server is required to send the list back using the
RPL_INVITELIST and RPL_ENDOFINVITELIST messages. A
separate RPL_INVITELIST is sent for each active mask.
After the masks have been listed (or if none present) a
RPL_ENDOFINVITELIST MUST be sent.
"<channel> <exceptionmask>"
"<channel> :End of channel exception list"
Kalt Informational [Page 46] RFC 2812 Internet Relay Chat: Client Protocol April 2000
- When listing the 'exception masks' for a given channel,
a server is required to send the list back using the
RPL_EXCEPTLIST and RPL_ENDOFEXCEPTLIST messages. A
separate RPL_EXCEPTLIST is sent for each active mask.
After the masks have been listed (or if none present)
a RPL_ENDOFEXCEPTLIST MUST be sent.
"<version>.<debuglevel> <server> :<comments>"
- Reply by the server showing its version details.
The <version> is the version of the software being
used (including any patchlevel revisions) and the
<debuglevel> is used to indicate if the server is
running in "debug mode".
The "comments" field may contain any comments about
the version or further version details.
"<channel> <user> <host> <server> <nick>
:<hopcount> <real name>"
"<name> :End of WHO list"
- The RPL_WHOREPLY and RPL_ENDOFWHO pair are used
to answer a WHO message. The RPL_WHOREPLY is only
sent if there is an appropriate match to the WHO
query. If there is a list of parameters supplied
with a WHO message, a RPL_ENDOFWHO MUST be sent
after processing each list item with <name> being
the item.
"( "=" / "*" / "@" ) <channel>
:[ "@" / "+" ] <nick> *( " " [ "@" / "+" ] <nick> )
- "@" is used for secret channels, "*" for private
channels, and "=" for others (public channels).
"<channel> :End of NAMES list"
- To reply to a NAMES message, a reply pair consisting
of RPL_NAMREPLY and RPL_ENDOFNAMES is sent by the
server back to the client. If there is no channel
found as in the query, then only RPL_ENDOFNAMES is
Kalt Informational [Page 47] RFC 2812 Internet Relay Chat: Client Protocol April 2000
returned. The exception to this is when a NAMES
message is sent with no parameters and all visible
channels and contents are sent back in a series of
RPL_NAMEREPLY messages with a RPL_ENDOFNAMES to mark
the end.
"<mask> <server> :<hopcount> <server info>"
"<mask> :End of LINKS list"
- In replying to the LINKS message, a server MUST send
replies back using the RPL_LINKS numeric and mark the
end of the list using an RPL_ENDOFLINKS reply.
"<channel> <banmask>"
"<channel> :End of channel ban list"
- When listing the active 'bans' for a given channel,
a server is required to send the list back using the
RPL_BANLIST and RPL_ENDOFBANLIST messages. A separate
RPL_BANLIST is sent for each active banmask. After the
banmasks have been listed (or if none present) a
RPL_ENDOFBANLIST MUST be sent.
":End of INFO list"
- A server responding to an INFO message is required to
send all its 'info' in a series of RPL_INFO messages
with a RPL_ENDOFINFO reply to indicate the end of the
":- <server> Message of the day - "
":- <text>"
":End of MOTD command"
- When responding to the MOTD message and the MOTD file
is found, the file is displayed line by line, with
each line no longer than 80 characters, using
Kalt Informational [Page 48] RFC 2812 Internet Relay Chat: Client Protocol April 2000
RPL_MOTD format replies. These MUST be surrounded
by a RPL_MOTDSTART (before the RPL_MOTDs) and an
RPL_ENDOFMOTD (after).
":You are now an IRC operator"
- RPL_YOUREOPER is sent back to a client which has
just successfully issued an OPER message and gained
operator status.
"<config file> :Rehashing"
- If the REHASH option is used and an operator sends
a REHASH message, an RPL_REHASHING is sent back to
the operator.
"You are service <servicename>"
- Sent by the server to a service upon successful
"<server> :<string showing server's local time>"
- When replying to the TIME message, a server MUST send
the reply using the RPL_TIME format above. The string
showing the time need only contain the correct day and
time there. There is no further requirement for the
time string.
":UserID Terminal Host"
":<username> <ttyline> <hostname>"
":End of users"
":Nobody logged in"
- If the USERS message is handled by a server, the
replies RPL_USERSTART, RPL_USERS, RPL_ENDOFUSERS and
RPL_NOUSERS are used. RPL_USERSSTART MUST be sent
first, following by either a sequence of RPL_USERS
or a single RPL_NOUSER. Following this is
Kalt Informational [Page 49] RFC 2812 Internet Relay Chat: Client Protocol April 2000
"Link <version & debug level> <destination>
<next server> V<protocol version>
<link uptime in seconds> <backstream sendq>
<upstream sendq>"
"Try. <class> <server>"
"H.S. <class> <server>"
"???? <class> [<client IP address in dot form>]"
"Oper <class> <nick>"
"User <class> <nick>"
"Serv <class> <int>S <int>C <server>
<nick!user|*!*>@<host|server> V<protocol version>"
"Service <class> <name> <type> <active type>"
"<newtype> 0 <client name>"
"Class <class> <count>"
"File <logfile> <debug level>"
"<server name> <version & debug level> :End of TRACE"
- The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
Kalt Informational [Page 50] RFC 2812 Internet Relay Chat: Client Protocol April 2000
RPL_TRACENEWTYPE is to be used for any connection
which does not fit in the other categories but is
being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
"<linkname> <sendq> <sent messages>
<sent Kbytes> <received messages>
<received Kbytes> <time open>"
- reports statistics on a connection. <linkname>
identifies the particular connection, <sendq> is
the amount of data that is queued and waiting to be
sent <sent messages> the number of messages sent,
and <sent Kbytes> the amount of data sent, in
Kbytes. <received messages> and <received Kbytes>
are the equivalent of <sent messages> and <sent
Kbytes> for received data, respectively. <time
open> indicates how long ago the connection was
opened, in seconds.
"<command> <count> <byte count> <remote count>"
- reports statistics on commands usage.
"<stats letter> :End of STATS report"
":Server Up %d days %d:%02d:%02d"
- reports the server uptime.
"O <hostmask> * <name>"
- reports the allowed hosts from where user may become IRC
"<user mode string>"
- To answer a query about a client's own mode,
RPL_UMODEIS is sent back.
"<name> <server> <mask> <type> <hopcount> <info>"
Kalt Informational [Page 51] RFC 2812 Internet Relay Chat: Client Protocol April 2000
"<mask> <type> :End of service listing"
- When listing services in reply to a SERVLIST message,
a server is required to send the list back using the
RPL_SERVLIST and RPL_SERVLISTEND messages. A separate
RPL_SERVLIST is sent for each service. After the
services have been listed (or if none present) a
RPL_SERVLISTEND MUST be sent.
":There are <integer> users and <integer>
services on <integer> servers"
"<integer> :operator(s) online"
"<integer> :unknown connection(s)"
"<integer> :channels formed"
":I have <integer> clients and <integer>
- In processing an LUSERS message, the server
sends a set of replies from RPL_LUSERCLIENT,
RPL_LUSERCHANNELS and RPL_LUSERME. When
replying, a server MUST send back
RPL_LUSERCLIENT and RPL_LUSERME. The other
replies are only sent back if a non-zero count
is found for them.
"<server> :Administrative info"
":<admin info>"
":<admin info>"
":<admin info>"
- When replying to an ADMIN message, a server
is expected to use replies RPL_ADMINME
through to RPL_ADMINEMAIL and provide a text
message with each. For RPL_ADMINLOC1 a
description of what city, state and country
the server is in is expected, followed by
details of the institution (RPL_ADMINLOC2)
Kalt Informational [Page 52] RFC 2812 Internet Relay Chat: Client Protocol April 2000
and finally the administrative contact for the
server (an email address here is REQUIRED)
in RPL_ADMINEMAIL.
"<command> :Please wait a while and try again."
- When a server drops a command without processing it,
it MUST use the reply RPL_TRYAGAIN to inform the
originating client.
5.2 Error Replies
Error replies are found in the range from 400 to 599.
"<nickname> :No such nick/channel"
- Used to indicate the nickname parameter supplied to a
command is currently unused.
"<server name> :No such server"
- Used to indicate the server name given currently
does not exist.
"<channel name> :No such channel"
- Used to indicate the given channel name is invalid.
"<channel name> :Cannot send to channel"
- Sent to a user who is either (a) not on a channel
which is mode +n or (b) not a chanop (or mode +v) on
a channel which has mode +m set or where the user is
banned and is trying to send a PRIVMSG message to
that channel.
"<channel name> :You have joined too many channels"
- Sent to a user when they have joined the maximum
number of allowed channels and they try to join
another channel.
Kalt Informational [Page 53] RFC 2812 Internet Relay Chat: Client Protocol April 2000
"<nickname> :There was no such nickname"
- Returned by WHOWAS to indicate there is no history
information for that nickname.
"<target> :<error code> recipients. <abort message>"
- Returned to a client which is attempting to send a
PRIVMSG/NOTICE using the user@host destination format
and for a user@host which has several occurrences.
- Returned to a client which trying to send a
PRIVMSG/NOTICE to too many recipients.
- Returned to a client which is attempting to JOIN a safe
channel using the shortname when there are more than one
such channel.
"<service name> :No such service"
- Returned to a client which is attempting to send a SQUERY
to a service which does not exist.
":No origin specified"
- PING or PONG message missing the originator parameter.
":No recipient given (<command>)"
":No text to send"
"<mask> :No toplevel domain specified"
"<mask> :Wildcard in toplevel domain"
"<mask> :Bad Server/host mask"
- 412 - 415 are returned by PRIVMSG to indicate that
the message wasn't delivered for some reason.
ERR_NOTOPLEVEL and ERR_WILDTOPLEVEL are errors that
are returned when an invalid use of
"PRIVMSG $<server>" or "PRIVMSG #<host>" is attempted.
Kalt Informational [Page 54] RFC 2812 Internet Relay Chat: Client Protocol April 2000
"<command> :Unknown command"
- Returned to a registered client to indicate that the
command sent is unknown by the server.
":MOTD File is missing"
- Server's MOTD file could not be opened by the server.
"<server> :No administrative info available"
- Returned by a server in response to an ADMIN message
when there is an error in finding the appropriate
":File error doing <file op> on <file>"
- Generic error message used to report a failed file
operation during the processing of a message.
":No nickname given"
- Returned when a nickname parameter expected for a
command and isn't found.
"<nick> :Erroneous nickname"
- Returned after receiving a NICK message which contains
characters which do not fall in the defined set. See
section 2.3.1 for details on valid nicknames.
"<nick> :Nickname is already in use"
- Returned when a NICK message is processed that results
in an attempt to change to a currently existing
Kalt Informational [Page 55] RFC 2812 Internet Relay Chat: Client Protocol April 2000
"<nick> :Nickname collision KILL from <user>@<host>"
- Returned by a server to a client when it detects a
nickname collision (registered of a NICK that
already exists by another server).
"<nick/channel> :Nick/channel is temporarily unavailable"
- Returned by a server to a user trying to join a channel
currently blocked by the channel delay mechanism.
- Returned by a server to a user trying to change nickname
when the desired nickname is blocked by the nick delay
"<nick> <channel> :They aren't on that channel"
- Returned by the server to indicate that the target
user of the command is not on the given channel.
"<channel> :You're not on that channel"
- Returned by the server whenever a client tries to
perform a channel affecting command for which the
client isn't a member.
"<user> <channel> :is already on channel"
- Returned when a client tries to invite a user to a
channel they are already on.
"<user> :User not logged in"
- Returned by the summon after a SUMMON command for a
user was unable to be performed since they were not
logged in.
Kalt Informational [Page 56] RFC 2812 Internet Relay Chat: Client Protocol April 2000
":SUMMON has been disabled"
- Returned as a response to the SUMMON command. MUST be
returned by any server which doesn't implement it.
":USERS has been disabled"
- Returned as a response to the USERS command. MUST be
returned by any server which does not implement it.
":You have not registered"
- Returned by the server to indicate that the client
MUST be registered before the server will allow it
to be parsed in detail.
"<command> :Not enough parameters"
- Returned by the server by numerous commands to
indicate to the client that it didn't supply enough
":Unauthorized command (already registered)"
- Returned by the server to any link which tries to
change part of the registered details (such as
password or user details from second USER message).
":Your host isn't among the privileged"
- Returned to a client which attempts to register with
a server which does not been setup to allow
connections from the host the attempted connection
is tried.
":Password incorrect"
- Returned to indicate a failed attempt at registering
a connection for which a password was required and
was either not given or incorrect.
Kalt Informational [Page 57] RFC 2812 Internet Relay Chat: Client Protocol April 2000
":You are banned from this server"
- Returned after an attempt to connect and register
yourself with a server which has been setup to
explicitly deny connections to you.
- Sent by a server to a user to inform that access to the
server will soon be denied.
"<channel> :Channel key already set"
"<channel> :Cannot join channel (+l)"
"<char> :is unknown mode char to me for <channel>"
"<channel> :Cannot join channel (+i)"
"<channel> :Cannot join channel (+b)"
"<channel> :Cannot join channel (+k)"
"<channel> :Bad Channel Mask"
"<channel> :Channel doesn't support modes"
"<channel> <char> :Channel list is full"
":Permission Denied- You're not an IRC operator"
- Any command requiring operator privileges to operate
MUST return this error to indicate the attempt was
"<channel> :You're not channel operator"
- Any command requiring 'chanop' privileges (such as
MODE messages) MUST return this error if the client
making the attempt is not a chanop on the specified
Kalt Informational [Page 58] RFC 2812 Internet Relay Chat: Client Protocol April 2000
":You can't kill a server!"
- Any attempts to use the KILL command on a server
are to be refused and this error returned directly
to the client.
":Your connection is restricted!"
- Sent by the server to a user upon connection to indicate
the restricted nature of the connection (user mode "+r").
":You're not the original channel operator"
- Any MODE requiring "channel creator" privileges MUST
return this error if the client making the attempt is not
a chanop on the specified channel.
":No O-lines for your host"
- If a client sends an OPER message and the server has
not been configured to allow connections from the
client's host as an operator, this error MUST be
":Unknown MODE flag"
- Returned by the server to indicate that a MODE
message was sent with a nickname parameter and that
the a mode flag sent was not recognized.
":Cannot change mode for other users"
- Error sent to any user trying to view or change the
user mode for a user other than themselves.
5.3 Reserved numerics
These numerics are not described above since they fall into one of the following categories:
- no longer in use;
Kalt Informational [Page 59] RFC 2812 Internet Relay Chat: Client Protocol April 2000
reserved for future planned use;
in current use but are part of a non-generic 'feature' of the current IRC server.
- Current implementations
The IRC software, version 2.10 is the only complete implementation of the IRC protocol (client and server). Because of the small amount of changes in the client protocol since the publication of RFC 1459 [IRC], implementations that follow it are likely to be compliant with this protocol or to require a small amount of changes to reach compliance.
- Current problems
There are a number of recognized problems with the IRC Client Protocol, and more generally with the IRC Server Protocol. In order to preserve backward compatibility with old clients, this protocol has almost not evolved since the publication of RFC 1459 [IRC].
7.1 Nicknames
The idea of the nickname on IRC is very convenient for users to use when talking to each other outside of a channel, but there is only a finite nickname space and being what they are, it's not uncommon for several people to want to use the same nick. If a nickname is chosen by two people using this protocol, either one will not succeed or both will removed by use of a server KILL (See Section 3.7.1).
Kalt Informational [Page 60] RFC 2812 Internet Relay Chat: Client Protocol April 2000
7.2 Limitation of wildcards
There is no way to escape the escape character "" (%x5C). While this isn't usually a problem, it makes it impossible to form a mask with a backslash character ("") preceding a wildcard.
7.3 Security considerations
Security issues related to this protocol are discussed in the "IRC Server Protocol" [IRC-SERVER] as they are mostly an issue for the server side of the connection.
Current support and availability
Mailing lists for IRC related discussion: General discussion: email@example.com Protocol development: firstname.lastname@example.com Software implementations: ftp://ftp.irc.org/irc/server ftp://ftp.funet.fi/pub/unix/irc ftp://ftp.irc.org/irc/clients Newsgroup: alt.irc
Parts of this document were copied from the RFC 1459 [IRC] which first formally documented the IRC Protocol. It has also benefited from many rounds of review and comments. In particular, the following people have made significant contributions to this document:
Matthew Green, Michael Neumayer, Volker Paulsen, Kurt Roeckx, Vesa Ruokonen, Magnus Tjernstrom, Stefan Zehl.
Kalt Informational [Page 61] RFC 2812 Internet Relay Chat: Client Protocol April 2000
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[HNAME] Braden, R., "Requirements for Internet Hosts — Application and Support", STD 3, RFC 1123, October 1989.
[IRC] Oikarinen, J. & D. Reed, "Internet Relay Chat Protocol", RFC 1459, May 1993.
[IRC-ARCH] Kalt, C., "Internet Relay Chat: Architecture", RFC 2810, April 2000.
[IRC-CHAN] Kalt, C., "Internet Relay Chat: Channel Management", RFC 2811, April 2000.
[IRC-SERVER] Kalt, C., "Internet Relay Chat: Server Protocol", RFC 2813, April 2000.
Author's Address
Christophe Kalt 99 Teaneck Rd, Apt #117 Ridgefield Park, NJ 07660 USA
EMail: email@example.com
Kalt Informational [Page 62] RFC 2812 Internet Relay Chat: Client Protocol April 2000
Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Funding for the RFC Editor function is currently provided by the Internet Society.
Kalt Informational [Page 63]


text:
The Grand Budapest Hotel opens to most U.S. theaters this Friday, March 21, 2014 after having been open in select U.S. theaters since March 7, 2014. Palm Beach County residents may still have issues trying to find a theater showing the film. Marketed as a comedy-drama, the well made film offers spats of laughter followed by boredom. I normally love quirky comedies especially those featuring Bill Murray and Jason Schwartzman like Rushmore, and though this film is worth seeing, it may be best left to seeing during a matinee or waiting for streaming via Netflix.
Throughout the movie, audiences are treated to quick scenes of a seemingly endless list of major stars, however the Budapest relies on accomplished actor Ralph Feinnes and relative newcomer Tony Revolori for the bulk of the film. Feinnes does a superb job, however I suspect the film will only appeal to a certain segment of the population due to its unconventional comedy. That said, the film will likely be seen by a large number of Americans so they can gain a glimpse of their favorite stars.
Feinnes plays M. Gustave, a concierge at the opulent hotel and has multiple affairs with the guests over the years. Revolori plays the role of Zero Moustafa which Gustave takes under his wing. The two end up in a caper of sorts, whereas Gustave becomes the heir to a priceless painting of one of his wealthy female guests and becomes wanted by the authorities.
Other stars of note are Jeff Goldblum, Jude Law, Harvey Keitel, F. Murray Abraham (the elder Zero Moustafa), Adrien Brody, Willem Defoe, Edward Norton, Tilda Swinton, Owen Wilson and many more.
Budapest was filmed in various parts of Germany and had its premiere there earlier this year. Worldwide the film has garnered over $25 million in gross receipts. It opened to a limited four theaters on March 7, 2014 in the U.S. and was able to earn $200,000 gross per screen - a major achievement.


text:
Jingjiang Oriental Hotel - Changsha
- Location:
- Address: Wuyi West Road 243, Changsha
- Tel: 0731-82685888-0 (Book this hotel, call 800-2682918)
- Hotel Name in Chinese: 长沙景江东方大酒店
- Lowest Price: $31
Jingjiang Oriental Hotel is located at Changsha shopping and entertainment areas, the junction of Wuyi Street and Huangxing Road, close to the bar street and walking street of business street.
- Prices not include 18% service fee and tax.
- Payment Method: pay using our secure online payment service or pay at the hotel at some hotels.
- Triple/quad occupancy may require an extra bed at extra cost.
Hotel Amenities
|Hotel Services
|Car rentals, Medical clinic service, Wake Up Call, Permanent English-speaking staff, Business Centre, Copy Service, E-mail, Fax Service, Typing Service
|Room Amenities
|Air conditioning, Alarm clock, Color Television, Telephone, Bath and Shower, Internet access
Hotel Amenities: Elevator, Parking, Business Floor or Executive Floor, Air-Conditioned Facilities, Beauty Salon, Sauna, Meeting Room, Deposit Box at Front Desk, Fire Detector, Chess & Playing Cards Room
Dining Facilities: Chinese Restaurant, Western Restaurant
Print the Taxi Directions
- Please drive me to Jingjiang Oriental Hotel - Changsha, thank you!
- 请送我到长沙景江东方大酒店,谢谢
- Address: Wuyi West Road 243, Changsha
- 地址: Wuyi West Road 243, Changsha
- Tel: 0731-82685888-0
Similar Hotels as Jingjiang Oriental Hotel - Changsha
Changsha Sanhe Hotel - Changsha
From: $ 31
The Park Hotel - Changsha
From: $ 31
Lai Peng Qingjing Hotel - Changsha
From: $ 31
Check out the list of all 162 hotels in Changsha


text:
Blu-ray 3D Disc Playback Support Coming to PlayStation 3 Next Week
Sony recently announced at the Tokyo Game Show, and on its PlayStation Blog, that 3-D Blu-Ray support will be coming next week with its latest software update, which is version 3.5. This update is due to be released on September 21.
This new feature expands the PS3's 3D capabilities – as you may recall, we added the ability to play stereoscopic 3D games with the 3.30 firmware update in April.
While support for Blu-ray 3D discs is the primary new feature within the 3.50 update, there will be a few additional features. We'll post more details on the blog prior to the firmware's release, so check back here on Monday.
via : Blu-ray 3D Disc Playback Support Coming to PlayStation 3 System Next Week @ PlayStation Blog


text:
Snapple a day
by Snapple Beverage Group
Product Type
16 fl oz glass
Nutritional Info
serving size 8fl oz;
servings per container 2;
calories 120;
fat 0g;
sodium 10mg;
total carb 30g;
sugars 26g;
protein 0g
water, high fructose corn syrup,pear juice from concentrate, banana puree, skim milk sugar, citric acid, cream, natural banana flavor with other natural flavors, pectin, ascorbic acid, beta cartotene, lactic acid
Review: Go Bananas
Posted: Mar 14, 2003 at 12:00 AM (Last Updated: Mar 12, 2003 at 4:22 PM)While in the past we've seen people cringe at the thought of a banana based beverage, this product is actually one of the better and more innovative Snapple flavors to hit the shelves in recent years. Specifically, it has a lite fruit flavor that has a mellow banana flavor (with hints of pear as well) that is refreshing and relatively natural tasting. If you consider this product among the realm of other 10% fruit juice based beverages, it's definitely among the cream of the crop. Overall, a job well done by Snapple -- innovative and tasty at the same time!


text:
MUST GO SOON!!! WEDDING Dress for sale
(size 10-12) and can be taken in or out by a seamstress. located in Jacksonville, AL. it was worn for LESS than an hour. from David's Bridal (Michelangelo brand) and It's in great condition. The original price was $2500.00 and I'd like to get $900.00 for it. (or best offer, willing to negotiate!) Has a pin up in the back for the train. its ivory and pearl with a lace design. I also have Jessica Simpson shoes that match that look like the came out of the box and the tool skirt that makes the dress "fluff" up for separate prices if interested!!
- Alterations: Can be altered to fit a size 10 or size 12.
- Preservation Method: It is still in the bag that was given to me at the time of purchase
- Terms of Sale: All Sales Final
- Original Owner:
- Has Original Receipt:
- Location: Jacksonville, AL
- Will Ship to: Anywhere at Buyer Expense
- Payment Methods Accepted: Other
Please read our BUYER'S GUIDE before purchasing a dress online.


text:
// Audio Recording
How I Got My Stupid Album on Spotify and iTunes (and You Can Too)By Evan Dashevsky 06.10.2015Read More >
Ableton Live 9 Suite
Bottom Line: In its latest iteration, Ableton Live 9 Suite is a powerful all-in-the-box solution for composing music, particularly electronic-influenced, but it's not for everyone.
Ableton Push
Bottom Line: The Ableton Push MIDI controller is a revelation in its admittedly very narrow target market; if you're an Ableton Live user, you absolutely have to try this thing.
Arturia V Collection 4
Bottom Line: The Arturia V Collection 4 gives you some of the best 1970s and 1980s synthesizers in virtually identical-sounding plug-ins; it's a stellar value, and sure weighs a heck of a lot less than having to lug all of the real things around.
Algoriddim Unveils DJay Pro With Spotify IntegrationBy Angela Moscaritolo 12.18.2014Read More >
Apogee One (for iPad & Mac)
Bottom Line: The Apogee One is a smartly conceived, excellent-sounding solution for personal music listening and recording on both Macs and iOS devices.
KRK Rokit 6 G3
Bottom Line: The budget-priced KRK Rokit 6 G3 is a sweet-sounding active studio monitor speaker with plenty of low-end, and a sonically accurate frequency response curve that's not fatiguing during long listening sessions.
Apple GarageBand 10 (for Mac)
Bottom Line: GarageBand is more powerful than ever, and now gives novices and pros alike easy recording built into every Mac. It's still the best way to get started recording or to learn piano or guitar on a computer.
Cakewalk SONAR X3
Bottom Line: Cakewalk retools the least expensive version of its flagship SONAR X3 digital audio workstation with exceptional results.
IK Multimedia iLoud
Bottom Line: The IK Multimedia iLoud is the ideal portable Bluetooth speaker if you're a musician on the go, thanks to its direct guitar input and studio monitor-like sound, but it doesn't fare quite as well for standard music listeners on the wireless front.
Focusrite Scarlett 18i8
Bottom Line: Focusrite scores on features, sound quality, and value with this well-priced audio interface with four mic preamps.


text:
Joe Scott is a contractor and real estate developer who built a thriving enterprise from a truck and a toolbox. He has negotiated thousands of business deals involving corporate executives, homeowners, bankers, laborers, and union officials. In addition, he has hired, and been hired by, individuals from every walk of life. Through these dealings, Joe has learned that all people fall into three types - givers, takers, and those who both give and take. Knowing how to recognize and cope with all three types is the key to his success. In this children's series, he hopes to instill in kids a good foundation for a happy and positive life. His first book, "The Joe Dial", released in 2011, is age appropriate for those who are 12 to 95 years old. The Friend Ship Friendesha series is based on the adult book, "The Joe Dial."
This interview is part of a 15-day virtual tour sponsored by the National Writing for Children Center, a showcase for children's book authors and illustrators.
Q: Congratulations on the release of your book, The Friend Ship Friendesha. What was your inspiration for it?
A: I took my inspiration from helping my children and grandchildren to build a good foundation for a happy and positive life. I wanted to promote anti-bullying, and to have them think positively, and see how they can effect others around them with good, positive vibes.
Q: When did your passion for children's books begin? Did you have a favorite book when you were a child?
A: I began writing the Friend Ship Friendesha series 4 years ago.
Q: Did you take any workshops or courses before you started writing?
A: No, I like to just relax at the end of the day, and let my mind write.
Q: How was your creative process like during the writing of this book and how long did it take you to complete it? Did you face any difficulties along the way?
A: I need total concentration and to be alone when I write. I found you need to put the time in, after all the family time is over, probably a couple of hours at the end of the day.
Q: What do you find most challenging about writing for children?
A: I wanted the books to be simple, short, and to the point. It has to make sense, and easy to understand the message.
Q: What is your writing schedule like and how do you balance it with your other work and family time?
A: I find after all the family time is done for the day, is the best time I can sit alone and write.
Q: Tell us about your publisher and how you found it.
A: I self published through Hillcrest Media, Inc. My co-writer offered many helpful suggestions with the process.
Q: What was it like working with an illustrator and how much control did you have over the artwork?
A: All the characters of the Friendeshans are based on members of my family, so I had a great amount of input as to their features and characteristics. They are all near and dear to my heart, and my illustrator was great at listening to what I wanted and making them come to life on the pages.
Q: Do you think that becoming an author entails sacrifices?
A: I think it does, both your sacrifices and those of your family. You need their support, and you need to be disciplined enough to make it happen.
Q: What advice would you give to aspiring children's writers? Do you know of any helpful resources you'd like to share?
A: Make your book short, simple, and to the point. Allow the children's characters solve their own problems, and make sure the message is easy to understand.
Q: What's on the horizon for you?
A: Book 1 and 2 are complete, book 3 is being illustrated now, and books 4 and 5 are in queue. I hope this series will continue for many years, developing each of the characters.


text:
I do free webinars for alumni associations. It's my way of giving back, and it's also a fun way to meet people and market my services. You can see examples of them HERE and HERE.
So, I was going back and forth with Georgetown University about a topic I had proposed entitled "Time Management for Misfits and Dreamers." They originally accepted the idea, then pushed back about six weeks in advance, since they had done a lot of time management already and they weren't sure to what extent Georgetown students would identify as Misfits and Dreamers. I explained the premise, that this was a very different type of time management, less about techniques and tools, and more about the attitudes and emotions we bring to time management. I think this is true in general, and doubly true for people in creative endeavors (the Misfits and Dreamers). I am very thankful that they decided to run this program, since it's something I believe in.
About a week before the webinar, I got an email from Georgetown telling me that this webinar had set a record for most registrants ever for one of their presentations! I can't tell you how happy I am that so many people found value in my webinar, and that Georgetown trusted me enough to let this move forward. I got a huge response as well to my offer of a free coaching session, and lots of people joined my eZine list.
Thanks to everyone who promoted and attended this event!
If you like this post, please consider following Dave Kaiser and Dark Matter Consulting on FaceBook and Twitter. Better yet, subscribe to my eZine, a $29 annual value, and get tips, tools and inspiration for creating a truly Extraordinary Life. Click HERE to subscribe.