4
I had that problem on chronolabs.coop, there is a couple of options you can do for one you can use Profile 1.76 to add a validation field that will lock the submit button on the registration form until the form is validated, you then prepare a table of answeres for a question you ask on the form. I orginally did this where you would have to know an existing email address, but this didnt work I still got spam signup.
What they are that are signing up is
Captcha Sweat shops these prodominately operate out of China and places like india where people are paid less than $1 USD a day to set up accounts on websites for a bot attack later on. Stop forum spam doesn't cover this type of spammer / harvestor. But i find it is in
Project Honeypot.
Xortify 3.04 (download) is completely bug free if you would like to give it a go, if you want we can set up a netherlands cloud for it at
http://xortify.nlxoops.nl if you like which means for that intial query of 1 IP address every 24 hours, or 1 IP address, username and/or email address every 24 hours or whatever you set it for, then you can point the xortify in the nl at xortify.nlxoops.org instead of having to wait for the europe -> australia pipe to clear as
DNS Resolution.
But i warn you xortify is sitting on a Beast it gets currently over 69 million api hits a month. I found like many others did including Ivan that xortify solves all the other problems that protector doesn't cover for including captcha sweat shops..
So try it out
http://xortify.com to get the client for XOOPS. It is quiet likely that the
API key in protector will be disabled talking to paul from SFS soon as it offers not
anti bot or
IP Cache querying system like
built into the xortify cloud or anything else that has allowed Xortify to query for SFS in over 55k queries an hour.
The problem with it being built into protector is you are all using the Same
API Key, that as paul from Stop Forum Spam who is on my skype told me should never be published with OS otherwise he will close it down when i was talking to them about the load and setting up a pipe between our machines while writting xortify. See the API it gets abused by people trying to DOS Attack and other stuff on his API on his system. It is only a matter of time till that silly idea of duplicating the wheel in protector from xortify, is disabled and then income the spammers again.
I also find that i intermitently get a WSOD when the
API query in protector fails cause it isn't in a
try {} catch () {} clause in php as well as some of the anti crash system put into and well researched by myself over the SDLC of Xortify.
Mamba: We need to set up http://xortify.xoops.org as well at some point as it is included with 2.6 as per my branch task. The 2.6.0 version is already written, just so people have options.