AustNet Home
About
Support
Services
Servers
Administration
AustNet Charter
ASD
Server Applications
Vote Centre
Contact
Copyright © 1998 austnet.org
 20 December 1998 Preface The AustNet IRC Network is supposed to be a friendly network of communication. Less lag, no collides, kills etc. ASD Operators are friendly and helpful. If you need services help, you can always get it from #ASD, and ASD Operators are expected to behave in accordance with the status quo of IRC. This means that you are to oversee the operations of services and #ASD as an operator of the channel. This also means that you general duties of being an ASD Operator are to act in a respectful and disciplined way. If a user annoys you, do not show that you are annoyed. Everyone is entitled to their opinion. You are expected to use /ignore like everyone else. Definitions The following terms and abbreviations will be used throughout this document:
General Behavior In regard to the operations of the ASD, ASD Operators are not to swear, be abusive (whether in response to abuse or not) and act in a civilised manner. The emphasis is on self-control and discipline. A lot of it is common sense. Please do not use abusive or possibly abusive language or be offensive in nature. You will find your self on a short route OUT of the department if you behave like this. Please adhere to common sense and logical reasoning and never let hot headedness become your enemy. #ASD #ASD is the channel of the AustNet Services Department. It is there for people to obtain swift, efficient and correct information when they require help with services. Therefore you will provide them with exactly that. As an ASD Operator, you are expected to frequent #ASD as often as possible, or else your access will be suspended or removed indefinately. However, behavior such as the following will not be tolerated:
* h4x0r watches as the sights level on WarHead. Not only is it flooding, it is annoying to other users as the above is totally unrelated to services, is a pain, and confuses newbies. On top of that, pounding someone 20ft into the ground is not very polite and comforting. There is also to be absolutely no idle chat (i.e. non-services discussion) when somebody requires assistance, nor is there to be abusive behavior or giving out of incorrect information. All idle chat should be taken to #ASD-Conference. Do not ban people from #ASD in jest or just for fun. It's not a game, it's channel. It's all about a communication network. If you do ban someone, the ASD Administration will expect to find a good reason for it (preferably in a log file) or someone to vouch that it was necessary should we get any complaints. The general reasons that will be accepted:
Be reminded that banning a user has the effect of a mute on them so they are unable to speak or unable to change their nick. If they leave the channel they won't be able to get back in (obviously) so if someone is being abusive, just place a ban on them for a while (do not kick them) but the ban will prevent them from saying anything, and this may let them calm down or they will become more frustrated and leave. If they personally abuse you, inform them if they persist they will be ignored. Then ignore them if they persist. Host bans are bans such as *!*@student.uq.edu.au prevent all users from student services at the University of Queensland from accessing the channel or speaking if they are already present on this. This is to be used only if no other way to prevent unacceptable behaviour is possible. In the case where a user is using an dynamic SLIP/PPP address such as [email protected], you may have to ban the host, *!*@cs5p11.gil.com.au, to prevent them changing their username which is always a problem with PPP/SLIP accounts. Domain bans ban the entire domain of a network. An example would be *!*@*.ozemail.com.au. This would prevent anyone using OzEmail to enter #ASD or speak if they are on it. When you're talking domain bans such as *!*@*.ozemail.com.au, you're talking about banning a lot of people, remember that when you think about domain banning someone. Domain bans are highly discouraged, and require a very good reason. Generally you shouldn't have to do this unless for some reason a user has multiple accounts over that network or is perhaps even an administrator of the network and able to twist his host and username to his own means. Opping users who are not official ASD Operators and who are not on the op list is strictly prohibited and will result in suspension of both #ASD and services access. Whenever changes occur, you will be notified so there is no excuse whatsoever for breaching this rule. Weddings To have a wedding the netcouple must first book it. When they book it, a note is sent to #chapel. Once they have booked, someone from the #chapel database contacts them to arrange a suitable time. Make sure the to be married couple are using the nicks that are listed on the engaged list database (/msg loveop netcouple list engaged *) or LoveOP won't recognise them.
Nick Deletes This is generally used when you see the global notices possible nick abuse. However if it is a common mask (eg user@*.sg) it will show all people with that mask as being connected. Please check by messaging the nick to see if they are on a network/lan, if they are a school, or have a reason for needing more than 4 nicknames.
If there are a large number of nicks registered, as is usually the case with nick "stealers" or holders, then find an ASD Administrator to mass-delete all the nicks, instead of sending a flood of delete commands. If there are no ASD administrators active, set an OPAS ignore and delete the nicks. Password Retrieval All users have email addresses stored with NickOP. There is NO reason to tell any user his password; you should instead mail it to the address given (services will do this for you with the -email optioin). If that address is not valid, nothing can be done. The only exception is that if there are minor typing errors in the set e-mail address, e.g. brackets enclosing or, ".ua" instead of ".au". In this case, use NickOP to correct the e-mail address, and then send the password. Obvious changes to the username or host (e.g. "admin" to "administrator") do not count. Channel owner's nickname has expired
Suspension for services abuse This can include note, seek and funmsg flooding, or using topic to advertise other networks, etc.
Suspension for advertising or mass inviting This is when a channel goes into other channels disrupts their sessions and tells everyone to come to their channel. This can be done by joining other channels and doing it on a channel, or private messages, or mass spamming without joining.
Using ASD access to control ChanOP Do not do this unless there are no alternatives. ASD does not own the channel, so we do not have the right to use ChanOP unless there is abuse going on and there is no other means to rectify a situation that could affect other people in a bad way. Flooding, virus spreading, and other non-services abuse is not to be dealt with by ASD Operators in any circumstances. You are to let the channel operators deal with it, or obtain the assistance of a network operator. Remember, ASD is for services assistance only. Denying registration to a nick or channel This is used only if a user is abusing services. Do not use this facility in fun. Instructing the Services to ignore a user Do not use this command unless necessary: its effects are permanent. Once on services ignore, a person cannot remove themselves -- therefore it is up to you to maintain ignores you set. Protecting a channel or nick from automatic expiration Only do this for Austnet related channels or nicks (helpers/opers, promotion channels etc). Exceptions are sometimes made by ASD Administrators on a temporary basis. Modifying the registration status of a channel Use this in situations such as promotions where an email has been sent to austnet.org. This is also used to change a registered owner or remove a channel.
Administration If someone is deleted from ASD please send note to #ASD so we know. If someone is added to ASD please send note to #ASD, quoting the level. All ASD Operators are required to be subscribed to the services mailing list [email protected]. Information on how-to-subscribe can be obtained from http://www.austnet.org/. It is also up to you to make sure your austnet.org e-mail address is always correct by contacting the AustNet CEO, or whoever is delegated to maintain the e-mail aliases at the time. Occasionally a time and date will be set for conferences and training sessions. You are expected to attend, or else you are required to contact the ASD HOD and give reasons to your absenence in advance. The same applies should you be on leave for an extended period, otherwise access suspension or removal may occur. Abuse Any ASD Operator caught abusing their access will be dealt with harshly. All cases of abuse should be sent to [email protected] or the current ASD HOD with relevant logs and information supporting the case. All mail sent to these addresses is treated as strictly confidential.
|
