Friendly Captcha (another de-G**gle initiative)
-
Day 1 looks promising! I'm used to waking up to at least a handful of spam messages sent from the contact forms. So far, I got none! Will report back tomorrow.
-
@humptydumpty same here!
I also switched on the WP-login captcha but users with a password manager couldn't get in, the entry was too fast So I switched that of again (we hadn't a captcha before and do have Wordfence login control).
-
Day 2 report: No spam from the contact forms yet. I repeat, ZERO spam messages sent so far!
-
@humptydumpty we had day 1: 1 spam email and day 2: 0 spam email
-
Day 3: almost forgot to post today, zero spam all day.
-
@humptydumpty it’s getting boring but same here!
-
@girish strange, it seems there is something changed on their website. It’s not only looking different but I swear there was something like “use our api or host it on your own server” that’s why I created this app wish. It would be great to host “the API” as an app for your own endpoint. However I don’t see such solution anymore, or maybe I don’t look at the right place?
-
@imc67 I think what was opensource was only the libraries and not the server component (I could be wrong). But you are right, there used to a note before - https://web.archive.org/web/20201220025130/https://friendlycaptcha.com/ but it only stated "FriendlyCaptcha is open source allowing you to build out this service yourself."
-
@girish @imc67 Quoting a closed issue on their github...
Hi, after doing a bit of research, I've realized that FriendlyCaptcha isn't entirely open source. Alternatively, do it yourself FriendlyCaptcha is open source allowing you to build out this service yourself. https://friendlycaptcha.com/ Its front-end and algorithms are open source (MIT), the SaaS wrapper around the hosted version is not [yet, I set it as a sponsorship goal], I hope that’s ok. https://codeberg.org/swiso/website/issues/133 I will appreciate if the website makes it clear that some bits are proprietary.
Source: https://github.com/FriendlyCaptcha/friendly-challenge/issues/10
I think that means someone could use a different wrapper for their source code and make it work for Cloudron and elsewhere, right?