| Irc Services |
Article Index for Irc |
Website Links For Internet Relay |
Information AboutIrc Services |
| CATEGORIES ABOUT INTERNET RELAY CHAT SERVICES | |
| irc services | |
|
COMPONENTS 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.
Some others are also seen following this naming convention in some services packages including:
HISTORY 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 this or that 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 and EFnet 's ''Nicknames are not owned'' policy arose. In 1995 DALnet invented ChanServ, then re-implemented ''NickServ'' and ''MemoServ''. Today EFnet and IRCnet are pretty much 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. IRC SERVICES SOFTWARE PACKAGES There are several 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. STANDARDIZATION 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). SEE ALSO EXTERNAL LINKS
|
|
|