I did a search for Searchspam...and didn't find a thing (except for !betatesting thread)
So..Here is my question...Since there seems to be a hole lot of hubs going down becouse of searchspamming (some jackass just trying to have fun I suppose)
is there anyway to make an AntiSearchspam script??
A script who only allows 1search in 3 minutes??I know its not very nice to all the honest people but whattha heck are you supposed to do?
So please........please please....Can someone just make this script for me??And make a working one to?? :]
A better solution would to be to find out how these hubs are being search spammed (I believe PtokaX only allows a search every 5 seconds?). The offender may be creating multiple connections to the targeted hub and then cycling through each seperate connection to spam the hub. A way to prevent this would be to only allow a search from the same IP every 1 second (obviously the rule for the same person every 5 seconds still applies).
-NotRabidWombat
i think the majority of searchspam comes from the way the client is setup, if i remember correctly, from the DC++ board, its generated from the client searching for alternates i believe that was the case, i in my own hub was searchspamming with this setup.
searching for alternatives, is one thing, yup.
but with searchspamming I guess those guys only search for like "." or a's single letters that way.
you let out one searchspam, and the all users will reply over the hub well only when the searcher was passive.
other thing is what about a getnicklist spam or myinfo spam.
Haven't tried it, out, but I know the hub sends a new myinfo to all users when the new is different from the old one. and getnicklist.. is even mor intense I think.
But from what I know, it actually never took down a hub, the hub just starts to lag a lot.
so maybe best is onl allow 1-3 same ip's in a hub. that should do the search spam thing when using ptokax.
Allowing only 1-3 ips is not very pratical. Many college students and professionals are on a subnet behind the same IP.
From what you described, the best solution would be to require the search have at least X number of characters or match some sort of rule depending on the severity of the situation.
-NotRabidWombat