Internet Relay Chat

Template:Lead too short Internet Relay Chat (IRC) is an application layer protocol that facilitates transfer of messages in the form of text. The chat process works on a client/server model of networking. IRC clients are computer programs that a user can install on their system. These clients are able to communicate with chat servers to transfer messages to other clients.<ref name="rfc 1459 1 introduction">Template:Cite IETF</ref> It is mainly designed for group communication in discussion forums, called channels,<ref>Template:Cite IETF</ref> but also allows one-to-one communication via private message<ref>Template:Cite IETF</ref> as well as chat and data transfer,<ref>Template:Cite web</ref> including file sharing.<ref>Template:Cite book</ref>

Client software is available for every major operating system that supports Internet access.<ref name=Sage>Template:Cite webTemplate:Dead link</ref> As of April 2011, the top 100 IRC networks served more than half a million users at a time,<ref name="irc networks top 100">Template:Cite web</ref> with hundreds of thousands of channels<ref name="irc networks top 100" /> operating on a total of roughly 1,500 servers<ref name="irc networks top 100" /> out of roughly 3,200 servers worldwide.<ref>Template:Cite web</ref>

Over the past decade IRC usage has been declining: since 2003 it has lost 60% of its users (from 1 million to about 400,000 in 2014) and half of its channels (from half a million in 2003).<ref>Template:Cite web</ref>

Template:IPstack

History Template:Anchor

IRC was created by Jarkko Oikarinen in August 1988 to replace a program called MUT (MultiUser Talk) on a BBS called OuluBox in Finland.<ref name="founding irc">Template:Cite web</ref> Oikarinen found inspiration in a chat system known as Bitnet Relay, which operated on the BITNET.<ref name="founding irc" />

IRC was used to report on the 1991 Soviet coup d'état attempt throughout a media blackout.<ref>Template:Cite web</ref> It was previously used in a similar fashion during the Gulf War.<ref>Template:Cite web</ref> Logs of these and other events are kept in the ibiblio archive.<ref>Template:Cite web</ref>

Technical information

IRC is an open protocol that uses T*****<ref name="rfc 1459 1 introduction" /> and, optionally, TLS. An IRC server can connect to other IRC servers to expand the IRC network.<ref>Template:Cite IETF</ref> Users access IRC networks by connecting a client to a server.<ref>Template:Cite IETF</ref> There are many client implementations, such as mIRC, HexChat and irssi, and server implementations, e.g. the original IRCd. Most IRC servers do not require users to register an account but a user will have to set a nickname before being connected.<ref>Template:Cite IETF</ref>

IRC was originally a plain text protocol <ref name="rfc 1459 1 introduction" /> (although later extended), which on request was assigned port 194/T***** by IANA.<ref>Template:Cite web</ref> However, the de facto standard has always been to run IRC on 6667/T*****<ref>Template:Cite IETF</ref> and nearby port numbers (for example T***** ports 6660–6669, 7000)<ref>Template:Cite book</ref> to avoid having to run the IRCd software with root privileges.

The protocol specified that characters were 8-bit but did not specify the character encoding the text was supposed to use.<ref name="rfc 1459 2.2 character codes">Template:Cite IETF</ref> This can cause problems when users using different clients and/or different platforms want to converse.

All client-to-server IRC protocols in use today are descended from the protocol implemented in the irc2.4.0 version of the IRC2 server, and documented in RFC 1459. Since RFC 1459 was published, the new features in the irc2.10 implementation led to the publication of several revised protocol documents (RFC 2810, RFC 2811, RFC 2812 and RFC 2813); however, these protocol changes have not been widely adopted among other implementations.Template:Citation needed

Although many specifications on the IRC protocol have been published, there is no official specification, as the protocol remains dynamic. Virtually no clients and very few servers rely strictly on the above RFCs as a reference.Template:Citation needed

Microsoft made an extension for IRC in 1998 via the proprietary IRCX.<ref>Template:Cite IETF</ref> They later stopped distributing software supporting IRCX, instead developing the proprietary MSNP.

