Mirc free download Archives

The first IRC server, tolsun.oulu.fi, a Sun-3 server on display near the University of Oulu computer centre. (2001)

Internet Relay Chat (IRC) is an application layer protocol that facilitates communication in the form of text. The chat process works on a client/server networking model. IRC clients are computer programs that users can install on their system or web based applications running either locally in the browser or on a 3rd party server. These clients communicate with chat servers to transfer messages to other clients.^[1] IRC is mainly designed for group communication in discussion forums, called channels,^[2] but also allows one-on-one communication via private messages^[3] as well as chat and data transfer,^[4] including file sharing.^[5]

Client software is available for every major operating system that supports Internet access.^[6] As of April 2011, the top 100 IRC networks served more than half a million users at a time,^[7] with hundreds of thousands of channels^[7] operating on a total of roughly 1,500 servers^[7] out of roughly 3,200 servers worldwide.^[8] IRC usage has been declining steadily since 2003, losing 60% of its users (from 1 million to about 400,000 in 2012) and half of its channels (from half a million in 2003).^[9]

History[edit]

IRC was created by Jarkko Oikarinen in August 1988 to replace a program called MUT (MultiUser Talk) on a BBS called OuluBox at the University of Oulu in Finland, where he was working at the Department of Information Processing Science. Jarkko intended to extend the BBS software he administered, to allow news in the Usenet style, real time discussions and similar BBS features. The first part he implemented was the chat part, which he did with borrowed parts written by his friends Jyrki Kuoppala and Jukka Pihl. The first IRC network was running on a single server named tolsun.oulu.fi.^[10] Oikarinen found inspiration in a chat system known as Bitnet Relay, which operated on the BITNET.^[11]

Jyrki Kuoppala pushed Oikarinen to ask Oulu University to free the IRC code so that it also could be run outside of Oulu, and after they finally got it released, Jyrki Kuoppala immediately installed another server. This was the first "irc network". Oikarinen got some friends at the Helsinki University and Tampere University to start running IRC servers when his number of users increased and other universities soon followed. At this time Oikarinen realized that the rest of the BBS features probably wouldn't fit in his program.^[10]

Oikarinen got in touch with people at the University of Denver and Oregon State University. They had their own IRC network running and wanted to connect to the Finnish network. They had obtained the program from one of Oikarinen's friends, Vijay Subramaniam—the first non-Finnish person to use IRC. IRC then grew larger and got used on the entire Finnish national network—Funet—and then connected to Nordunet, the Scandinavian branch of the Internet. In November 1988, IRC had spread across the Internet and in the middle of 1989, there were some 40 servers worldwide.^[10]

EFnet[edit]

In August 1990, the first major disagreement took place in the IRC world. The "A-net" (Anarchy net) included a server named eris.berkeley.edu. It was all open, required no passwords and had no limit on the number of connects. As Greg "wumpus" Lindahl explains: "it had a wildcard server line, so people were hooking up servers and nick-colliding everyone". The "Eris Free Network", EFnet, made the eris machine the first to be Q-lined (Q for quarantine) from IRC. In wumpus' words again: "Eris refused to remove that line, so I formed EFnet. It wasn't much of a fight; I got all the hubs to join, and almost everyone else got carried along." A-net was formed with the eris servers, while EFnet was formed with the non-eris servers. History showed most servers and users went with EFnet. Once ANet disbanded, the name EFnet became meaningless, and once again it was the one and only IRC network.^[10]

It is around that time that IRC was used to report on the 1991 Soviet coup d'état attempt throughout a media blackout.^[12] It was previously used in a similar fashion during the Gulf War.^[13]Chat logs of these and other events are kept in the ibiblio archive.^[14]

Undernet fork[edit]

Another fork effort, the first that really made a big and lasting difference, was initiated by 'Wildthang' in the U.S. October 1992 (it forked off the EFnet ircd version 2.8.10). It was meant to be just a test network to develop bots on but it quickly grew to a network "for friends and their friends". In Europe and Canada a separate new network was being worked on and in December the French servers connected to the Canadian ones, and by the end of the month, the French and Canadian network was connected to the US one, forming the network that later came to be called "The Undernet".^[10]

