Yet Another Anon Bot Screwing Up The Forums

Once again the JU forums are being trashed by some anon that appears to be another forum trashing bot. This one is called Test. There must be some way to block these asshats to keep them from trashing the forums. I have been making sure that all of my articles are available for comments by registered users only, but there are a lot who don't for various reasons. This crap is damned annoying.

The asshats responsible for this sort of crap should be publicly horsewhipped before being locked in a portable toilet and set on fire.
4,056 views 11 replies
Reply #1 Top
It's crap like that, that has us thinking about disallowing anonymous posting period.
Reply #2 Top
Reply #1
It's crap like that, that has us thinking about disallowing anonymous posting period.


Wouldn't hurt my feelings any.
Reply #3 Top
publicly horsewhipped before being locked in a portable toilet and set on fire.


That has got to be one of the funniest and most demeaning torture and death scenarios ever.

~Zoo
Reply #4 Top
"It's crap like that, that has us thinking about disallowing anonymous posting period."


I've suggested it more times than I can remember. I think there is some baby that will be lost with the bathwater, but I also think it would remove an almost invincible tool that trolls and the exiled use to continue to harass the site.
Reply #5 Top
What are you referring too?

Do you actually mean bot when you say "bot", if so why not just use the standard anti bot blocker..... alpha numeric graphics that must be typed by anons to post a reply. Its all very simply stuff.


Reply #6 Top
Do you actually mean bot when you say "bot"


I really don't understand your question as one wouldn't actually use the word bot unless they meant bot. I never say shoelaces when I mean to order coffee either.

Some sort of verification would be a good idea to block the bots, but it still wouldn't stop the actual live anon trolls who also like to screw up the forums.
Reply #7 Top



It's crap like that, that has us thinking about disallowing anonymous posting period


YAY!!!!!!!!!!!!!!!!!! I'm all for that. It'd put an end to the eejits who are exiled yet who keep coming back and posting as anon users, not to mention the trolls who hide under JU's rickety bridges.

(the bridge reference has to do with a fairytale my dad used to tell me about Billy-Goat Gruff who trip-trapped his way across a rickety bridge and then butted the troll who lived beneath said bridge to kingdom come when he complained. I don't know if you guys have the same fairytale over here or not.....)

Reply #8 Top

I've suggested it more times than I can remember. I think there is some baby that will be lost with the bathwater, but I also think it would remove an almost invincible tool that trolls and the exiled use to continue to harass the site.

Maybe just one of those holographic words that needs to be spelled?  Some anons join and are pretty good members.  I would hate to eliminate those babies with the sewer water, but maybe ZOOMBA can work some magic?

Reply #9 Top
It's going to be a consideration for the JU rewrite coming up.  Stronger access controls, eliminating spam etc...

Maybe something like "type the weird obscured word in the image above" as a way to block bots.  But we get a fair number of manual-spammers too, and nothing short of blocking anon comments will stop that.
Reply #10 Top
I never say shoelaces when I mean to order coffee either.


Not unless you're in the habit of putting your foot in your mouth.

I requested clarification because... it was unclear.... i felt there might have been more too it than just bots. As it turns out there was. Bots are but one half the problem.



Reply #11 Top
But we get a fair number of manual-spammers too, and nothing short of blocking anon comments will stop that.


define maxAnonPostingLimit = x
define thisAnonPosterPostCount
define coolDownPeriod = y (in mins)

thisAnonPosterPostCount = getThisAnonPosterPostCountSince(anonIpAddress, (datetime.now-coolDownPeriod))

If thisAnonPosterPostCount >= maxAnonPostingLimit Then
response.redirect("buggeroff.aspx")
End If


No need for wholesale blocking, you can provide a more granular level of control than that.