UbugtuChannelGuard

Differences between revisions 5 and 6
Revision 5 as of 2006-07-04 23:09:05
Size: 1595
Editor: seveas
Comment:
Revision 6 as of 2006-07-05 21:46:07
Size: 1725
Editor: host-87-74-66-37
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 * Would have to have an exception for i.e. netsplits, where there are necessarily many join/parts, often by unregistered users.

There has to be a way to automatically protect Ubuntu channels (mainly #ubuntu since it's the only one often attacked). This includes flood protection, badword banning etc.

Flood protection

Ubugtu should protect against floods

  • Join floods should trigger measures like a mode +rR (The +R is important, it suppresses part/quit messages)
  • Text floods should trigger a one minute mute and a message to use the pastebin for floods, second flood triggers an unlimited mute (ie: to be removed by operator)
  • Would have to have an exception for i.e. netsplits, where there are necessarily many join/parts, often by unregistered users.

Badword protection

#ubuntu is a family friendly channel and should remain so. Bad words (list to be determined) should trigger one or a few warnings followed by a kick. People will receive points (not credits, but negative points) for bad words. Each known bad word (well, regex) has a score, specific scores will trigger actions. Score for people will be lowered automatically after predetermined times.

Example:

f*ck gets you one point f*ckf*ce gets you three (+1 for f*ck)

4 points trigger a kick, 8 points a temp ban and 16 a permanent ban (without lowering of score).

Bot abuse protection

Both Ubugtu and ubotu have abuse protection, although for ubotu it is less restrictive. Ubugtu should notice intensive bot (ab)usage and warn people not to abuse the bots. Possibly followed by a kick after continued abuse.

Abuse notification and logging

All actions taken by Ubugtu should be logged and the log should be publicly available on the website (maybe the unauthorized edits too?). The actions also should be relayed to #ubuntu-ops

UbugtuChannelGuard (last edited 2008-08-06 16:19:53 by localhost)