The standard structure of a network of IRC servers is a tree.<ref>Template:Cite IETF</ref> Messages are routed along only necessary branches of the tree but network state is sent to every server<ref>Template:Cite IETF</ref> and there is generally a high degree of implicit trust between servers. This architecture has a number of problems. A misbehaving or malicious server can cause major damage to the network<ref>Template:Cite IETF</ref> and any changes in structure, whether intentional or a result of conditions on the underlying network, require a net-split and net-join. This results in a lot of network traffic and spurious quit/join messages to users<ref>Template:Cite IETF</ref> and temporary loss of communication to users on the splitting servers. Adding a server to a large network means a large background bandwidth load on the network and a large memory load on the server. Once established however, each message to multiple recipients is delivered in a fashion similar to multicast, meaning each message travels a network link exactly once.<ref>Template:Cite IETF</ref> This is a strength in comparison to non-multicasting protocols such as Simple Mail Transfer Protocol (SMTP) or Extensible Messaging and Presence Protocol (XMPP).

An IRC daemon can also be used on a local area network (LAN). IRC can thus be used to facilitate communication between people of the own network (internal communication).<ref>Template:Cite web</ref><ref>Template:Cite web</ref>

Commands and replies

Template:Main IRC has a line-based structure with the client sending single-line messages to the server,<ref>Template:Cite IETF</ref> receiving replies to those messages<ref>Template:Cite IETF</ref> and receiving copies of some messages sent by other clients. In most clients, users can enter commands by prefixing them with a '/'. Depending on the command, these may either be handled entirely by the client, or (generally for commands the client does not recognize) passed directly to the server, possibly with some modification.Template:Citation needed

Due to the nature of the protocol, automated systems cannot always correctly pair a sent command with its reply with full reliability and are subject to guessing.<ref>Template:Cite web</ref>

Channels

The basic means of communicating to a group of users in an established IRC session is through a channel.<ref name="rfc 1459 3.2.2 to a group (channel)">Template:Cite IETF</ref> Channels on a network can be displayed using the IRC command LIST,<ref>Template:Cite IETF</ref> which lists all currently available channels that do not have the modes +s or +p set, on that particular network.

Users can join a channel using the JOIN command,<ref name="rfc 1459 4.2.1 join message">Template:Cite IETF</ref> in most clients available as /join #channelname. Messages sent to the joined channels are then relayed to all other users.<ref name="rfc 1459 3.2.2 to a group (channel)" />

Channels that are available across an entire IRC network are prefixed with a '#', while those local to a server use '&'.<ref>Template:Cite IETF</ref> Other less common channel types include '+' channels—'modeless' channels without operators —<ref>Template:Cite IETF</ref> and '!' channels, a form of timestamped channel on normally non-timestamped networks.<ref>Template:Cite IETF</ref>

Modes

Users and channels may have modes that are represented by single case-sensitive letters<ref>Template:Cite IETF</ref> and are set using the MODE command.<ref>Template:Cite IETF</ref> User modes and channel modes are separate and can use the same letter to mean different things (e.g. usermode "i" is invisible mode whilst channelmode "i" is invite only.<ref>Template:Cite IETF</ref>) Modes are usually set and unset using the mode command that takes a target (user or channel), a set of modes to set (+) or unset (-) and any parameters the modes need.

Some but not all channel modes take parameters and some channel modes apply to a user on a channel or add or remove a mask (e.g. a ban mask) from a list associated with the channel rather than applying to the channel as a whole.<ref>Template:Cite IETF</ref> Modes that apply to users on a channel have an associated symbol that is used to represent the mode in names replies<ref name="rfc 1459 p.51 rpl_namreply">Template:Cite IETF</ref> (sent to clients on first joining a channel<ref name="rfc 1459 4.2.1 join message" /> and use of the names command) and in many clients also used to represent it in the client's displayed list of users in a channel or to display an own indicator for a user's modes.

