Jump to content

EFnet: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m Characteristics: Why surprising?
Characteristics: EFnet used to have a NickServ until 1995...I used to have "Addams" registered on it
Line 33: Line 33:
Due to ''EFnet'' nature it has gained recognition over the years (as other IRC networks have) for [[warez]]<ref>http://www.wired.com/culture/lifestyle/news/2000/03/35141</ref>, [[hackers]]<ref>http://edition.cnn.com/2002/TECH/internet/04/10/hackers.chat.rooms/index.html</ref> [[DoS attacks]]<ref>http://www.vnunet.com/vnunet/news/2115605/efnet-eff-dos-attack</ref> and [[online help]]<ref>http://www.onlamp.com/pub/a/bsd/2001/12/27/Big_Scary_Daemons.html</ref>.
Due to ''EFnet'' nature it has gained recognition over the years (as other IRC networks have) for [[warez]]<ref>http://www.wired.com/culture/lifestyle/news/2000/03/35141</ref>, [[hackers]]<ref>http://edition.cnn.com/2002/TECH/internet/04/10/hackers.chat.rooms/index.html</ref> [[DoS attacks]]<ref>http://www.vnunet.com/vnunet/news/2115605/efnet-eff-dos-attack</ref> and [[online help]]<ref>http://www.onlamp.com/pub/a/bsd/2001/12/27/Big_Scary_Daemons.html</ref>.


''EFnet'' has always been known for its lack of IRC services that other IRC networks support (such as [[NickServ]] and [[ChanServ]]). However, in July 2001, a service called ''CHANFIX''<ref>http://www.irchelp.org/irchelp/ircd/chanfix.html</ref> (originally named ''JUPES'') was created, which is designed to give back ops to channels which have lost ops or been [[IRC takeover|taken over]].
''EFnet'' has always been known for its lack of IRC services that other IRC networks support (such as [[NickServ]] and [[ChanServ]], though EFnet once had a NickServ until 1995). However, in July 2001, a service called ''CHANFIX''<ref>http://www.irchelp.org/irchelp/ircd/chanfix.html</ref> (originally named ''JUPES'') was created, which is designed to give back ops to channels which have lost ops or been [[IRC takeover|taken over]].


For help with ''CHANFIX'' a user can find an [[IRC operator]] with the command: <code>/stats p</code> or by entering the <code>#chanfix</code> channel.
For help with ''CHANFIX'' a user can find an [[IRC operator]] with the command: <code>/stats p</code> or by entering the <code>#chanfix</code> channel.

Revision as of 13:51, 28 April 2009

Eris Free Network
Founded1990
Geographic locationUnited States
Europe
Canada
Based inWorldwide
Website URLwww.efnet.org
Primary DNSirc.efnet.org
Average users50,000 - 55,000
Average channels25,000 - 26,000
Average servers60
Content/subjectPublic/Unrestricted
File:Irc.efnet.org.gif
There are 42 EFnet servers in the world as of Dec 2008.

EFnet or Eris Free network is a major IRC network, with over 50,000 users[1]. It is the modern-day descendant of the original IRC network.

IRC clients can connect to EFnet via irc.efnet.org which will connect to an EFnet IRC server at random (using round robin), or clients may wish to connect to a geographically closer server.[2]

History

Initially, most IRC servers formed a single IRC network, to which new servers could join without restriction, but this was soon abused by people who set up servers to sabotage other users, channels, or servers. In August 1990, the server eris.berkeley.edu remained the only one to allow anyone to connect servers, IRC server operator Greg Lindahl ("wumpus") broke away to start EFnet. The resulting argument split the IRC community of admins into EFnet and A-net (Anarchy Network), which soon vanished, leaving EFnet as the only IRC network.

Continuing problems with performance and abuse eventually led to the rise of another major IRC network, Undernet, which split off in October 1992.

In July 1996, disagreement on policy caused EFnet to break in two: the slightly larger European half (including Australia and Japan) formed IRCnet, while the American servers continued as EFnet. This was widely known as the Great Split [3].

Characteristics

EFnet is probably the least "unified" IRC network, with large variations in rules and policy between different servers as well as the three major regions (EU, CA, and US) each have their own policy structure. Each region votes on their own server applications. However, central policies are voted upon by the server admin community which is archived for referencing.[4]

Due to EFnet nature it has gained recognition over the years (as other IRC networks have) for warez[5], hackers[6] DoS attacks[7] and online help[8].

EFnet has always been known for its lack of IRC services that other IRC networks support (such as NickServ and ChanServ, though EFnet once had a NickServ until 1995). However, in July 2001, a service called CHANFIX[9] (originally named JUPES) was created, which is designed to give back ops to channels which have lost ops or been taken over.

For help with CHANFIX a user can find an IRC operator with the command: /stats p or by entering the #chanfix channel.

February 2009 sees the introduction of a new CHANFIX module called OPME, a mechanism for EFnet Admins to use to restore ops in an opless channel.[10] It provides a much cleaner alternative to masskill, which is unnecessarily invasive and disruptive to the network.

A vast majority of servers on EFnet run ircd-ratbox. A handful run ircd-hybrid, and two run csircd[2].

EFnet channel operators are generally free to run their channels however they see fit without the intervention of IRCops. IRCops are primarily there to handle network and server related issues, and rarely get involved with channel level issues.[11]

In 2007 various EFnet servers began implementing SSL.[12]

References