delayed kick by flood filter

[Vrvy]

As I understand, there is a delay of 10 seconds in kicking a user if he is flooding. Would it be possible to somehow set this to 0 seconds?

Users that are flooding can still make a mess in the time that takes for them to be kicked.

regards

[Lapo]

Not for the moment. The reason is that before they are kicked or banned an admin message is sent, so the delay allows them to read it.

[Vrvy]

I will make a filter in an extension then.

[SimpleSquid]

I'm getting the same problem. I was wondering if there is a way around it in this version?

[sstark]

there are setting in the server's config file for flood control.

[SimpleSquid]

Yes I am aware of that; however, there is a 10 second delay as Lapo has mentioned.

[Lapo]

Is the delay a problem? Why?

[SimpleSquid]

The delay is a problem because it takes 10 seconds. During that time people who are spamming will fill up multiple pages of my chat application, before they are kicked.

Let me know if there is a solution within SFS.

Thanks Lapo.

[Lapo]

Those ten seconds are necessary to send an admin message to the client.
If you have problems with people sending too big messages, you could limit the <MaxMsgLen> to lowerv value than the default (4096 = 4Kb)

Additionally you can perform minimal checks on your client side to prevent big messages to spam the chat box.

[SimpleSquid]

Hey Lapo,

I'm not having a problem with big messages; rather, it's small messages that users like to spam very quickly. For instance, they'll fill a page up with the letter "d" before they get kicked.

Anyway to fix this?

[Lapo]

If users log in with name and password ban them by name and also add their email to a black list. This way the next time they will try to recreate an account they won't be able to do it.

If you're allowing guest users you should think of removing this possibility.

[no-one]

just a sugestion but you could block the user from sending more messages once the kick delay starts, and once oyur at it its pretty easy to ad a custom length limit :

Code: Select all


private final static MAX_LENGTH =200;

public void init(){
   StaticObjects.zone.setPubMsgInternalEvent(true);
   StaticObjects.zone.setPrivMsgInternalEvent(true);
   

}
......

public void handleInternalEvent(InternalEventObject event) {
   if(event.getEventName().equalsIgnoreCase(event.EVENT_PUBLIC_MESSAGE)){
         
   String msg = event.getParam("msg");
   User u = (User) event.getObject("user");
   Room r = (Room) event.getObject("room");
         
   if(msg.length()>MAX_LENGTH)
      return;
         
   if(!u.isBeingKicked)
      StaticObjects.helper.dispatchPublicMessage(msg, r, u);
   }
      if(event.getEventName().equalsIgnoreCase(event.EVENT_PRIVATE_MESSAGE)){

         
   String msg = event.getParam("msg");
   User u = (User) event.getObject("user");
   Room r = (Room) event.getObject("room");
   User rc = (User) event.getObject("recipient");
         
   if(msg.length()>MAX_LENGTH)
      return;
         
   if(!u.isBeingKicked)
      StaticObjects.helper.dispatchPrivateMessage(msg, r, u, rc);
   }   
   
      
}

[SimpleSquid]

yeah, thanks for the code. I'll definitely check that out.