The "undernetters" wanted to take ircd further in an attempt to make it less bandwidth consumptive and to try to sort out the channel chaos (netsplits and takeovers) that EFnet started to suffer from. For the latter purpose, the Undernet implemented timestamps, new routing and offered the CService—a program that allowed users to register channels and then attempted to protect them from troublemakers. The very first server list presented, from 15 February 1993, includes servers from USA, Canada, France, Croatia and Japan. On 15 August, the new user count record was set to 57 users.^[10]

In May 1993, RFC 1459^[1] was published and details a simple protocol for client/server operation, channels, one-to-one and one-to-many conversations.^[10] It is notable that a significant number of extensions like CTCP, colors and formats are not included in the protocol specifications, nor is character encoding,^[15] which led various implementations of servers and clients to diverge. In fact, software implementation varied significantly from one network to the other, each network implementing their own policies and standards in their own code bases.

DALnet fork[edit]

During the summer of 1994, the Undernet was itself forked. The new network was called DALnet (named after its founder: dalvenjah), formed for better user service and more user and channel protections. One of the more significant changes in DALnet was use of longer nicknames (the original ircd limit being 9 letters). DALnet ircd modifications were made by Alexei "Lefler" Kosut. DALnet was thus based on the Undernet ircd server, although the DALnet pioneers were EFnet abandoners. According to James Ng, the initial DALnet people were "ops in #StarTrek sick from the constant splits/lags/takeovers/etc".^[10]

DALnet quickly offered global WallOps (IRCop messages that can be seen by users who are +w (/mode NickName +w)), longer nicknames, Q:Lined nicknames (nicknames that cannot be used i.e. ChanServ, IRCop, NickServ, etc.), global K:Lines (ban of one person or an entire domain from a server or the entire network), IRCop only communications: GlobOps, +H mode showing that an IRCop is a "helpop" etc. Much of DALnet's new functions were written in early 1995 by Brian "Morpher" Smith and allow users to own nicknames, control channels, send memos, and more.^[10]

IRCnet fork[edit]

In July 1996, after months of flame wars and discussions on the mailing list, there was yet another split due to disagreement in how the development of the ircd should evolve. Most notably, the "european" (most of those servers were in Europe) side that later named itself IRCnet argued for nick and channel delays where the EFnet side argued for timestamps.^[10] There were also disagreements about policies: the European side had started to establish a set of rules directing what IRCops could and could not do, a point of view opposed by the US side.^[16]

Most (not all) of the IRCnet servers were in Europe, while most of the EFnet servers were in the US. This event is also known as "The Great Split" in many IRC societies. EFnet has since (as of August 1998) grown and passed the number of users it had then. In the (northern) autumn of the year 2000, EFnet had some 50,000 users and IRCnet 70,000.^[10]

