0002108: flood feature suggestions - UnrealIRCd Bug Tracker

ID	Project	Category	View Status	Date Submitted	Last Update

0002108	unreal	ircd	public	2004-10-03 21:50	2007-04-27 06:21

Reporter	White_Magic	Assigned To
Priority	normal	Severity	tweak	Reproducibility	N/A
Status	closed	Resolution	wont fix

Summary	0002108: flood feature suggestions
Description	would it be possible to add the following chanmodes into the flood feature settings to be used.. +T = to be used for message/notice to stop notice floods rther that using +M or +m. +V = to be used for joins when setting +i so that eggy bots / flooders who managed to get ops cant /invite the bots to flood +k = to be used for joins so unregistered ops or away ops can gain access to the channel with the key (incase they dont have umode +r on). also could it set mode than 1 mode.. ie -> +f [10m#MT2]:10 or +f [5j#iV2,3k#K1]:8 also with using text is it possible to make it set a extended ban like ~q instead of a kick ban? just some ideas and suggestions...
Tags	No tags attached.

3rd party modules

aquanight 2004-10-04 03:03 reporter ~0007867	OK first of all, your +T example doesn't exactly fit too well, because a user can't /notice anyway when they normally can't speak. Yes I know sometimes errors aren't returned but that's a known issue... For +T to be really useful, you'd have to make a seperate event for it, but since IIRC the flood checker considers notice == text/message, so this increments the m and t counters anyway, so a noticeflood will usually result in the message/text flood stuff tripping. Only reason I can see is if you want a more stringent limit on channel notices, since most sound-capable clients seem to make more noise on those events :-) . Also, your +V suggestion, well this is why you have secureops or similar, because if a eggy bot flooder managed to get ops, guess what? They can just -i/-V (and even -f!!) and let them back in anyway! Now if a flooder got halfop, but not op, it's different, they can only set -i, but if you use +R instead, then they're stuck. However, even if the channel is +M, they can do some damage by voicing their floodbots. In this case, best solution is to just protect your channel from allowing these people to get any privilege leveel of any kind. +k = This would kinda break +f. How would you decide what the key is set to? An op not in the channel would be kinda stuck if a random key was used, and he'd probably be better off identifying and getting back in that way. And if a key was set in the floodstring, well anyone who joins can find out what that key will be, unless you implement it to not show the key to ANYONE. As for ~q, I guess it could work, could even add support the usual unset time thingy. And as for multiple modes, I could imagine a "flood stage" or similar, where the first mode is set, and if the flood continues it moves to the second mode and so forth.

Date Modified	Username	Field	Change
2004-10-03 21:50	White_Magic	New Issue
2004-10-04 03:03	aquanight	Note Added: 0007867
2007-04-27 06:21	~~stskeeps~~	Status	new => closed
2007-04-27 06:21	~~stskeeps~~	Resolution	open => wont fix
2007-05-09 07:28	syzop	Relationship added	related to 0003322