IRC is meant to be fun. We like to keep it that way, so follow the rules
please. If not, you're looking at being suspended or your O:Line (Opers)
removed.
1. All IRCops/Admins must log. This is to show your
Admins or the Network Admins what happened, if something does happen.
Plus, it is good to keep a log of what you do.2. OPing yourself in
any channel is a BIG no-no. If You own the room, that is
different. But we ask that you PLEASE USE SERVICES. This is why we
have them. You can
lose your O:Line if we catch you doing this without just cause
(another good reason for logs).
3. K:Lines - DO NOT USE THEM. If services are down, you
must ask a Tech Admin/Network Admin. We do not like them, and they're
hard to keep track of, so as a rule we do not use them. Requests for
permanent kills go to
kline@jetirc.net.
4. BANWALK - DO NOT ABUSE IT. If you are banned from a
channel, then stay out, unless you are doing something Network/Server based.
Channel Owners run their channel any way they want to, and Opers must
respect that. Complaints will go to Saturn. Once banned
from a channel, you must
/invite yourself into the channel to banwalk. We cannot stress
enough that this is only to be done in emergencies.
5.
Channel/User Modes. We as IRCops/Server Admins/Network Admins, can
override
ANY user/channel modes except for +H (prevents Opers with
+I from entering the channel). If you're not sure what modes are set for a
channel, do /chanserv info #channel. Do NOT
change channel modes UNLESS YOU HAVE TO, or are ASKED TO DO
IT
by the channel owner or a Network Admin, or it's necessary for the
security of the Network.
6. Channel Takeovers. We might get this, and if so, all Opers
are to STOP the Channel Takeover. Log an IP and/or host mask
and nick and give them to an Admin. If one is not on at the time,
email or memo Saturn. Then add an akill (if you have the access).
Tell Saturn (in any case), so that we know what to look for. Someone
may say the channel password was hacked. Do not do anything unless you're on
the Abuse Team.
7. Do not use your IRCop/Admin status as a
Symbol. This can get your O:Line taken or server delinked. In other
words, don't abuse your power.
8. You are required to be registered on the
Forum.
Additionally, it is every staff members' responsibility to check in
with the forum frequently (minimum weekly) as news and updates are
posted there. Ignorance is NOT an excuse!
9. IRCops
with the capability may only change users' nicks, to Guest#### or for a
similar NECESSARY function, but are not to "play" with it.
10. Be careful if testing out cloned connections (that you
own). Even as an IRCop you are subject to the same restrictions of 4
clones. If you need a higher limit, please contact Saturn. All
Opers can have as many clones as they like, with no hassle. BUT you need
Saturn
to set and exemption for you first!
Q. How Do I add an akill?
First, you must be a Services Operator (SOP). Then do a
/whois on the User. Find where this person is connecting from. Then do
/operserv akill add <*@host> <reason> <date> to
dispute email kline@jetirc.net
Set a Wildcard on the Ident. We have you do that for better
security. Make sure you put in the Date and put "to dispute email
kline@jetirc.net" That way, the Abuse Team will be able look at
it, and the user has a method of appeal. LOG IT AND WHY YOU ADDED IT
so, if they spammed, make sure you have a record.
EXAMPLE: If Blah was spamming, you would do
/whois Blah ... Then do
/operserv akill add *@yourmom.is.gone.com* You were spamming 21sep00 To
dispute email kline@jetirc.net Then you memo Saturn about
it, including the entire akill confirmation line (Status window). That is
when Saturn looks at it and fixes it from there. Failure to
notify Saturn can result in sever penalties.
/Kill is a neat Item to Opers. This means we kick the user from the
server (disconnect them) until they come back. In other words, they are
immediately disconnected, but can also immediately reconnect with no
delay. This is not the same as an akill or a Kline.
Again, keep a log, in case you are asked to justify the kill later.
Procedure: Put the reason and the date.
EXAMPLE: /kill User Abusing Services 21sep00 -- This is
to show them (and the Admins) why they were killed and what date it
happened.