In order to correctly parse incoming mode messages and track channel state the client must know which mode is of which type and for the modes that apply to a user on a channel which symbol goes with which letter. In early implementations of IRC this had to be hard-coded in the client but there is now a de facto standard extension to the protocol called ISUPPORT that sends this information to the client at connect time using numeric 005.<ref>Template:Cite web</ref><ref>Template:Cite IETF</ref>

There is a small design fault in IRC regarding modes that apply to users on channels: the names message used to establish initial channel state can only send one such mode per user on the channel,<ref name="rfc 1459 p.51 rpl_namreply" /> but multiple such modes can be set on a single user. For example, if a user holds both operator status (+o) and voice status (+v) on a channel, a new client will be unable to know the less precedented mode (voice). Workarounds for this are possible on both the client and server side but none is widely implemented.

Standard (RFC 1459) modes

Many IRCd programmers have added extra modes or modified the behavior of modes in the above list<ref>Template:Cite web</ref><ref>Template:Cite web</ref><ref>Template:Cite web</ref><ref>Template:Cite web</ref> so it is strongly advisable to check the documentation of the IRC network or IRCd (though note that the network may have patched the IRCd) for more detailed information on what the modes do on a particular server or network.

Channel Operators

A Channel Operator is a client on an IRC channel that manages the channel. IRC Channel Operators can be easily seen by a symbol "@", or a Latin letter "+o"/"o". On most networks, an operator can:

• Kick a user
• Ban a user
• Give another user IRC Channel Operator Status or IRC Channel Voice Status.
• Change the IRC Channel topic.
• Change the IRC Channel Mode locks.

IRC Operators

Template:Main There are also users who maintain elevated rights on their local server, or the entire network; these are called IRC operators,<ref name="rfc 1459 1.2.1 operators">Template:Cite IETF</ref> sometimes shortened to IRCops or Opers (not to be confused with channel operators). As the implementation of the IRCd varies, so do the privileges of the IRC operator on the given IRCd. RFC 1459<ref name="rfc 1459 1.2.1 operators" /> claims that IRC operators are "a necessary evil" to keep clean state of the network, and as such they need to be able to disconnect and reconnect servers. Additionally, to prevent malicious users or even harmful automated programs from entering IRC, IRC operators are usually allowed to disconnect clients and completely ban IPs or complete subnets. Networks that carry services (Nickserv et al.) usually allow their IRC operators also to handle basic "Ownership" matters. Further privileged rights may include overriding channel bans (being able to join channels they would not be allowed to join, if they were not opered), being able to op themselves on channels where they would not be able without being opered, being auto-opped on channels always and so forth.

Hostmasks

A hostmask is a unique identifier of an IRC client connected to an IRC server.<ref name="thiedeke-2003">Template:Cite book</ref><ref name="rogers-2005">Template:Cite book</ref> IRC servers, services, and other clients including bots can use it to identify a specific IRC session.

The format of a hostmask is nick!user@host. The hostmask looks similar to, but should not be confused with an e-mail address.

The nick part is the nickname chosen by the user and may be changed while connected. The user part is the username reported by ident on the client.<ref name="petersen-2002">Template:Cite book</ref> If ident is not available on the client, the username specified when the client connected is used after being prefixed with a tilde.<ref name="freenode faq">Template:Cite web</ref>

The host part is the hostname the client is connecting from. If the IP address of the client cannot be resolved to a valid hostname by the server, it is used instead of the hostname.

Because of the privacy implications of exposing the IP address or hostname of a client, some IRC daemons also provide privacy features, such as InspIRCD or UnrealIRCD's "+x" mode. This hashes a client IP address or masks part of a client's hostname, making it unreadable to users other than IRCops. Users may also have the option of requesting a "virtual host" (or "vhost"), to be displayed in the hostmask to allow further anonymity. Some IRC networks such as Freenode use these as "cloaks" to indicate that a user is affiliated with a group or project.<ref>Template:Cite web</ref>

Challenges

