You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I use an inspircd network and sometimes the server kicks me because of flooding, which then has a painful intersection with +J (or as I lovingly call it "twat mode").
It seems to be a common pain point, so I was thinking, instead of kicking people for flooding which is intrusive anyway... why not just block their messages after the configured threshold? Most intersections with +f are not from bots, but legitimate participants, especially if it's misconfigured.
@SaberUK was talking about this the other day, I think. Also I noticed #499 but it seems like a dead issue, so I opened this one up.
The text was updated successfully, but these errors were encountered:
So I use an inspircd network and sometimes the server kicks me because of flooding, which then has a painful intersection with
+J
(or as I lovingly call it "twat mode").It seems to be a common pain point, so I was thinking, instead of kicking people for flooding which is intrusive anyway... why not just block their messages after the configured threshold? Most intersections with
+f
are not from bots, but legitimate participants, especially if it's misconfigured.@SaberUK was talking about this the other day, I think. Also I noticed #499 but it seems like a dead issue, so I opened this one up.
The text was updated successfully, but these errors were encountered: