That's a cool idea. Janitors should not be mods, but after around 5 banrequests you know something is up.

Agreed. We've been getting a lot of crapfloods and sagebombs in /co/ of late. I get the feeling it's probably the same people doing it over and over again, since it's usually the same types of threads, so anything to stop them for a few minutes would be greatly appreciated.

Agreed, this would be awesome.

>>1214

You shouldn't be ban requesting the same IP that many times to begin with.
If an IP already has a ban request on it, you really don't need to make another.
The fact that people ban request the same IP 55 times is one of the reasons that the ban requests keep getting so backlogged.

If someone's spamming or invading, ban requesting him that many more times isn't going to get you help any faster- in fact, it'll probably just make it slower. Yelling for a mod in IRC is really the only effective way to deal with something that needs such immediate attention.

>>1218
Though this is true, sometimes it is difficult to tell whether or not a spammer is from the same IP. It is quicker to ban request the poster (and have that post removed) via the extension than to report the post, and distinguish it is as a unique IP address.

I think what also should be added is a mass report function. It should be much like how you can delete multiple posts using the password box on the bottom. As far as I know, reports can only be done for one post at a time even if multiple posts are selected. It will only select the first post that is selected and bring up a confirmation window for that particular post.

Having this feature would be helpful for me personally and would streamline my workflow during heavy posting periods.

>>1219
What you should be doing in the case of a spammer like that is to get the attention of a mod. Janitors are not properly equipped to deal with that kind of situation. Ban requesting every single post of an invasion doesn't help anything.

>>1220
I am suggesting that a feature be implemented so I can ban request UNIQUE IPs and thus not just "ban requesting every post of an invasion."

>>1221
Even then, though, ban requesting isn't an ideal way to deal with an invasion since it depends too heavily on mods actually looking at the ban requests. If they're not, ban requesting would be no better at stopping an invasion than deleting would be.

Janitors just aren't equipped to deal with invasions and the like, and I'm not sure we're meant to be. Getting the attention of someone who IS equipped to deal with it is about the most effective strategy we have.

>>1222
>Even then, though, ban requesting isn't an ideal way to deal with an invasion since it depends too heavily on mods actually looking at the ban requests. If they're not, ban requesting would be no better at stopping an invasion than deleting would be.
>Janitors just aren't equipped to deal with invasions and the like, and I'm not sure we're meant to be. Getting the attention of someone who IS equipped to deal with it is about the most effective strategy we have.

Ding ding ding!

Flag the board and delete the spam. Stop issuing tons ban requests--it does absolutely nothing if nobody is active, except flood the queue with junk. The only persons equipped to address a large-scale flood are MrVacBob and myself.

>>1216
>I get the feeling it's probably the same people doing it over and over again, since it's usually the same types of threads, so anything to stop them for a few minutes would be greatly appreciated.

What? The vast majority of these floods are done by bots/"viruses". The mods, for the most part, are just as ineffective against these types of attacks.

>>1223
>Flag the board and delete the spam.

Yeah, I cringe when I see 600 ban requests on one IP. My fellow janitor brethren need to calm down on the request ban button in my opinion.

>>1227
>My fellow janitor brethren need to calm down on the request ban button in my opinion.

YEP.