Jump to content

IRC services: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
Added info on Atheme and added a new services package.
 
(33 intermediate revisions by 26 users not shown)
Line 1: Line 1:
{{short description|Type of service}}
⚫
{{Redirect|AKill|the creator of [[Akbot]], whose online pseudonym is AKILL|Owen Walker}}
{{Refimprove|date=May 2009}}
{{Refimprove|date=May 2009}}


'''Internet Relay Chat services''' (usually called '''IRC services''') is a name for a set of features implemented on many modern [[Internet Relay Chat]] networks. Services are automated [[Internet bot|bot]]s 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.
'''IRC services''' is a set of features implemented on many [[Internet Relay Chat]] networks. Services are automated [[Internet bot|bot]]s 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.


== Components ==
== Components ==
Line 18: Line 18:
* ''HostServ'', a host service bot, is used to allow general users to register a [[vhost (IRC)|vhost]] so that their real [[IP address]] on IRC is hidden.
* ''HostServ'', a host service bot, is used to allow general users to register a [[vhost (IRC)|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.
* ''RootServ'', used on specific networks, is utilized by Services Root Administrators to perform Root Administrative functions for the IRC Network and Services Program.
* ''SpamServ'', used to protect channels against spam.<ref>{{cite web|url=https://gamesurge.net/cms/SpamServ |title=>> SpamServ |publisher=GameSurge |date=2008-12-18 |accessdate=2013-07-11}}</ref>
* ''SpamServ'', used to protect channels against spam.<ref>{{cite web|url=https://gamesurge.net/cms/SpamServ |title=>> SpamServ |publisher=GameSurge |date=2008-12-18 |access-date=2013-07-11}}</ref>
* ''StatServ'', a statistic services bot, is used to perform various statistical analysis on the IRC Network.
* ''StatServ'', a statistic services bot, is used to perform various statistical analysis on the IRC Network.


Other commonly used services bots:
Other commonly used services bots:


* ''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-line]]d{{clarify|date=February 2012}} server so it has the ability to spoof nicknames. This service is often renamed to the name of the network (e.g. ''[[DalNet]]'' or ''[[Xevium]]''.).
* ''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-line (IRC)|U-lined]]{{clarify|date=February 2012}} server so it has the ability to spoof nicknames. This service is often renamed to the name of the network (e.g. ''[[DalNet]]'' or ''[[Xevium]]''.).


== History ==
== History ==
The original '''NickServ''' was written by [[Armin Gruner]] at the [[Munich University of Technology]] in 1990.<ref>{{cite journal
The original '''NickServ''' was written by [[Armin Gruner]] at the [[Technical University of Munich]] in 1990.<ref>{{cite journal
| last = Bechar-Israeli
| last = Bechar-Israeli
| first = Haya
| first = Haya
⚫
|date=September 1995
| authorlink =
⚫
|date=November 1995
| title = From &lt;Bonehead&gt; to &lt;cLoNehEAd&gt;: Nicknames, play, and identity on Internet Relay Chat
| title = From &lt;Bonehead&gt; to &lt;cLoNehEAd&gt;: Nicknames, play, and identity on Internet Relay Chat
| journal = [[Journal of Computer-Mediated Communication]]
| journal = [[Journal of Computer-Mediated Communication]]
Line 37: Line 36:
| publisher = [[Indiana University School of Library and Information Science]]
| publisher = [[Indiana University School of Library and Information Science]]
| location = [[Bloomington, Indiana]]
| location = [[Bloomington, Indiana]]
| doi = 10.1111/j.1083-6101.1995.tb00325.x
| url = http://jcmc.indiana.edu/vol1/issue2/bechar.html
| url = https://onlinelibrary.wiley.com/doi/10.1111/j.1083-6101.1995.tb00325.x
| accessdate = 2009-07-02
| access-date = 2020-03-29
}}</ref> 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.
}}</ref> 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 to today's ''MemoServ''.
''NoteServ'' and ''MsgServ'' followed up soon after the introduction of NickServ, and had a similar job to today's ''MemoServ''.


It was considered acceptable behavior simply to ''/ignore'' NickServ's notices, but an operator decided to ''/kill NickServ'' and use the nickname ''NickServ'' himself, subsequently collecting all ''identify'' passwords from users and being amused by that.
It was considered acceptable behavior simply to ''/ignore'' NickServ's notices, but an operator decided to ''/kill NickServ'' and use the nickname ''NickServ'' himself, subsequently collecting all ''identify'' passwords from users and being amused by that.{{Citation needed|date=January 2020}}
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.
This led to a public debate over the usefulness and safety of services and 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''.
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. Some debate still remains over the value and benefits of Services on IRC, although they are generally considered essential to providing a pleasant chatting experience. This is proven in the fact that most service-less networks have died out.{{Citation needed|date=January 2010}}
Today, EFnet and [[IRCnet]] are the last large IRC networks which stick to their policy of living without identity protection.{{Citation needed|date=January 2020}} Some debate still remains over the value and benefits of Services on IRC, although they are generally considered essential to providing a pleasant chatting experience.{{By whom|date=January 2020}} This is proven in the fact that most service-less networks have died out.{{Citation needed|date=January 2010}}


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.
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 [[Undernet]] and [[QuakeNet]] stick out with a completely different approach.
Still, most of them are inspired by DALnet's and Armin's original works, only [[Undernet]] and [[QuakeNet]] stick out with a completely different approach.


== ChanServ {{anchor|ChanServ}} ==
== ChanServ {{anchor|ChanServ}} ==
'''ChanServ''', on many [[IRC]] networks, is an IRC service which maintains [[Internet Relay Chat#Channels and modes|channel]] registration and access information.<ref>[http://www.technerd.net/chanserv.html ChanServ Help] by TechNerd. Accessed October 6, 2008.</ref> If a channel is registered with ChanServ, its owners (and those they have designated) can use ChanServ to obtain control over the channel, gaining [[IRC channel operator|channel operator]] privileges. Most channel service bots also allow other sorts of channel management options, such as topic locks (in addition to +t), mode locks, and providing users automatically with operator status, half-operator status, voice, or other access, as designated by the channel owners. They may also provide some form of automated ban-list management.<ref>[http://www.wyldryde.org/a/000911.php What is ChanServ?] by WyldRyde. Accessed October 6, 2008.</ref>
'''ChanServ''', on many [[IRC]] networks, is an IRC service which maintains [[Internet Relay Chat#Channels and modes|channel]] registration and access information.<ref>[http://www.technerd.net/chanserv.html ChanServ Help] by TechNerd. Accessed October 6, 2008.</ref> If a channel is registered with ChanServ, its owners (and those they have designated) can use ChanServ to obtain control over the channel, gaining [[IRC channel operator|channel operator]] privileges. Most channel service bots also allow other sorts of channel management options, such as topic locks (in addition to +t), mode locks, and providing users automatically with operator status, half-operator status, voice, or other access, as designated by the channel owners. They may also provide some form of automated ban-list management.<ref>[http://www.wyldryde.org/a/000911.php What is ChanServ?] {{webarchive|url=https://web.archive.org/web/20090626145356/http://www.wyldryde.org/a/000911.php |date=2009-06-26 }} by WyldRyde. Accessed October 6, 2008.</ref>


There are several implementations of IRC services which have a ChanServ bot; some other services use other names, such as '''CS'''. The exact commands and features available depend on the service implementation and the network in question.
There are several implementations of IRC services which have a ChanServ bot; some other services use other names, such as '''CS'''. The exact commands and features available depend on the service implementation and the network in question.
Line 62: Line 62:
| title = ChanServ Information
| title = ChanServ Information
| url = http://docs.dal.net/docs/chanserv.html
| url = http://docs.dal.net/docs/chanserv.html
| accessdate = 13 May 2010
| access-date = 13 May 2010
| date = 8 March 2010
| date = 8 March 2010
| origyear = 2001
| orig-year = 2001
| publisher = [[DALnet]] IRC Network
| publisher = [[DALnet]] IRC Network
| chapter = Changing channel founders
| chapter = Changing channel founders
| chapterurl = http://docs.dal.net/docs/chanserv.html#11.1
| chapter-url = http://docs.dal.net/docs/chanserv.html#11.1
}}</ref>
}}</ref>
* Super Operator (often written as SOP or SOp)<ref>{{cite book
* Super operator (often written as SOP or SOp)<ref>{{cite book
| author = Mystro
| author = Mystro
| title = ChanServ Information
| title = ChanServ Information
| url = http://docs.dal.net/docs/chanserv.html
| url = http://docs.dal.net/docs/chanserv.html
| accessdate = 13 May 2010
| access-date = 13 May 2010
| date = 8 March 2010
| date = 8 March 2010
| origyear = 2001
| orig-year = 2001
| publisher = [[DALnet]] IRC Network
| publisher = DALnet IRC Network
| chapter = Adding/removing/listing SOps
| chapter = Adding/removing/listing SOps
| chapterurl = http://docs.dal.net/docs/chanserv.html#5
| chapter-url = http://docs.dal.net/docs/chanserv.html#5
}}</ref>
}}</ref>
* Auto Operator (often written as AOP or AOp)<ref>{{cite book
* Auto operator (often written as AOP or AOp)<ref>{{cite book
| author = Mystro
| author = Mystro
| title = ChanServ Information
| title = ChanServ Information
| url = http://docs.dal.net/docs/chanserv.html
| url = http://docs.dal.net/docs/chanserv.html
| accessdate = 13 May 2010
| access-date = 13 May 2010
| date = 8 March 2010
| date = 8 March 2010
| origyear = 2001
| orig-year = 2001
| publisher = [[DALnet]] IRC Network
| publisher = DALnet IRC Network
| chapter = Adding/removing/listing AOps
| chapter = Adding/removing/listing AOps
| chapterurl = http://docs.dal.net/docs/chanserv.html#6
| chapter-url = http://docs.dal.net/docs/chanserv.html#6
}}</ref>
}}</ref>


== OperServ {{anchor|OperServ|AKill}} ==
== OperServ {{anchor|OperServ|AKill}} ==
⚫
{{Redirect|AKill|the creator of Akbot, whose online pseudonym is AKILL|Owen Walker}}
'''OperServ''' is a component of most IRC services packages used to help administer an [[Internet Relay Chat]] network. It provides [[IRC operator]]s with functions to help monitor and maintain the network, manage the other services, and deal with problematic users.
'''OperServ''' is a component of most IRC services packages used to help administer an [[Internet Relay Chat]] network. It provides [[IRC operator]]s with functions to help monitor and maintain the network, manage the other services, and deal with problematic users.


Line 99: Line 100:
On [[DALnet]] a similar concept known as an "AKill" was used instead of a G-line. The term AKill comes from an earlier implementation in which the IRC services would automatically "kill" (disconnect) the user remotely upon login, rather than the individual servers simply denying the connection.
On [[DALnet]] a similar concept known as an "AKill" was used instead of a G-line. The term AKill comes from an earlier implementation in which the IRC services would automatically "kill" (disconnect) the user remotely upon login, rather than the individual servers simply denying the connection.


On [[OpenNap]] networks, OperServ is a pseudo-user which allows users above a specific permission level to execute server administration commands. Although primarily intended to supplement clients without built-in support for such actions, there are no restrictions on its use.
On OpenNap networks, OperServ is a pseudo-user which allows users above a specific permission level to execute server administration commands. Although primarily intended to supplement clients without built-in support for such actions, there are no restrictions on its use.


== IRC services software packages ==
== IRC services software packages ==
There are several [[computer software|software]] packages that implement services. Some of the popular ones include [[srvx]], [[Atheme]] (is to be discontinued by the developers<ref>http://www.is-atheme-dead-yet.net/</ref>), [[ChatServices]] (a fork of Atheme that is continued to be developed), Hybserv (developed for use with the [[IRCD-Hybrid|Hybrid IRCd]] software), [[Epona (IRC services)|Epona]], [[Anope]], and [[IRC Services 5]] (supporting a wide range of IRC daemons, considered the "original" IRC Services). 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.
There are several [[computer software|software]] packages that implement services. Some of the popular ones include '''srvx''', '''Atheme''', '''DalekIRC Services''', '''ChatServices''', Hybserv (developed for use with the '''Hybrid IRCd''' software), '''Epona''', '''Anope''', and '''IRC Services 5''' (supporting a wide range of IRC daemons, considered the "original" IRC Services). 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.

== Standardization ==
{{unreferenced section|date=June 2012}}
The IRC+ initiative was working on producing recommendations for services to use common numerics for essential functions, so that clients could have unified and simplified user interfaces for dealing with services for the most essential functions (like, registering an identity on an IRC network). However, due to lack of support, the IRC+ initiative have ceased their work.


== See also ==
== See also ==
* [[IRC commands]]
* [[IRC commands]]
* [[Comparison of Internet Relay Chat daemons]]
* [[Internet Relay Chat]]
* [[Internet Relay Chat]]
* [[IRC operator]]
* [[IRC operator]]
Line 124: Line 120:
| url = http://www.irc.org/tech_docs/ircnet/SERVICE.html
| url = http://www.irc.org/tech_docs/ircnet/SERVICE.html
| title = IRC Services
| title = IRC Services
| accessdate = 2009-07-02
| access-date = 2009-07-02
| last = Kalt
| last = Kalt
| first = Christophe
| first = Christophe
| authorlink =
| date = 1997-09-03
| date = 1997-09-03
}}
}}
Line 133: Line 128:
{{IRC topics}}
{{IRC topics}}