Issues in the original design of IRC were the amount of shared state data<ref>Template:Cite IETF</ref><ref>Template:Cite IETF</ref> being a limitation on its scalability,<ref>Template:Harvnb 1.2.1 Growth</ref> the absence of unique user identifications leading to the nickname collision problem,<ref>Template:Cite IETF</ref> lack of protection from netsplits by means of cyclic routing,<ref>Template:Cite IETF</ref><ref>Template:Harvnb 1.2.2 Network failures</ref> the trade-off in scalability for the sake of real-time user presence information,<ref>Template:Cite IETF</ref> protocol weaknesses providing a platform for *****,<ref>Template:Harvnb 1.2.3 Sociological and security aspects</ref> no transparent and optimizable message passing,<ref>Template:Cite IETF</ref> and no encryption.<ref>Template:Cite IETF</ref> Some of these issues have been addressed in Modern IRC.

Attacks

Because IRC connections are usually unencrypted and typically span long time periods, they are an attractive target for Dos/DDoS attackers and hackers. Because of this, careful security policy is necessary to ensure that an IRC network is not susceptible to an attack such as a takeover war. IRC networks may also K-line or G-line users or networks that have a harming effect.

A small number of IRC servers support SSL/TLS connections for security purposes. This helps stop the use of packet sniffer programs to obtain the passwords of IRC users, but has little use beyond this scope due to the public nature of IRC channels. SSL connections require both client and server support (that may require the user to install SSL binaries and IRC client specific patches or modules on their computers). Some networks also use SSL for server to server connections, and provide a special channel flag (such as +S) to only allow SSL-connected users on the channel, while disallowing operator identification in clear text, to better utilize the advantages that SSL provides.<ref>Template:Cite web</ref><ref>Template:Cite web</ref>

IRC served as an early laboratory for many kinds of Internet attacks, such as using fake ICMP unreachable messages to break T*****-based IRC connections (nuking) to annoy users or facilitate takeovers.

***** prevention

One of the most contentious technical issues surrounding IRC implementations, which survives to this day, is the merit of "Nick/Channel Delay" vs. "Timestamp" protocols. Both methods exist to solve the problem of denial-of-service attacks, but take very different approaches. The problem with the original IRC protocol as implemented was that when two servers split and rejoined, the two sides of the network would simply merge their channels. If a user could join on a "split" server, where a channel that existed on the other side of the network was empty, and gain operator status, they would become a channel operator of the "combined" channel after the netsplit ended; if a user took a nickname that existed on the other side of the network, the server would kill both users when rejoining (i.e., 'nick-collision'). This was often *****d to "mass-kill" all users on a channel, thus creating "opless" channels where no operators were present to deal with *****. Apart from causing problems within IRC, this encouraged people to conduct denial of service attacks against IRC servers in order to cause netsplits, which they would then *****.

Nick/channel delay

The nick/channel delay (abbreviated ND/CD) solution to this problem was very simple. After a user signed off and the nickname became available, or a channel ceased to exist because all its users left (as often happens during a netsplit), the server would not allow any user to use that nickname or join that channel, until a certain period of time (the delay) had passed. The idea behind this was that even if a netsplit occurred, it was useless to an *****r because they could not take the nickname or gain operator status on a channel, and thus no collision of a nickname or 'merging' of a channel could occur. To some extent, this inconvenienced legitimate users, who might be forced to briefly use a different name (appending an underscore was popular) after rejoining.

Timestamping

The alternative, the timestamp or TS protocol, took a different approach. Every nickname and channel on the network was assigned a timestampTemplate:Spaced ndashthe date and time when it was created. When a netsplit occurred, two users on each side were free to use the same nickname or channel, but when the two sides were joined, only one could survive. In the case of nicknames, the newer user, according to their TS, was killed; when a channel collided, the members (users on the channel) were merged, but the channel operators on the "losing" side of the split lost their channel operator status. TS is a much more complicated protocol than ND/CD, both in design and implementation, and despite having gone through several revisions, some implementations still have problems with "desyncs" (where two servers on the same network disagree about the current state of the network), and allowing too much leniency in what was allowed by the 'losing' side. Under the original TS protocols, for example, there was no protection against users setting bans or other modes in the losing channel that would then be merged when the split rejoined, even though the users who had set those modes lost their channel operator status. Some modern TS-based IRC servers have also incorporated some form of ND and/or CD in addition to timestamping in an attempt to further curb *****. Most networks today use the timestamping approach. The timestamp versus ND/CD disagreements caused several servers to split away from EFnet and form the newer IRCnet. After the split, EFnet moved to a TS protocol, while IRCnet used ND/CD.

