Limit bot should forward channel/flood logs to hub

[sknake]

[08:33] <usual> Channel flood from farrel -- kicking

Currently this only displays on the leaf bot -- I would like this message displayed on the hub and include which channel. In this case it is my console channel.

[bryan]

It would flood the hub on a drone flood, and make the net ping out.

[bryan]

I didn't close it though, perhaps there is another solution? - A flood
kick bot?
I was going to make a flood kick bot when I got around to adding spam code.

-- 
Bryan

[bryan]

I originally intended the chathub (+c) aka 'chanhub' to handle these
things,
but a good majority of people set either their entire net +c or 5+ bots.

[sknake]

I was just going to use this output for informational purposes to give me a heads up that a channel might be having problems.

I don't really see a change needed other than that -- and i dont like the manual role based idea (+c bots).

I set a bot +c if i trust it and it is stable, typically the +c bot is also the limit bot. Any other +c bot was set for testing or my primary was temporarily down.

[bryan]

Same idea then, I was thinking of using limit bot or voice bot for these
things. But people overset them.
(I know the voice/limit bot needs to be more automated anyway)

I could have the hub tell a bot "You report floods for this channel",
but if it splits or has connection problems, it's the same
problems as limit/voice bots :\... unless I detect that on the hub and
account for it, but it turns into a huge predictive cpu/mem/bw mess,
which is why I haven't done it with auto/voice limit bots yet.

[sknake]

Ohhh -- misunderstand. Voice/limit bots can report flooding as long as they don't flood the net. I was thinking you were going to have only these bots enforce the flood-kick or ban. This is perfectly fine since if a limit bot is split or not present and you're getting flooded then you're not paying attention.

Who needs a heads-up to a flood if you don't have your limit bot in there enforcing flood protection? :)

This feature should be married to a limit bot and not a voice but (albeit they can be the same) since the limit feature is an anti-flood feature.