If that’s the case, how do you validate that what is blocked is actually spam? Seems there should at least be an option to store the “spam” into the database, marked as spam, so that an administrator can properly verify.
Also, this plugin blocks spam by generating a “password” for an anonymous user to copy & paste to validate that they are human. So, how does that stop someone that scripts a desktop browser to post spam? Or someone that scripts cURL to post spam? It seems all they would have to do is set the script to pull the “password” from one field, into another, correct?