SAVE

In recent versions of the IRCnet ircd, as well as ircds using the TS6 protocol (including Charybdis and InspIRCd), ND has been extended/replaced by a mechanism called SAVE. This mechanism assigns every client a unique UID upon connecting to an IRC server. This ID starts with a number, which is forbidden in nicks (although some ircds, namely IRCnet and InspIRCd, allow clients to switch to their own UID as the nickname).

If two clients with the same nickname join from different sides of a netsplit ("nick collision"), the first server to see this collision will force both clients to change their nick to their UID, thus saving both clients from being disconnected. On IRCnet, the nickname will also be locked for some time (ND) to prevent both clients from changing back to the original nickname, thus colliding again.

Networks

There are thousands of running IRC networks in the world. They run various implementations of IRC servers, and are administered by various groups of IRC operators, but the protocol exposed to IRC users is very similar, and all IRC networks can be accessed by the same client software, although there might be slight incompatibilities and limited functionality due to the differing server software implementations.

The largest IRC networks have traditionally been grouped as the "Big Four"<ref name="the book of irc">Template:Cite book</ref><ref name="encyclopedia of new media">Template:Cite book</ref><ref name="the imac book">Template:Cite book</ref><ref name="information technology for management">Template:Cite book</ref>Template:Mdash a designation for networks that top the statistics. The Big Four networks change periodically, but due to the community nature of IRC there are a large number of other networks for users to choose from.

Historically the "Big Four" were:<ref name="the book of irc" /><ref name="encyclopedia of new media" /><ref name="the imac book" />

• EFnet
• IRCnet
• Undernet
• DALnet

IRC reached 6 million simultaneous users in 2001 and 10 million users in 2003.

As of March 2013 the largest IRC networks were:

• freenode – around 85k users at peak hours
• IRCNet – around 55k users at peak hours
• QuakeNet – around 53k users at peak hours
• Undernet – around 43k users at peak hours
• EFnet – around 33k users at peak hours
• rizon – around 20k users at peak hours

Today, entire IRC grouped has around 400k users at peak hours.

Timeline

Template:Simple Horizontal timeline

URI scheme

There are three recognized URI schemes for Internet Relay Chat, irc, irc6, and ircs,<ref>Template:Cite web</ref> that (when supported) allows hyperlinks of various forms, including

irc://<host>[:<port>]/[<channel>[?<channel_keyword>]]

(where items enclosed within brackets ([,]) are optional) to be used to (if necessary) connect to the specified host (or network, if known to the IRC client) and join the specified channel.<ref>Template:Cite IETF</ref> (This can be used within the client itself, or from another application such as a Web browser). irc is the default URI, irc6 specifies a connection to be made using IPv6, and ircs specifies a secure connection.

Per the specification, the usual hash symbol (#) will be prepended to channel names that do not begin with an alphanumeric character—allowing it to be omitted. Some implementations (for example, mIRC) will do so unconditionally resulting in a (usually unintended) extra (for example, ##channel), if included in the URL.

Some implementations allow multiple channels to be specified, separated by commas.Template:Citation needed

Clients

Client software

Template:Details

Client software exists for various operating systems or software packages, as well as web-based or inside games. Many different clients are available for the various operating systems, including Windows, Unix & Linux, Mac OS X and mobile operating systems (such as iOS and Android). On Windows, mIRC is one of the most popular clients.<ref>Template:Cite book</ref>

Some programs which are extensible through plug-ins also serve as platforms for IRC clients. For instance, a client called ERC, written entirely in Emacs Lisp is included in v.22.3 of Emacs. Therefore, any platform that can run Emacs can run ERC.

A number of web browsers have built in IRC clients, such as Opera (version 12.17 and earlier)<ref>Template:Cite web</ref> or the ChatZilla add-on for Mozilla Firefox (included as a built-in component of SeaMonkey). Web-based clients, such as Mibbit and open source KiwiIRC, can run in most browsers.

Games such as "Pokemon Omega"War§ow,<ref>Template:Cite web</ref> Unreal Tournament (up to Unreal Tournament 2004),<ref>Template:Cite web</ref> Uplink,<ref>Template:Cite web</ref> Spring Engine-based games, 0 A.D. and ZDaemon have included IRC.<ref>Template:Cite web</ref>

Ustream's chat interface is IRC with custom authentication<ref>Template:Cite web</ref> as well as Justin.tv's.<ref>Template:Cite web</ref>

Bots

Template:Main

A typical use of bots in IRC is to provide IRC services or a specific functionality within a channel such as to host a chat-based game or provide notifications of external events.

Bouncer

Template:Main A program that runs as a daemon on a server and functions as a persistent proxy is known as a BNC or bouncer. The purpose is to maintain a connection to an IRC server, acting as a relay between the server and client, or simply to act as a proxy.Template:Citation needed Should the client lose network connectivity, the BNC may stay connected and archive all traffic for later delivery, allowing the user to resume his IRC session without disrupting their connection to the server.<ref>Template:Cite web</ref>

Furthermore, as a way of obtaining a bouncer-like effect, an IRC client (typically text-based, for example Irssi) may be run on an always-on server to which the user connects via ssh. This also allows devices that only have ssh functionality, but no actual IRC client installed themselves, to connect to the IRC, and it allows sharing of IRC sessions.<ref>Template:Cite web</ref>

To keep the IRC client from quitting when the ssh connection closes, the client can be run inside a piece of screen-detaching software (e.g. GNU Screen or tmux), thus staying connected to the IRC network(s) constantly and able to log conversation in channels that the user is interested in, etc. Modelled after this setup, in 2004 an IRC client following the client-server model, called Smuxi, has been launched.<ref>Template:Cite web</ref><ref>Template:Cite web</ref>

Search engines

There are numerous search engines available to aid the user in finding what they are looking for on IRC.<ref>Template:Cite book</ref><ref>Template:Cite book</ref> Generally the search engine consists of two parts, a "back-end" (or "spider/crawler") and a front-end "search engine".

The back-end (spider/crawler) is the work horse of the search engine. It is responsible for crawling IRC servers to index the information being sent across them. The information that is indexed usually consists solely of channel text (text that is publicly displayed in public channels). The storage method is usually some sort of relational database, like MySQL or Oracle.Template:Citation needed

The front-end "search engine" is the user interface to the database. It supplies users with a way to search the database of indexed information to retrieve the data they are looking for. These front-end search engines can also be coded in numerous programming languages. The more popular languages for such search engines and indexing spiders are Perl, PHP and C.Template:Citation needed

Most search engines have their own spider that is a single application responsible for crawling IRC and indexing data itself; however, others are "user based" indexers. The latter rely on users to install their "add-on" to their IRC client; the add-on is what sends the database the channel information of whatever channels the user happens to be on.Template:Citation needed

Many users have implemented their own ad hoc search engines using the logging features built into many IRC clients.

Modern IRC

IRC has changed much over its life on the Internet. New server software has added a multitude of new features.

• Services: Network-operated bots to facilitate registration of nicknames and channels, sending messages for offline users and network operator functions.
• Extra modes: While the original IRC system used a set of standard user and channel modes, new servers add many new modes for such features as removing color codes from text, or obscuring a user's hostmask ("cloaking") to protect from denial-of-service attacks.Template:Citation needed
• Proxy detection: Most modern servers support detection of users attempting to connect through an insecure (misconfigured or exploited) proxy server, which can then be denied a connection. An example is the Blitzed Open Proxy Monitor or BOPM. This proxy detection software is used by several networks, although that real time list of proxies is defunct since early 2006.Template:Citation needed
• Additional commands: New commands can be such things as shorthand commands to issue commands to Services, to network operator only commands to manipulate a user's hostmask.Template:Citation needed
• Encryption: For the client-to-server leg of the connection SSL might be used (messages cease to be secure once they are relayed to other users on standard connections, but it makes eavesdropping on or wiretapping an individual's IRC sessions difficult). For client-to-client communication, SDCC (Secure DCC) can be used.Template:Citation needed
• Connection protocol: IRC can be connected to via IPv4, the current standard version of the Internet Protocol, or by IPv6, the next-generation version of the protocol.

There is an effort of standardization and adding new features to the IRC protocol by IRCv3 working group.<ref>Template:Cite web</ref>

Character encoding

IRC still lacks a single globally accepted standard convention for how to transmit characters outside the 7-bit ASCII repertoire. IRC servers normallyTemplate:Clarify transfer messages from a client to another client just as byte sequences, without any interpretation or recoding of characters. The IRC protocol (unlike e.g. MIME or HTTP) lacks mechanisms for announcing and negotiating character encoding options. This has put the responsibility for choosing the appropriate character codec on the client. In practice, IRC channels have largely used the same character encodings that were also used by operating systems (in particular Unix derivatives) in the respective language communities:

• 7-bit era: In the early days of IRC, especially among Scandinavian and Finnish language users, national variants of ISO 646 were the dominant character encodings. These encode non-ASCII characters like Ä Ö Å ä ö å at code positions 0x5B 0x5C 0x5D 0x7B 0x7C 0x7D (US-ASCII: [ \ ] { | }). That is why these codes are always allowed in nicknames. According to RFC 1459, { | } in nicknames should be treated as lowercase equivalents of [ \ ] respectively.<ref name="rfc 1459 2.2 character codes" /> By the late 1990s, the use of 7-bit encodings had disappeared in favour of ISO 8859-1, and such equivalence mappings were dropped from some IRC daemons.

• 8-bit era: Since the early 1990s, 8-bit encodings such as ISO 8859-1 have become commonly used for European languages. Russian users had a choice of KOI8-R, ISO 8859-5Template:Citation needed and *****1251, and since about 2000, modern Russian IRC networks convert between these different commonly used encodings of the Cyrillic script.

• Multi-byte era: For a long time, East Asian IRC channels with ideographic scripts in China, Japan, and Korea have been using multi-byte encodings such as EUC or ISO-2022-JP. With the common migration from ISO 8859 to UTF-8 on Linux and Unix platforms since about 2002, UTF-8 has become an increasingly popular substitute for many of the previously used 8-bit encodings in European channels. Some IRC clients are now capable of reading messages both in ISO 8859-1 or UTF-8 in the same channel, heuristically autodetecting which encoding is used. The shift to UTF-8 began in particular on Finnish-speaking IRC (Merkistö (Finnish)).

Today, the UTF-8 encoding of Unicode/ISO 10646 would be the most likely contender for a single future standard character encoding for all IRC communication, if such standard ever relaxed the 510 bytes message size restriction. UTF-8 is ASCII compatible and covers the superset of all other commonly used coded character set standards.

File sharing

Much like conventional P2P file sharing, users can create file servers that allow them to share files with each other by using customised IRC bots or scripts for their IRC client. Often users will group together to distribute warez via a network of IRC bots.<ref>Template:Cite web</ref>

Technically, IRC provides no file transfer mechanisms itself; file sharing is implemented by IRC clients, typically using the Direct Client-to-Client (DCC) protocol, in which file transfers are negotiated through the exchange of private messages between clients. The vast majority of IRC clients feature support for DCC file transfers, hence the view that file sharing is an integral feature of IRC.<ref>{{cite web