See? Jim's "we're under attack" is completely ignoring why his system sucks so bad. People PERCEIVE that the system is completely broken. That's because it IS. If your workaround is to completely ignore the retardation you have to go through on a WEBSITE, then I don't know what else to tell you. Shit STINKS and if outsiders are attacking you had ought to thank them for red teaming this crap because it is fragile as fuck error messages that SAY NOTHING even when working! Error: '' it worked, this time maybe.
No amount of attacks will ever convince a retard who refuses to address, fix, and make life better for his users if he never ADMITS THE DUMB. He's only had years to make sure that the working default path is not dumb as shit. Been on any other chans ever? They don't do this error: worked? no, 502. error: error: error: error: maybe worked error anyway: nothing. update and hope to god the post got there because it doesn't actually update unless you click update. TRY AGAIN.
That's WITHOUT captcha. Broken as fuuuuuck. And not actually limiting anything? Come on! This is Jim's code! He has to fix it! It likely was changed anyway and therefore broke. I mean, that's obvious. Lurker bug? Nah, because to lurk within a codebase, it implies that normally isn't buggy as fuck.