Trying a new Anti-Spam function

[Swede]

We're testing another Anti-Spam function for a week or so. If there are any problems post here or drop me a PM.

[GeoffreyA]

Yesterday, I had a problem posting a WeTransfer link; it said that HTTPS links were forbidden. Today, it worked.

[Barough]

I can edit a post but not making a reply in a ongoing thread. Need to disconnect the VPN to be able to reply/post. This is kinda fucked up imo.

*** Forbidden. Your IP belongs to a high spam risk network. Please, try again without VPN. Anti-Spam by CleanTalk. ***

[filler56789]

From LigH:
I wanted to post new uploads but your new spam filter blocks it.

[Emulgator]

BTW, the few spam posts were easy to spot (for me), easy to report (for everyone) and I guess easy to remove.
Maybe our humane intelligence is well up to the task of keeping our table clean on these few occasions.
(before everybody has to obtain a brand new handled-by-somebody-else's-machine's-intelleventuality passport)
Just my 2 cents.

[Swede]

True. Easy to spot... The problem is that it requires a round-the-clock presence and I'm trying to minimize that. So, just bear with me for a few days while we evaluate this.. If nothing else it's caught over 5000 not-wanted-registrations so far and only 5 false positive posts.

[filler56789]

*** Forbidden. Your IP belongs to a high spam risk network. Anti-Spam by CleanTalk. ***

Yes, your antispam filter clearly and actually sucks.
Time to send it to the garbage can, IMNSHO.

[Swede]

Yeah, it didn't really work the way I wanted so I'm turning it off...

[Snowknight26]

Is this what's causing an expires header with a value way in the past to be sent with each request? This is preventing the browser from caching pages, even when navigating back/forward. Normally if you navigate back you see the (cached) previous page instantly, but now we have to wait for the network request to that previous page to finish again.