View Issue Details

IDProjectCategoryView StatusLast Update
0004149unrealircdpublic2012-12-15 20:24
Reporterdboyz Assigned Tosyzop  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionno change required 
Product Version3.2.10-rc1 
Summary0004149: [Feature Request:] New (better?) mechanism to combat part/quit reason flood
DescriptionAs of now, channel ops and ircops have no direct way of combating part/quit reason flood without modifying the config file.

I would like to suggest unrealircd to implement a channel mode (or anything more efficient) that allows ircops and channel ops to, at any time, replace part/quit reason with the static part/quit reason set in the config file.

Currently (as available in the official documentation) the part/quit reason is handled separately in the config (set::anti-spam-quit-message-time, set::static-quit and set::static-part)

Take note that flood, including part/quit reason flood can happen at any time. I find it unreasonable to leave the part/quit reason as a static message because of the probability of people misusing it.

This feature request is closely related to 0004006 but with different suggestions.
3rd party modules

Activities

katsklaw

2012-12-12 20:05

reporter   ~0017255

1> there is no such thing as a "quit reason flood".
2> There is such a thing as join/part flood and it is controlled via existing channel modes.
3> There is connection throttling already built in.
4> As mentioned, parts/quits do not need to be handled on the fly.
5> Bug 4006 is a anti-spam enhancement by disallowing user defined messages from unidentified users (umode -r), not a way to micromanage whom can display quit/part messages.

syzop

2012-12-15 20:23

administrator   ~0017256

Sorry, but using a channel mode just for the sake of not displaying (original) quit reasons is really a waste IMO.
This won't be a core feature, but feel free to make a 3rd party module and submit to modules.unrealircd.org

Issue History

Date Modified Username Field Change
2012-12-10 12:39 dboyz New Issue
2012-12-12 20:05 katsklaw Note Added: 0017255
2012-12-15 20:23 syzop Note Added: 0017256
2012-12-15 20:23 syzop Status new => closed
2012-12-15 20:24 syzop Assigned To => syzop
2012-12-15 20:24 syzop Resolution open => no change required