The problem isn't the normal use by all of us, but robot scraping massively increased last year (from Google, Bing are there, but also thousands of unrelated residential/global IPS).

To get an idea what happened, daily requests suddenly rose from 77,349 on July 10 to 320,784 on July 22, which you can calculate as 3 requests per second if it was even.. but as it isn't even, some single seconds have hundreds of simultaneous requests.

A lot of this I expect is the increase in AI infrastructure around the world. They suddenly decided our content is 'on their radar'.

I cannot simply increase the threshhold, as that would overload the server CPU/memory.

The message usually only appears for few seconds, so if you see the busy message, just wait a few seconds and click refresh.

If the busy error happens whilst you are posting and clicking 'Send', even if you don't make a copy-paste backup of the text, remember that unlike TMF, at Shrewd'm the go-back button is safe to get back to your post and click 'Send' again.

Don't worry, I'm on it. It requires work both at the application layer (deeper caching, etc), plus changing configuration of the server protection software (blocking far more, though not all, traditional and AI robots).

- Manlobbi