[[Category:Internet Relay Chat|Services, Internet Relay Chat]]
[[Category:IRC|Services, Internet Relay Chat]]
[[Category:Internet Relay Chat services| ]]
[[Category:IRC bots|Services, Internet Relay Chat]]

Latest revision as of 22:09, 11 June 2024

IRC services is a set of features implemented on many 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.

Components[edit]

The most popular style of services uses 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 to perform administrative functions. Also known as AdminServ, RootServ, or OpServ (srvx).

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

  • BotServ, a bot 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.
  • SpamServ, used to protect channels against spam.[1]
  • StatServ, a statistic services bot, is used to perform various statistical analysis on the IRC Network.

Other commonly used services bots:

  • 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[clarification needed] server so it has the ability to spoof nicknames. This service is often renamed to the name of the network (e.g. DalNet or Xevium.).

History[edit]

The original NickServ was written by Armin Gruner at the Technical University of Munich in 1990.[2] 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 to today's MemoServ.

It was considered acceptable behavior simply to /ignore NickServ's notices, but an operator decided to /kill NickServ and use the nickname NickServ himself, subsequently collecting all identify passwords from users and being amused by that.[citation needed] This led to a public debate over the usefulness and safety of services and 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.[citation needed] Some debate still remains over the value and benefits of Services on IRC, although they are generally considered essential to providing a pleasant chatting experience.[by whom?] This is proven in the fact that most service-less networks have died out.[citation needed]

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 Undernet and QuakeNet stick out with a completely different approach.

