It’s nice to see that someone is attempting to address the issue of form spam, but is reCapture really the way to go? I know it’s great business for Google because it allows them to add even more tracking code onto web users, but ultimately, it’s not the best defence against spam - particularly now that it is without a challenge. Machine learning (which is what invisible reCapture uses) means that determined spammers will come up with machine generated bypass methods.
I feel a better thing to develop would be a new form bric that can included hidden fields which can be set to pre-filled values or must remain empty. There should also be an option to direct forms to external form scripts, many of which now have some fairly nifty spam detection.
That said, I have to admit, the only spam received from the Blocs form script comes from the manual form-fillers sitting in front of a computer screen. Spam-Bots don’t usually get very far with a Blocs form because the email address is well hidden and most spam bots harvest email addresses.
On the rare occasion I’ve received spam from a Blocs form, it only inconveniences me - the form script doesn’t appear too susceptible to acting as a spam gateway which could affect thousands of other people.
To use a real belt and braces method of dealing with the manual spammers (which is where the real problem lies with website forms) is to have the form direct to a cloaked email address before being forwarded to a real email. By doing this, if the volume of spam becomes a real problem, just change the cloaked email address on the website form and delete the old one.
Anyway, I’m sure some may find it useful, but I’m wondering how many Blocs websites have been badly affected by spam?