Hi there, please find the following text in your language and delete EVERYTHING:

Below is a list of the teams that are currently active on DALnet.

Coders Team <email>dalnet-src@dal.net</email>

The members of the Coders Team are the people who code the DALnet IRCD. They program, make the necessary adjustments, and perform maintenance when needed. They create the new commands within Services. They make life on DALnet possible!

Help Committee <email>hc@dal.net</email>

The Help Committee's main responsibility is to assist the users in various ways. They set general policies for recommended help channels in order to maintain a high standard of help on DALnet. Basically, the team consists of one member from each DALnet owned help channel. The Help Committee works in several areas, therefore, sub-teams have been created.

Documentation Team (HC Sub-team) <email>docs@dal.net</email>

This team is responsible for all the documents about DALnet, its Services, and various other applications that can be of some help to the users on the network. The Docs Team make them available and understandable for everyone who wishes to consult them. This involves the translation of the documents to quite a few different languages so that users who do not have English as their first language can be accommodated, too.

help.dal.net Web Team (HC Sub-team) <email>help-www@dal.net</email>

This team is responsible for maintaining and updating the Help Committee websites. The Web Team makes sure that the information provided on these websites are accurate and up-to-date, so the users can navigate through it with the confidence that the information there is current and correct.

Hostmasters Team <email>hostmaster@dal.net</email>

They handle everything related with DNS issues and configuration for the net. This includes setting up DNS entries for new servers and maintaining the server pool.

KLine Team <url>http://www.dal.net/admin/contactkline.php3</url>

DALnet's KLine team was established as a mediator between DALnet, the offenders and the providers, in the hopes of reaching a peaceful resolution to any questions regarding autokills that are in place. Whether the question comes from a DALnet user, a staff member, or a provider, it's up to the KLine team to offer proof upon request regarding any charge of abuse. Please keep in mind that the DALnet IRC Network, as well as any server linked to DALnet, have the right to deny any access to its network for any reason, with or without cause. Abuse includes, but is not limited to: mass-advertising, open proxy abuse, exploiting of viruses or any material that might cause damage to another user, cloning, evading autokills and evading channel bans. Each area is handled by a specialized sub-team.

Closers Team (KLine Sub-team) <email>closers@dal.net</email>

The purpose of the Closers team is to deal with channels that have been closed. The Closers Team will interact with both the users and the DALnet operators in resolving issues regarding closed channels. The Closers Team, upon request of a DALnet user, operator, or other source, will directly investigate the circumstances surrounding the closing of the channel in question, and return an evaluation of the situation to the person making the request.

The Closers Team may make one of several choices based on the evidence provided. Some sort of agreement would be made with the staff who closed the channel that the closure was the correct solution, and state so to the person making the request after finding conclusive evidence to support the action.

Reopen the channel based on:

a) A lack of supporting evidence to warrant the channel being closed.

b) Finding the close was not an appropriate method of stopping the alleged abuse.

Decide the situation requires more investigation and contact the CSop that closed the channel in order to obtain a better perspective of the circumstances related to the close.

Note: In case of a frozen channel, contact http://www.dal.net/admin/contactkline.php3 or the Csop who froze it. The closers team will not deal with frozen channel issues.

CyberCafe (KLine Sub-team) <email>cybercafe@dal.net</email>

This team keeps record of the authorized cybercafes; in order for your site not to be considered a multiple clones site from DALnet's Administration and Services, some general contact information is needed for recognition purposes to ensure your connections are not terminated.

Massads Team (KLine Sub-team) <url>http://www.dal.net/admin/contactmassad.php3</url>

The DALnet Massads team was established as a mediator between the users and the providers that were autokilled for spamming (which includes both channel invites and web sites). This team is responsible for communication between the users and the providers, in an effort to curb spamming on DALnet.

Due to the recent surge of virii that search websites for email address', the Massads Team only accepts online contact. If you wish to report a spam, please visit http://www.dal.net/admin/contactmassad.php3; make sure a time-stamped and dated log and the /whois of the spammer is included.

Exploits Prevention Team <url>http://kline.dal.net/exploits/contact.htm</url>

The DALnet Exploits Prevention Team was established as a mediator for users who have been autokilled for exploiting other users, either knowingly or unknowingly. If a user is autokilled for exploits, and they didn't know they were infected, it is this team's job to help them remove the exploit from their system, so that they may get back online. For users that do this knowingly, this team also contacts the provider about the abuse issue. Where #nohack is the front end of this overall operation, the Exploits Prevention Team is the back end. #nohack tries to help before it becomes an issue with an autokill. The Exploits Prevention Team helps you after you've been autokilled. They are also responsible for identifying the exploitative scripts and add-ons. They also deal with clones and open proxy abuse.

Services Abuse Team <email>sabuse@dal.net</email>

The purpose of this team is to deal with abuse issues directly related to the DALnet Services. This is to include both user connections as well as other IRC Operator connections. The forms of abuse include, but not limited to: mass nickname registrations, mass channel registrations, flooding, or spamming users via MemoServ, use of *!*@*.* in the access list, the AOp lists, or the SOp lists.

Postmasters Team <email>postmaster@dal.net</email>

The postmasters basically maintain all the @dal.net mailing lists and manage the database of opers and their email aliases.

Moderators Team (Postmasters Sub-team) <email>moderators@dal.net</email>

