This page lists people who have chanserv access to #debian* channels.
- weasel, dondelelcaro, Myon, Ganneff, azeem, gravity, helix, mentor, Maulkin, stew, peterS, zobel, abrotman, themill, RichiH, babilen, SynrG, somiaj, jm_
Hydroxide, dondelelcaro, greycat, helix, ljlane, ?LoRez, RichiH, mentor, Netsnipe, TML, xk, gravity, azeem, Maulkin, stew, zobel, abrotman, themill, babilen, SynrG, somiaj, jm_
- weasel, dondelelcaro, Myon, Ganneff, azeem, gravity, helix, mentor, Maulkin, stew, peterS, zobel, abrotman, themill, RichiH, babilen, SynrG, somiaj
- abrotman, Ganneff, themill, SynrG
- abrotman, beardy, themill, SynrG
- Founder: nobse
- weasel, Kamion, Oskuro, vorlon, huggie, Ganneff, aba, zobel, Myon
- weasel, wiggy, Joy, waldi, Kamion, vorlon, Ganneff, aba
- Myon, Maulkin, Signum, eim
- Ganneff, elmo, HE, tbm, Myon, pasc, mako, aba, maxx, djpig, azeem
- Founder: willy
- aba, Myon, zobel
- zobel, aba, HE, vorlon, luk Founder: aba
- Founder: helix
- weasel, Ganneff, Joey, Alfie, waldi miro, azeem, towo, youam, HE, Myon, aba, nforcer, maxx, Marillion, zobel
- Alfie, andreasj, azeem, Bluehorn, blue^lap, CHS, codebreaker, eRich, fd0, formorer, Ganneff, Getty, Harlekin, HE, hps, jef, madd, maxx, Myon, NForcer nicki, nobse, panthera, plaisthos, Salz, stockholm, Tolimar, towo, waldi, weasel, Yarihm, youam, zobel, Zomb, _rene_
- Myon, aba, weasel, waldi, HE, Ganneff, maxx, Tolimar, panthera
- Founder: noodles
- Founder: wiggy
- Founder: dondelelcaro
- Founder: dondelelcaro
IRC Operator Information and Guidelines
This information is primarily informative, and non-normative; different channels may have different guidelines.
- -- Handles being opped, banning, and kicking, and then deopping as appropriate.
- Be a force for good
- Don't be afraid to use temporary +q/+b as a cooling down period
- Try not to remain +o
- When in doubt, it's OK to be proactive, but then seek consensus where possible
The IRC servers typically have a maximum number of bans that can be associated with a channel and in busy channels with more than their fair share of spam bots, trolls and trouble makers, this maximum can be reached fairly easily. Both Freenode and OFTC have a limit of 100 on the ban lists for a channel. To help keep the ban lists clean, to help avoid unintended bans of people with dynamic IPs and to avoid being overly harsh, ban trackers can be used to record why bans were placed and to lift the bans after a certain period of time. Ban tracking bots do a much better job of this than timeouts in individual operator's IRC clients; the information stored in the bots is only available to channel operators.
Two ban tracking bots are in use at present: eir on Freenode and debchange on OFTC.
eir is extensively documented on the Freenode website github. For the channel operator, the basic usage is:
- After setting a ban, eir will send a request in private message requesting a comment on the ban, for example:
<eir> Please comment on the following: ban *!*@troll.example.net was set on #debian by firstname.lastname@example.org on 2014-04-09 14:42:00 and had an expiry date of 2014-04-09 16:42:00.
- A specially constructed reply to eir can change both the expiry and also annotate the ban with a comment.
<star_op> %~14d persistent trolling
The syntax tells eir to gain operator privileges if needed, to remove the ban (rather than just warn it is expired) and instructs that the ban should expire in 14 days. The default timeout is 2 hours; suffixes of m, h, d are all understood by eir.
Other useful commands for eir are
btinfo 63807: displays the expiry time and comment on a particular ban
btpending #debian: displays the bans that eir has not received any comment for
btset 63807 %~28d persistent trolling; also abusive in private message: amend the details already set for a ban
debchange uses the ChanTracker plugin. For the channel operator, the basic usage is:
- After setting a ban, debchange will send a request in private message requesting a comend on the ban, for example:
<debchange> For [#64 +q *!*@troll.example.net in #debian - 1 user(s)] type <duration> <reason>, you have 3 minutes
- A specially constructed reply to debchange can change both the expiry and annotate the ban with a comment.
<star_op> 14d persistent trolling
The bot will automatically remove the ban on expiry. The default timeout is 2 hours; suffixes of m, h, d are all understood by debchange. If you don't reply within the alloted 3 minutes, then use the edit and mark commands below.
Other useful commands for debchange are:
edit 64 28d: edit ban number 64, changing the expiry to 28 days
mark 64 persistent trolling; also abusive in private message: amend the annotation ('mark') already set for a ban
affect 64: list the users that this ban applies to
check #debian *!*@example.net: list all users that would be affected were that hostmask to banned
match #debian badguy: list all the bans (including expiry times and annotations) that apply to the specified nick