ChanServ [edit]

ChanServ, on many IRC networks, is an IRC service which maintains channel registration and access information.[3] If a channel is registered with ChanServ, its owners (and those they have designated) can use ChanServ to obtain control over the channel, gaining channel operator privileges. Most channel service bots also allow other sorts of channel management options, such as topic locks (in addition to +t), mode locks, and providing users automatically with operator status, half-operator status, voice, or other access, as designated by the channel owners. They may also provide some form of automated ban-list management.[4]

There are several implementations of IRC services which have a ChanServ bot; some other services use other names, such as CS. The exact commands and features available depend on the service implementation and the network in question.

Access levels [edit]

  • Founder[5]
  • Super operator (often written as SOP or SOp)[6]
  • Auto operator (often written as AOP or AOp)[7]

OperServ [edit]

"AKill" redirects here. For the creator of Akbot, whose online pseudonym is AKILL, see Owen Walker.

OperServ is a component of most IRC services packages used to help administer an Internet Relay Chat network. It provides IRC operators with functions to help monitor and maintain the network, manage the other services, and deal with problematic users.

Some of the more infamous functions of OperServ are the "lines", such as the K-line and G-line. These are used to discipline troublesome network users, however, other network lines are available for use. The exact features available depend upon a particular operator's permissions, and the specific implementation in use.