The people on this team moderate DALnet's mailing lists. They are in charge of keeping spams off the lists and filtering the posts for off-topic postings or flames.

Routing Team <email>routing@dal.net</email>

This team maintains links between servers. The Routing Team reconnects servers to optimize the network structure.

Training Team (No public email address)

This team's mission is to provide consistent training for all newly selected IRCops, Services Administrators and CSOps. This team will not train you to become an IRCop. They only train those who have already been selected as such.

Web Team <url>http://www.dal.net/admin/submit.php3</url>

This team is in charge of general maintenance and updating of DALnet's website. The Web Team is responsible for all the information contained on the website.

Administrative Oversight Board (Formerly known as Executive Board) <email>aob@dal.net</email>

They have the maximum authority on DALnet. They overview the general control of DALnet, as it may be settling disputes, or deciding on server CFVs.

Services Root Administrators <email>sra@dal.net</email>

These people have the highest level of access to the Services. They decide who deserves a CSOp status and manage Services at a console level (not to the ability of the coders though, in other words, coders actually dig around in Services code, SRAs don't). They have the ability to login to the machine on which Services is running and perform various operations. IRCops are told to go to them if they have any questions. They make rulings on many things, including IRC operator accesses. They also established the IRC operator code of behavior.

If this is done, please continue with that: Old text: "Lefler then was the one assigned to code MemoServ. JoelKatz maintained that code after that, made a few improvements, got rid of a lot of bugs and made Services cope with the increasing number of users, until a rewrite by taz. Services are being developed and maintained by MSofty." New text: "Lefler then was the one assigned to code MemoServ. Aetobatus maintained the services code after that and later JoelKatz joined as well and made a few improvements, got rid of a lot of bugs and made Services cope with the increasing number of users, until a rewrite by taz. Services are being developed and maintained by MSofty, Kobi_S, skill and xPsycho." Old text: "NickServ was born a couple months later on March 1, 1995. The first registered nick was Morph but over the years he changed it from Morph to Morpher which is why the date is no longer accurate. The oldest registered nicks today are JoeBlow, WatchMan, MirclMax, RunAbot and dalvenjah, in that order." New text: "NickServ was born a couple months later on March 1, 1995. The first registered nick was Morph but over the years he changed it from Morph to Morpher which is why the date is no longer accurate. The oldest registered nicks today are JoeBlow, WatchMan, MirclMax and dalvenjah, in that order." Old text: "On March 22nd 2000, dalvenjah turned over the CEO (Chief Executive Officer) position to taz, due to real life considerations which made it impossible for him to attend to DALnet as much as was needed. dalvenjah did a wonderful job, and taz continued the tradition. taz left in January 2003 handing it over to MirclMax with a new badge Director of Network Operations abolishing the CEO and the COO badges, MirclMax still is the current DNO." New text: "On March 22nd 2000, dalvenjah turned over the CEO (Chief Executive Officer) position to taz, due to real life considerations which made it impossible for him to attend to DALnet as much as was needed. dalvenjah did a wonderful job, and taz continued the tradition. taz left in January 2003 handing it over to MirclMax with a new badge Director of Network Operations abolishing the CEO and the COO badges. On June 8th, MirclMax turned over the DNO position to Ahnberg who is still the current DNO." Old text (for Ahnberg): "Joined DALnet in 1995. Currently admin for mozilla.*, member of the AOB, current SRA member, testnet and Hostmasters. Team Leader for Routing, responsible for server applications. Also responsible for calling and accounting for all the votes that take place on DALnet. Friendly and always there when you need him." New text (for Ahnberg): "Joined DALnet in 1995. Currently DNO, admin for mozilla.*, member of most of the teams. Friendly and always there when you need him." Old text (for Dakal): "Former Leader for Routing Team. Co-Created the new training team along with White_Dragon. Did a lot of technical work on DALnet." New text (for Dakal): "Former SRA member, Former Leader for Routing Team. Co-Created the new training team along with White_Dragon. Did a lot of technical work on DALnet." Old text (for JoelKatz): "Former AOB member, ex Coding Director, and ex SRA. He wrote the original CSOp guides. Former admin of quite a few servers (igc.*, enterprise.*, glass.*, wizlink.*, host.*) Basically he just stopped doing things, and that's why he isn't any of those things anymore. Barely comes online at all anymore. Used to be active on the mailing lists." New text (for JoelKatz): "Former AOB member, ex Coding Director, and ex SRA. He wrote the original CSOp guides. Former admin of quite a few servers (igc.*, enterprise.*, glass.*, wizlink.*, host.*). Barely comes online at all anymore. Used to be active on the mailing lists." Old text: "The various positions in a team are instated according to the needs of each team. Generally, you can regard the teams as a group of people with a common goal. Some of these teams require the team members to have a certain access level to Services (for example, KLine, Services Root Administrators, and Coders), while others (for example, Postmasters, Hostmasters, and some Help Committee sub-teams) do not. For more information on DALnet's teams, please visit:http://www.dal.net/admin/teams.php3 " New text: "The various positions in a team are instated according to the needs of each team. Generally, you can regard the teams as a group of people with a common goal. Some of these teams require the team members to have a certain access level to Services (for example, KLine, Services Abuse and Services Root Administrators), while others (for example, Postmasters, Hostmasters, and some Help Committee sub-teams) do not. For more information on DALnet's teams, please visit:http://www.dal.net/admin/teams.php3"