Operators' Code of Conduct

From Interlinked
Jump to: navigation, search

This is intended to be a non-exhaustive guide to the rules that should be followed at all times on Interlinked when you are an IRC operator. Note that these rules are subject to change, but only with notice.

Most of these fall under common sense. As such, it is expected opers should use common sense at all times on the network.

The rules are not complicated, mostly.

Privacy policy (what not to disclose)

  • Services-related information that is not already public should not be released. This includes e-mail addresses set private, private metadata, and nicks in a group.
  • User IPs are not to be disclosed as long as a user is under cloak (umode +x or v-host) without permission.
  • Hub IPs are never to be disclosed.
  • Do not disclose personally identifiable details about a user (including their name) without permission.
  • Avoid disclosing routing and network topology details.
  • Do not discuss bans about users without discussing their disclosure first.
  • Do not have debates regarding changes to the Code of Conduct or to any other network rules and policies in public; an exception may be granted to straw poll users on proposed changes.
  • Operators should not discuss the actions of other operators in public channels unless explicitly permitted by the transparency policy.
  • Only disclose internal network tools when appropriate.

Transparency policy (what may be disclosed)

  • Client servers that are open to the public should be published in DNS.
  • It is OK to disclose the v-host a user has.
  • You may inform users about the tools we use to manage the network if they are open-source.
  • It is OK to disclose information regarding a particular user if the user in question authorises such.
  • Maintenance issues should always be discussed openly and frankly if they affect end-users.
  • Possible outages should be disclosed if they will affect end users.
  • K:Line channels should always be disclosed.
  • Distribution of the Operators' Code of Conduct is unlimited and unencumbered.
  • Anything not covered by the transparency or privacy policies should be discussed with the other operators.
  • Anything discussed in #opers is to be subject to the privacy and transparency policies.

Behaviour towards users

  • Limit the scope of bans as much as is feasible.
  • Only K:Line users which affect the network seriously (botnetters), are severely slandering users without just cause (e.g. accusations of rape, paedophilia, or murder), or are clearly committing major crimes (legitimately attempting to seduce minors, trading child pornography or warez, etc.).
  • Evasion should result in a resetting of the duration time for the first offence and at least a six-times-longer K:Line for the next offence.
  • All K:Line-appeal decisions are final.
  • Operators should try to treat users with courtesy and respect – this includes not trolling users.
  • Friendly bots (ones that do not harass, highly annoy, or spam) should remain undisturbed.
  • Hostile bots (ones that DO harass, highly annoy, or spam) should be terminated with extreme prejudice.
  • When users make an inquiry, if possible, direct them to a service that allows for self-assistance. "Give a man a fish, and you feed him for a day; teach him to fish, and you feed him for a lifetime."
  • Do not invite users to private network channels or disclose private information.

Behaviour towards other operators

  • Be civil to other operators at all times.
  • No joke or retaliatory kills will be tolerated.
  • Creation of new operators as well as ejection from the operator team for any reason by a network administrator is final if a plurality of network administrators agree to the ejection or creation.
  • Creation or ejection of a network administrator requires a plurality of the entire operator team.
  • The network is jointly owned and operated by the operators and network administrators. Please behave accordingly.
  • Arguments and disputes will be moderated by network administrators and dealt with accordingly.
  • All network administrator decisions are final.

Usage of services

  • Misuse of services is prohibited.
  • If possible, perform network maintenance actions through services.
  • Avoid using K:Line directly; it is preferable to use AKILL instead (often referred to as K:Line due to the underlying mechanism).
  • Operators may not forcibly drop nicks to take them.
  • Global notices should be used for network service announcements only.
  • Operators may not forcibly drop channels to take them unless a plurality of operators agrees it ought to be a network channel, or it is being used for malicious activity.
  • Operators may not forcibly RESV nicks unless they are visually irritating (hard to read, etc.), used for spam, or maliciously crafted.
  • Limit use of overriding modes to urgent use only.

Usage of the IRCd

  • Limit use of overriding +bijklq to urgent use only.
  • +P should be set on all channels with a significant presence.
  • Please be courteous and limit operspy usage.
  • Please keep the snotes down or Kyle will yell. Without him we would be overrun with snotes, and all would be lost.Kyle is gone. Spam the snotes away!

Behaviour as a user of the network

  • It is not OK to flood channels because you have flood limits disabled.
  • It is not OK to use your status to gain favour in channels.
  • Please keep your behaviour when not actively performing operator duties in line of that of a normal user.