Oper Policy

JetIRC Forum

Home
Up
Who's in Charge
Network News
Network Stats
Network Rules
IRC Explained
Help
Chat NOW!
Support JetIRC
Complaints / Abuse
Contact Us
Linking Servers
IRCop/Helper Login
Search This Site
Staff WebMail

 

 

Welcome to the Policy & Procedure guide for JetIRC Opers...

Topics covered: 

 07 Jul 2003 .  Expected Behavior  
15 Jan 2001 .  Use of GETPASS
16 Sep 2000 .  Other Oper Duties
07 Jul 2003 .  Killing Users
13 Sep 2000 .  Helping Users

Expected Behavior on JetIRC

While the JetIRC Network is tolerant of just about any activities, we will NOT put up with abusive or negligent Opers.  You are expected to remain courteous to Users and fellow Opers alike.  The exception, of course, comes when a User is out of line (see Killing). 

Please circulate and idle in lots of channels.  This makes it look "busier" on the network, and the channel owners will appreciate this.  However, unless specifically invited to do so, do not op yourself in a channel that is not yours.  If it is absolutely necessary to perform a needed task, then you may do so.  This is an issue of respect for the people that make this network grow.

It is helpful to also idle in #Help and #JetIRC because users who need help are told to join these channels.  It looks good if there's at least one person there that can actually help them...

IRCops, in general, are expected to follow the same rules as any other user.  You have the power to bend or break those rules, but may only do so if there is no other alternative!  If you break a network rule and a complaint is made against you, you will be required to justify your actions.  Keep logs, because if the complainer has logs and you don't, you're screwed.  Action will be taken against IRCops who violate network rules without proper reason.  This can result in anything from a reprimand, to losing your rank, losing your O:Line, or even being banned from the network (serious cases).

All Opers are expected to visit the IRCop area of the website regularly -- as in once a month or more!  Important news will be posted in this area, as well as notices about meetings and so on.

[ Top ]


Use of GETPASS

Only SAs and above can use GETPASS. (See the OperServ Help section on GETPASS for syntax, if you have access).  The procedure for using GETPASS is as follows, and is not to be deviated from.

For Nickname Passwords

1.  ONLY give out a user's password if you are ABSOLUTELY sure that they are who they claim to be.

2.  Use the /whowas <nick> command to find their last couple of host masks.  Then use /whois to see the current host mask. 

3.  If the host masks match up closely enough, you may release the password.

4.  If you are ever unsure, please refer them to a Network Admin.

For Channel Passwords

1.  First have them identify for their nick (if they haven't already).

2.  Check /chanserv info #channel to determine the name of the founder.

3.  If the user you're talking to is not the founder... Tell them to go find the real founder.

4.  If they have identified for the nick, and they are the founder, you may release the password.

5.  If you are ever unsure, please refer them to a Network Admin.

[ Top ]


Other Oper Duties

All SOPs and SAs are to idle in #JetIRC and check in with #Help as often as possible whenever they are online.  Failure to do so can result in a loss of Services OP privileges.  Please check in that channel from time to time, as this is where Users go when they loose their passwords or need help.

SOPs have the right to add akills. Referrals for permanent kills (and/or Klines) are to be sent to a Network Admin.  You can also email them to kline@jetirc.net

[ Top ]


Killing Users

Killing a User is serious.  All kills are logged, as are all other commands.  IRCops that go on a "rampage" will quickly find themselves without an O:Line ... 

In most circumstances, you will find you want to kill a User because they are being an idiot... Unless they are seriously irritating others by private message (kick/ban them from the channel otherwise) and/or are advertising another Network, they should at least be given the opportunity to stop.  A warning to the offending user is preferred.  If they do not stop their activity, then you may kill them.

Unless you are an SOP, akills are impossible.  Klines and Permanent AKills are likewise prohibited to anyone other than a Network Admin.  

If you feel a users needs akilling, please ensure you put a reason, a date of the kill, and the email address abuse@jetirc.net into the reason field of the akill. 

eg: /operserv akill add mask@*.mask.* Harassing 

.........Users 15Jan01 - To dispute email 

.........abuse@jetirc.net

Note that akills last for 7 days and then automatically expire.  If you feel the user should be permanently killed, either email abuse@jetirc.net or memo a Network Admin.  Same goes for Kline or GLine.  

It is this network's policy to avoid adding Klines or GLines.  They are usually more trouble then they're worth -- however, if the need should arise, a GLine should be used instead of Kline.  Gline will ban across the entire network, while Kline is specific to one server.

[ Top ]


Helping Users

It is the duty of all Opers to help Users whenever needed.  The exception to this could be if the User is being an ass and no matter how much you explain the answer to their question, they just don't get it... Try for a while, but if you are getting nowhere, refer them to someone else.

If a user asks a question you can't answer, refer them upwards.  Please take the time to get to know who the higher-level Opers are (SOPs, SAs, Admins).  If in doubt, refer to the Who Can Help Me Online? page.

Also, you can save a lot of time by simply referring users to this website for help.

[ Top ]



 

Questions, suggestions, or comments about this website?  Contact Us
All page content (c) 2000-2006 JetIRC Network
c/o David Taylor (aka Saturn).  All rights reserved.  You may include content on this website on any other website, provided it is accompanied by "This material is (c) David Taylor and used with the permission on JetIRC.net." in clear text, visible immediately before or after the body of the borrowed text.

POWERED BY TitaniumWebs.com