These are not useful posts. The problem has been proven to exist, even if it doesn't bite everyone.

It is sufficiently widespread to affect numerous regular posters. (We don't know how many new users it affects because most of them will just give up and go elsewhere.)

Not everyone gets the "blocked" message - some have noticed an automatic redirect, some receive a captcha challenge (and if they provide free labour to Google the message goes through), others get a block screen without a captcha (and the precise text of that message can vary), sometimes there's a completely blank screens with nothing on at all, and so on.

The precise input that triggers the block is somewhat fluid - what works one day may stop working the next. It doesn't require [code] tags to trigger, but it can be related to any of shell/PHP/SQL/JavaScript - which most often occur in code tags - because it's a flawed attempt at security, and those technologies are common attack vectors.

Those unfamiliar with SQL may be unaware that SQL is closer to natural language than other programming languages. Every now and then someone triggers the block with a perfectly normal post containing no code because it just happens to include certain keywords in a certain order.

pizzipie posts a lot of Javascript and frontend code. The filter attacks those most aggressively.

Obviously, that filter should never have been activated. LinuxQuestions should be designed to secure without it, and AFAIK it is. It's ridiculous that the filter still on.

And it's especially ridiculous that it's still on for so long after it's been first reported to be a problem.

Thanks for the continued feedback. Do note that a very *very* small number of requests are impacted as a percentage of requests. That said, I understand it's frustrating when a legitimate request is blocked. I've made some additional changes today that should help.

--jeremy

3 members found this post helpful.

It's not a bit of an over reaction, let's see how you would react to Cloudfare blocking you for hrs/days/weeks/months on end when you have pressing work to attend to and are stuck.His reaction is understandable.