I started using IRC at a young age, and I have always been fascinated with it. As a language exercise, I was thinking about programming a simple IRC client in Ruby with Shoes as a graphical front-end. My question to you, kind-sirs, what do I need to become familiar with to start on this great adventure (besides shoes and Ruby of course)? I imagine there is some-sort of specification on IRC Protocol. Any pointers?
Asked
Active
Viewed 1.3k times
5 Answers
31
An earlier post mentioned RFC1459. While it is a very good introduction to IRC, it has actually been superseded by RFCs 2810-2813. Here is a more complete list of documentation you need to program anything IRC-related:
- RFC1459 (original RFC; superseded, but still useful)
- RFC2810 (IRC architecture)
- RFC2811 (IRC channel management)
- RFC2812 (IRC client protocol)
- RFC2813 (IRC server protocol)
- CTCP specification
- DCC specification
- Updated CTCP specification (not all clients support this)
- ISupport (response code 005) draft (almost all servers support this nowadays)
- Client capabilities (CAP command) draft (supported by some servers/clients)
- IRCv3 standards and proposals (the future features of IRC, some of which are already widely supported)
-
Note that RFC2810-RFC2813 are written my IRCnet alone (after the great split). IRCnet is basically the only major network that supports `!` channels. 005 parsing and understanding each token is.. hard. Different networks support other channel modes (like `q`, `a` and `h` as owner, admin and halfop) – Johannes Kuhn Sep 26 '13 at 09:44
-
`005` parsing is not that complicated, actually. New tokens are not added often (even less so in the future now that IRCv3 is getting adopted), and parsing current ones is rather straightforward: https://github.com/cinchrb/cinch/blob/master/lib/cinch/isupport.rb – Hinrik Nov 25 '13 at 11:04
-
You don't parse all the tokens. You just parse a handful tokens, but not all. – Johannes Kuhn Nov 25 '13 at 12:37
-
E.g. you don't look for the `CNOTICE` or `CPRIVMSG` tokens. – Johannes Kuhn Nov 25 '13 at 12:39
-
1If you look closely, you'll see that the code there only has special cases for a few tokens, and assumes all other tokens are booleans (e.g `CNOTICE` or `CPRIVMSG`) or string values if they contain '=' (e.g. `SOMETHING=foobar`). So it supports any future tokens of those types. In fact, any special parsing of complex token values (like the value in `CHANMODES=b,k,l,imnpstr`) is just there for convenience. In the unlikely event that a new kind of token like that were added and the library didn't parse it specially yet, the user would still be able to access the value as a string. – Hinrik Nov 25 '13 at 18:00
7
I found this gem on Wikipedia. Sounds intimidating.
It's actually not.
Telnet onto an IRC Server and witness the simplicity of the protocol first hand. The hardest part is the handshake, after that its very simple.
FlySwat
- 172,459
- 74
- 246
- 311
2
I once implemented a client and a server with 2 more guys (as part of a course).
I can tell you that the RFC you were already linked to is great.
I'd also try simply sniffing a connection with an existing client to see for yourself how stuff work.
abyx
- 69,862
- 18
- 95
- 117
0
Not exactly an answer to your question, but it may be helpful. If you are using Ruby, I have found the Autumn Leaves project to be a great way to build an IRC bot using Ruby:
http://github.com/RISCfuture/autumn/tree/master
It is pretty much the Jibble of the Ruby world.
hernan43
- 805
- 1
- 8
- 18