On DALnet a similar concept known as an "AKill" was used instead of a G-line. The term AKill comes from an earlier implementation in which the IRC services would automatically "kill" (disconnect) the user remotely upon login, rather than the individual servers simply denying the connection.

On OpenNap networks, OperServ is a pseudo-user which allows users above a specific permission level to execute server administration commands. Although primarily intended to supplement clients without built-in support for such actions, there are no restrictions on its use.

IRC services software packages[edit]

There are several software packages that implement services. Some of the popular ones include srvx, Atheme, DalekIRC Services, ChatServices, Hybserv (developed for use with the Hybrid IRCd software), Epona, Anope, and IRC Services 5 (supporting a wide range of IRC daemons, considered the "original" IRC Services). 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.

See also[edit]

References[edit]

  1. ^ ">> SpamServ". GameSurge. 2008-12-18. Retrieved 2013-07-11.
  2. ^ Bechar-Israeli, Haya (September 1995). "From <Bonehead> to <cLoNehEAd>: Nicknames, play, and identity on Internet Relay Chat". Journal of Computer-Mediated Communication. 1 (2). Bloomington, Indiana: Indiana University School of Library and Information Science. doi:10.1111/j.1083-6101.1995.tb00325.x. Retrieved 2020-03-29.
  3. ^ ChanServ Help by TechNerd. Accessed October 6, 2008.
  4. ^ What is ChanServ? Archived 2009-06-26 at the Wayback Machine by WyldRyde. Accessed October 6, 2008.
  5. ^ Mystro (8 March 2010) [2001]. "Changing channel founders". ChanServ Information. DALnet IRC Network. Retrieved 13 May 2010.
  6. ^ Mystro (8 March 2010) [2001]. "Adding/removing/listing SOps". ChanServ Information. DALnet IRC Network. Retrieved 13 May 2010.
  7. ^ Mystro (8 March 2010) [2001]. "Adding/removing/listing AOps". ChanServ Information. DALnet IRC Network. Retrieved 13 May 2010.

Further reading[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=IRC_services&oldid=1228559442"