/whois flood protection

By PuNkTuReD on Feb 08, 2010

this is a ircop only snippet,
this will kill a user off of the server if they /whois you too much.

default is 3 in 10 seconds,
but i used an alias so that you can easily edit it to fit your needs.

/*
/whois flood protection (for ircops)
By PuNkTuReD
http://www.sassirc.com

edit the "3" and "10"
example: 3 10
would be 3 /whois's in 10 seconds.
*/
alias max.whois return 3 10
on ^*:snotice:* did a /whois on you.: {
  $iif(!$($+(%,$2,whois),2),set $+(-u,$gettok($max.whois,2,32)) $+(%,$2,whois) 1,inc $+(%,$2,whois) 1)
  if ($($+(%,$2,whois),2) == $gettok($max.whois,1,32)) { unset $($+(%,$2,whois),1) | kill $2 [ /whois abuser - $max.whois in $max.whois.time secs ] }
}

Like Page Follow Author

Comments

SnoooP - Feb 11, 2010

I'm not disputing that,

Respond

PuNkTuReD - Feb 11, 2010

it was requested, so it was made, simple as that.

Respond

SnoooP - Feb 10, 2010

I still don't see how a whois notice flood would bother you. Unless you have something that beeps or bops up. They would probably flood themselves off a server but they even affected you.
Would you consider /chanserv help - a flood? that will display faster than any whois flood, and yet that doesn't affect you remotely.

Respond

Jonesy44 - Feb 10, 2010

sunslayer: i know, i was just being an ass really. But you see what i mean? if you don't want the messages, remove the W usermode as you said.

Respond

napa182 - Feb 09, 2010

or just hide ur net admin status in ur whois useing user modes.
+H-h

Respond

sunslayer - Feb 09, 2010

@jonesy44 there are alot more messages that you receive through snotices, unsetting usermode W stops you from getting the notice if your using UnReal

Respond

Jonesy44 - Feb 09, 2010

If they're taking on the role of oper, they should be prepared to get whois notices. Just because they're suddenly oper doesn't mean users shouldn't be able to check their info.

on ^:snotice::halt

Problem solved.

Respond

Jethro - Feb 09, 2010

I've concluded that some ops are simply paranoid and/or bored...

Respond

SnoooP - Feb 09, 2010

Jethro isn't it annoying to users connecting/disconnecting/nick changes etc. lol..

Respond

napa182 - Feb 09, 2010

another way you could make this :

on ^*:snotice:* did a /whois on you.: {
  .hinc -mu10 whois $2 1
  if ($hget(whois,$2) = 3) { kill $2 [/whois abuser - 3 in 10 secs] }
}

Respond

sunslayer - Feb 09, 2010

@SnoooP on most networks, including private ones, spam of any kind isn't tolerated at all.

Respond

Jethro - Feb 09, 2010

But isn't it as annoying as spamming to see multiple messages of "did a whois on you" from the same person?

I'm not sure about the snotice of whois on you, but I figure every time someone sends you one, you're supposed to see it via the snotice each and every time if I'm correct...

Respond

SnoooP - Feb 09, 2010

A chan flood and a whois flood are different lol, and whoising you repeatedly wont do fuck all to be honest.

Respond

PuNkTuReD - Feb 09, 2010

cheers cheiron
:-)

Respond

Cheiron - Feb 09, 2010

i have had to use this script a few times on one of my networks SnoooP.
i run alot of protection scripts on this network in some of the main channels (80+ user rooms) and we have been subject to alot of bot attacks etc, me more so on a personal level due to being oper so i get targeted to try and boot me out as a prime target, this script has saved my skin a good few times :D
nice work PunkTuReD :)
gets a like and a 10

Respond

PuNkTuReD - Feb 08, 2010

actually this script was a request for someone else, i dont use it.
ive never had a problem with people whois'n me
however some have, so this is what they wanted.

Respond

sunslayer - Feb 08, 2010

In a nutshell, you are abusing your oper status by killing a user for a totally shoot reason, Nice,in any case it is still spam, if someone spammed your channel you would ban them no?

Respond

SnoooP - Feb 08, 2010

Why would you kill a user for whoising you? that is probably one of the worst things a oper could do. Whois 'floods' will not effect you, unless you have some stupid script which notifies you and if yo do have protection on that instead.
In a nutshell, you are abusing your oper status by killing a user for a totally bullshit reason, Nice, I would like to visit your network.

Respond