Spring RTS Engine

This is basically a concept I have for eliminating spam in #main. I figure no matter how many mods get added there will still be random periods of time with zero mods online.

One solution to the problem is to implement some kind of server side flood protection. This could be done via a ChanServ - type bot (even a modification to Chanserv). The flood protection would work like this: Limit a user to a certain number of lines (15/20 or so) per every 30/40 seconds. If they exceed this limit they get a 10/20/whatever minute mute put on their account. If they then cause themselves to get muted 3 or 4 times in total they will be banned (With a note explaining exactly why).

Before people start arguing that this won't work and that people will find ways around it. I say sure, nothing is perfect. But I have IRC'd for more than ten years. Most of those times using a client that has the same kind of flood protection implemented by default when your an operator in the channel. And I've never seen any channels I've been an op in get flooded (atleast without them getting banned after a short 10 or 20 second spam). The flood protection simply fixes the problem.

Any thoughts to share?

i havent read all your post but

CLIENT SIDE SPAM PROTECTION!!!!

this would be VERY easy to implement and would not require.... any changes server side

there is that stupid bandwidth limit thing on the server but it is so high you have to spam absolutely loads to get banned.

also, if more server site restrictions were introduced i would like to see it only in main or and enable / dissable feature for private channels, i like spamming my own ones

iamacup wrote:CLIENT SIDE SPAM PROTECTION!!!!

I WILL JUST MAKE MY OWN SPAM CLIENT!!!
There are at least two different lobby clients, maybe more will follow and everybody would have to implent this...

knorke wrote:

iamacup wrote:CLIENT SIDE SPAM PROTECTION!!!!

There are at least two different lobby clients, maybe more will follow and everybody would have to implent this...

Very true! I think client side flood protection is more like a band-aid as opposed to an actual solution.

ChanServ side protection would work I guess. I don't have time right now to work on it and since everyone knows java anyway, feel free to write a patch and send it in ... :)

The purpose of client side protection is to block UN-intentional spamming...

basically if you are banned for flooding after, say 32kb of data being streamed to the server from you in 10 seconds, but the client was configured to soft mute you after 16kb or whatever (say, greying out the imput box for 30 seconds with a countdown), then no one could say "I didn't know I was flooding why'd you ban me?" anymore, then only spammers would exceed the server cap and be server banned and have no excuse for their behavior.

Betalord wrote:ChanServ side protection would work I guess. I don't have time right now to work on it and since everyone knows java anyway, feel free to write a patch and send it in ... :)

noone knows delphi and thus the client stays as it is

SinbadEV: You have convinced me of the usefulness of client side flood protection! Ultimately a mixture of the two will be the best solution.