From Wikipedia, the free encyclopedia

IRC services is a common name for a set of features implemented in most modern Internet Relay Chat networks. Services are automated bots with special status which are generally used to provide users with access with certain privileges and protection. They usually implement some sort of login system so that only people on the access control list can obtain these services.

The most popular style of services use a number of fake clients whose names end in "Serv". The four below are nearly always seen in services of this style.

• ChanServ, a channel service bot, is used to protect channel operators and help run the channel. This is convenient for the operators because they do not need to have an operator on the channel all of the time to keep their status.
• NickServ, a nickname service bot, is used to register and protect user nicknames.
• MemoServ, a memo service bot, is used to record and deliver messages to users who are currently offline.
• OperServ is used by IRC Operators. Also known as AdminServ, RootServ, or OpServ (srvx).

Some others are also seen following this naming convention in some services packages including:

• BotServ, a which allows channel operators to assign bots to their channels. these bots are mostly a ChanServ representative in the channel.
• HelpServ, the help service bot, is used to provide help on a variety of IRC topics.
• HostServ, a host service bot, is used to allow general users to register a vhost so that their real IP address on IRC is hidden.
• RootServ, used on specific networks, is utilized by Services Root Administrators to perform Root Administrative functions for the IRC Network and Services Program.
• StatServ, a statistic services bot, is used to perform various statistical analysis on the IRC Network.
• Global, a message agent, is a specific service that is used to send global messages via services. This agent is usually given a global IRC Operator status as to be able to perform the function. This service must be on a U:Lined server so it has the ability to spoof nicknames. This service is often renamed to the name of the network (e.g. EsperNet or Xelium.).
• DevNull, a "message sink"; all messages sent to it are simply ignored. Named after the UNIX /dev/null.

The original NickServ was written by Armin Gruner at the Munich University of Technology in 1990. The original intention was to give out friendly warnings that somebody else already likes to use a specific nickname, since the IRC protocol has no built-in provision to protect electronic identities. NoteServ and MsgServ followed up soon after the introduction of NickServ, and had a similar job of today's MemoServ.

It was considered okay behaviour to simply /ignore NickServ's notices, but an operator called Jupiter decided to /kill NickServ and use the nickname NickServ himself, subsequently collecting all identify passwords from users and being amused by that. This led to a public debate over the usefulness and safety of services, the discontinuation of NickServ on EFnet and EFnet's current Nicknames are not owned policy arose.

In 1995 DALnet invented ChanServ, then re-implemented NickServ and MemoServ. Today EFnet and IRCnet are the last large IRC networks which stick to their policy of living without identity protection. Services are generally considered essential to providing a pleasant chatting experience.

Many variants of services have been implemented over time, so each IRC network speaks a different service dialect, making it close to impossible for client developers to implement unified graphical interfaces to the various registration procedures. Still most of them are inspired by DALnet's and Armin's original works, only QuakeNet sticks out with a completely different approach.

There are several software packages that implement services. Some of the popular ones include srvx, Atheme, Hybserv (developed for use with the Hybrid IRC daemon software), Epona (Now deprecated), Anope, and IRC Services 5 (supporting a wide range of IRC daemons). While some of these packages provide excellent features in the eyes of many users, some network operators decide to write their own services, with the most important reasons being flexibility, customization, and often, mostly on smaller networks, fun also plays an important role. Not all packages implement the above service bots. Also, sometimes the bots have different names, and may or may not implement these functions in the form listed above. Even so, the above form is the most common.

The IRC+ initiative is working on producing a recommendation for services to use common numerics for essential functions, so that clients can have unified and simplified user interfaces for dealing with services for the most essential functions (like, registering your identity on an IRC network).

• IRC operator
• IRC channel operator
• IRC takeover
• IRCd
• Comparison of IRC services

• Anope Services
• Atheme IRC Services
• Auspice Services
• Denora Stats
• Epona Services
• IRC Services homepage
• ModServ IRC Services
• PTlink IRC Services
• QuakeNet Services
• Forcis IRC Services (Old Red-Unida)
• X3 IRC Services
• SurrealServices
• Undernet GNUWorld IRC services
• Ecks IRC Services