Modern IRC[edit]

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 features such as removing color codes from text,^[17] or obscuring a user's hostmask ("cloaking") to protect from denial-of-service attacks.^[18]
• 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. This proxy detection software is used by several networks, although that real time list of proxies is defunct since early 2006.^[19]
• 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.^{[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.^{[citation needed]}
• Connection protocol: IRC can be connected to via IPv4, the old version of the Internet Protocol, or by IPv6, the current standard of the protocol.

As of 2016^[update], a new standardization effort is under way under a working group called IRCv3, which focuses on more advanced client features like instant notifications, better history support and improved security.^[20] As of 2019^[update], no major IRC networks have fully adopted the proposed standard.^[21]

After its golden era during the 1990s and early 2000s (240,000 users on QuakeNet in 2004), IRC has seen a significant decline, losing around 60% of users between 2003 and 2012, with users moving to newer social media platforms like Facebook or Twitter,^[9] but also to open platforms like XMPP which was developed in 1999. Certain networks like Freenode have not followed the overall trend and have more than quadrupled in size during the same period.^[9] As of 2016, Freenode is the largest IRC network with around 90,000 users.^[22]

The largest IRC networks have traditionally been grouped as the "Big Four"^{[23][24][25][26]}—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:^[23][24][25]

IRC reached 6 million simultaneous users in 2001 and 10 million users in 2003, dropping to 371k in 2018.^{[citation needed]}

As of October 2018^[update], the largest IRC networks are:

• freenode – around 90k users at peak hours
• IRCnet – around 30k users at peak hours
• EFnet – around 18k users at peak hours
• Undernet – around 17k users at peak hours
• QuakeNet – around 15k users at peak hours
• Rizon – around 14k users at peak hours
• OFTC – around 13k users at peak hours
• DALnet – around 8k users at peak hours

Today, the top 100 IRC networks have around 370k users connected at peak hours.^[27]

Timeline[edit]

Technical information[edit]

A screenshot of HexChat, an IRC client for GTK environments.

Xaric, a text-based IRC client, in use on Mac OS X. Shown are two IRC channels and a private conversation with the software author.

IRC is an open protocol that uses TCP^[1] and, optionally, TLS. An IRC server can connect to other IRC servers to expand the IRC network.^[28] Users access IRC networks by connecting a client to a server.^[29] 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 nick is required before being connected.^[30]

IRC was originally a plain text protocol^[1] (although later extended), which on request was assigned port 194/TCP by IANA.^[31] However, the de facto standard has always been to run IRC on 6667/TCP^[32] and nearby port numbers (for example TCP ports 6660–6669, 7000)^[33] 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.^[15] 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.^{[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.^{[citation needed]}

Microsoft made an extension for IRC in 1998 via the proprietary IRCX.^[34] They later stopped distributing software supporting IRCX, instead developing the proprietary MSNP.

The standard structure of a network of IRC servers is a tree.^[35] Messages are routed along only necessary branches of the tree but network state is sent to every server^[36] and there is generally a high degree of implicit trust between servers. However, this architecture has a number of problems. A misbehaving or malicious server can cause major damage to the network^[37] 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^[38] 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.^[39] 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 within the local area network (internal communication).^[40][41]

Commands and replies[edit]

IRC has a line-based structure. Clients send single-line messages to the server,^[42] receive replies to those messages^[43] and receive 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.^{[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.^[44]

Channels[edit]

The basic means of communicating to a group of users in an established IRC session is through a channel.^[45] Channels on a network can be displayed using the IRC command LIST,^[46] 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,^[47] in most clients available as /join #channelname. Messages sent to the joined channels are then relayed to all other users.^[45]

Channels that are available across an entire IRC network are prefixed with a '#', while those local to a server use '&'.^[48] Other less common channel types include '+' channels—'modeless' channels without operators^[49]—and '!' channels, a form of timestamped channel on normally non-timestamped networks.^[50]

Modes[edit]

Users and channels may have modes that are represented by single case-sensitive letters^[51] and are set using the MODE command.^[52] User modes and channel modes are separate and can use the same letter to mean different things (e.g. user mode "i" is invisible mode while channel mode "i" is invite only.^[53]) 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 channel modes take parameters and other 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.^[54] Modes that apply to users on a channel have an associated symbol that is used to represent the mode in names replies^[55] (sent to clients on first joining a channel^[47] 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.^[56][57]

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,^[55] 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 see the mode with less priority (i.e. voice). Workarounds for this are possible on both the client and server side but none are widely implemented.

Standard (RFC 1459) modes[edit]

Many daemons and networks have added extra modes or modified the behavior of modes in the above list.^{[59][60][61][62]}

Channel Operators[edit]

A Channel Operator is a client on an IRC channel that manages the channel. IRC Channel Operators can be easily seen by the a symbol or icon next to their name (varies by client implementation, commonly a "@" symbol prefix, a green circle, 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 while channel mode +t is set.
• Change the IRC Channel Mode locks.

IRC operators[edit]

There are also users who maintain elevated rights on their local server, or the entire network; these are called IRC operators,^[63] 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^[63] claims that IRC operators are "a necessary evil" to keep a 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 IP addresses 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[edit]

A hostmask is a unique identifier of an IRC client connected to an IRC server.^[64][65] IRC servers, services, and other clients, including bots, can use it to identify a specific IRC session.

The format of a hostmask is . 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.^[66] If ident is not available on the client, the username specified when the client connected is used after being prefixed with a tilde.^[67]

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.^[68]

URI scheme[edit]

There are three recognized uniform resource identifier (URI) schemes for Internet Relay Chat: , , and .^[69] When supported, they allow hyperlinks of various forms, including

(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.^[70] (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 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.^[71]

Challenges[edit]

Issues in the original design of IRC were the amount of shared state data^[72][73] being a limitation on its scalability,^[74] the absence of unique user identifications leading to the nickname collision problem,^[75] lack of protection from netsplits by means of cyclic routing,^[76][77] the trade-off in scalability for the sake of real-time user presence information,^[78] protocol weaknesses providing a platform for abuse,^[79] no transparent and optimizable message passing,^[80] and no encryption.^[81] Some of these issues have been addressed in Modern IRC.

Attacks[edit]

Because IRC connections may be 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 servers that have a harming effect.

Some 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 ) to only allow SSL-connected users on the channel, while disallowing operator identification in clear text, to better utilize the advantages that SSL provides.^[82][83]

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

Abuse prevention[edit]

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 abused to "mass-kill" all users on a channel, thus creating "opless" channels where no operators were present to deal with abuse. 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 abuse.

The nick delay and channel delay strategies aim to prevent abuse by delaying reconnections and renames. After a user signs off and the nickname becomes available, or a channel ceases to exist because all its users parted (as often happens during a netsplit), the server will not allow any user to use that nickname or join that channel, until a certain period of time (the delay) has passed. The idea behind this is that even if a netsplit occurs, it is useless to an abuser because they cannot take the nickname or gain operator status on a channel, and thus no collision of a nickname or 'merging' of a channel can occur. To some extent, this inconveniences legitimate users, who might be forced to briefly use a different name after rejoining (appending an underscore is popular).

The timestamp protocol is an alternative to nick/channel delays which resolves collisions using timestamped priority. Every nickname and channel on the network is assigned a timestamp – the date and time when it was created. When a netsplit occurs, two users on each side are free to use the same nickname or channel, but when the two sides are joined, only one can survive. In the case of nicknames, the newer user, according to their TS, is killed; when a channel collides, the members (users on the channel) are merged, but the channel operators on the "losing" side of the split lose 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 abuse.

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.

In recent versions of the IRCnet ircd, as well as ircds using the TS6 protocol (including Charybdis), ND has been extended/replaced by a mechanism called SAVE. This mechanism assigns every client a 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.

Clients[edit]

Client software[edit]

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 and Linux, Mac OS X and mobile operating systems (such as iOS and Android). On Windows, mIRC is one of the most popular clients.^[84]

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.18 and earlier)^[85] and the ChatZilla add-on for Mozilla Firefox (for Firefox 56 and earlier; 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 War§ow,^[86]Unreal Tournament (up to Unreal Tournament 2004),^[87]Uplink,^[88]Spring Engine-based games, 0 A.D. and ZDaemon have included IRC.^[89]

Ustream's chat interface is IRC with custom authentication^[90] as well as Twitch's (formerly Justin.tv).^[91][92]

Bots[edit]

A typical use of bots in IRC is to provide IRC services or specific functionality within a channel such as to host a chat-based game or provide notifications of external events. However, some IRC bots are used to launch malicious attacks such as denial of service, spamming, or exploitation.^[93]

Bouncer[edit]

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.^{[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 their IRC session without disrupting their connection to the server.^[94]

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.^[95]

To keep the IRC client from quitting when the ssh connection closes, the client can be run inside a terminal multiplexer such as 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, or to maintain a channel's presence on the network. Modelled after this setup, in 2004 an IRC client following the client-server model, called Smuxi, was launched.^[96][97]

Search engines[edit]

There are numerous search engines available to aid the user in finding what they are looking for on IRC.^[98][99] Generally the search engine consists of two parts, a "back-end" (or "spider/crawler") and a front-end "search engine".

The back-end (spider/webcrawler) 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.^{[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.

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.^{[citation needed]}

Many users have implemented their own ad hoc search engines using the logging features built into many IRC clients. These search engines are usually implemented as bots and dedicated to a particular channel or group of associated channels.

Character encoding[edit]

IRC still lacks a single globally accepted standard convention for how to transmit characters outside the 7-bit ASCII repertoire. IRC servers normally^{[clarification needed]} 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.^[15] 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-5^{[citation needed]} and CP1251, and since about 2000, modern Russian IRC networks convert between these different commonly used encodings of the Cyrillic script.
• Multi-byte era:

Please follow the netiquette when posting on FFmpeg mailing lists, especially avoid top-posting and thread hijacking (that is, replying to a thread and changing the subject line to something completely unrelated that was not being discussed within the original thread) and please read the Code of conduct.

Configuring your mail client to break lines after 70 or so characters is a plus. If you attach files, avoid compressing small files, uncompressed is preferred. Also please try to avoid posting mails with overly long signatures or nonsense corporate disclaimers that claim the content of your mails is confidential.

Attached patches should not have application/octet-stream as mime-type, but text/plain or even better text/x-diff or text/x-patch.
If you send us a patch, please make it some form of unified diff. We prefer patches made using from the root of your FFmpeg checkout or sent with as shown in Using git to develop FFmpeg. For additional information and guidelines refer to the FFmpeg Developer Documentation.

1. Fixed perform on connect sorting bug.
2. Fixed numeric 330 bug.
3. Fixed menubar and toolbar flickering when switching windows.
4. Fixed ! on INPUT processing bug.
5. Fixed $read/etc. freeze bug when used with invalid filenames.
6. /window -o no longer activates a window.
7. Fixed switchbar multi-line display bug.
8. Fixed /window -h and Alt+F1 bug.
9. Fixed up/down keys not working in certain windows.
10. Fixed dcc ignore bug.
11. Fixed /timer bug, was triggering too early in some situations.
12. Fixed /window -h displaying minimized icon for a window when switchbar was turned off.
13. Shift+DoubleClick on a line in the Channels List window now joins the channel minimized.
14. Fixed bug in highlight feature.
15. Fixed remote toolbar button right-click menu bug.
16. Nick color list now allows you to add an item with no color selected.
17. Fixed background picture display bug when a window is resized.
18. Fixed listbox selection/cursor bug which affected listboxes in dialog windows.
19. Fixed /load command triggering multiple on load events.
20. mIRC now supports the IRCX events KNOCK, WHISPER, EVENT, PROP on any server that sends them, not just an IRCX server.
21. Added on LOGON event, triggers before and after mIRC sends the standard PASS, NICK, and USER messages to the server. on ^*:LOGON:*:echo Logging on to $network $server on *:LOGON:*:echo Logged on to $network $server. If you /halt the event, mIRC will not send the standard logon messages, allowing to send your own messages.
22. mIRC will again try to rejoin a channel even if it was +i or +k, since there are situations on some networks where the rejoin will work.
23. Fixed /set -u0 bug not unsetting variables in some situations.
24. Fixed enter key bug in empty channel nicklist.
25. Changed $ticks back to old method due to bug in Windows high performance timer which returned incorrect values.
26. Now handles numeric 378 in whois replies.
27. Fixed fileserver window not being closed on a time-out.
28. Fixed window active titlebar display bug when certain Window tile/cascade options were enabled.
29. Fixed /did -k not triggering events again if halted once.
30. Fixed debug window not showing entire raw line if it contained a $cr or $lf.
31. Fixed on START bug caused by loading custom dialogs during the event.
32. Fixed memory bug in script parser.
33. Fixed /load /unload not treating short/long filenames as the same file.
34. Notify list titlebar now shows total number of notify users online across all server connections.
35. Added $window().sbtext and .sbcolor properties.
36. Can now mark/copy text backwards or forwards.
37. Fixed $base() bug not handling negative numbers correctly.
38. Added $ialchan().pnick property.
39. Added $serverip identifier, returns server ip address.
40. Added /editbox -f switch, sets editbox focus.
41. Added $nick().idle property, returns idle time in seconds for nick on a channel, ie. the time since the user last sent a message to the channel.
42. Fixed on CONNECTFAIL bug.
43. Fixed $mklogfn() bug.
44. Fixed proxy authentication bug.
45. Added idle time option to nick color list dialog. Also added $cnick().idle property.
46. Fixed $asctime() bug.
47. Fixed /ignore -u bug.
48. Added exception masks option to firewall dialog.
49. Fixed dcc server ignore bug.
50. Can now specify %variables in a dialog item definition, and the %variable will be set with the contents of that item when the dialog is closed, eg.edit "", 2, 10 10 100 20, autohs %test
51. Online timer now handles multi-server connections.
52. Changed $input(prompt,N,window,title,text), where N is: