Since I found a working and screen reader-accessible PoW-based captcha which is super easy to implement on a site and people have been telling me to switch from RecaptchaV3 for years, I had a reason to write Verity, a tiny and super fast server for Altcha. Feel free to check it out and contribute should you wish to. This is currently the most feature-complete and secure implementation of an Altcha server to date to my knowledge. #captcha #altcha #free

Pitermach reshared this.

in reply to Erion

proof of work, hang on, so the same tech blockchains use? how would that stop bots though? not that I care about captchas at all, they could go burn in a fire for all I care, but for those who do...why is this useful? I hate hcaptcha, rcaptcha and so on with a passion, which makes me also hate all captchas, but if this one is actually better and protects against some kind of bots, that's good I suppose
in reply to the esoteric programmer

If you host websites or services, captchas are there to stop spam. The problem is that they are not user friendly at all. PoW-based captchas do the work for you, all you need to do is check a checkbox and wait until your pc finds the solution. Depending on the complexity, which usually rises the more requests you send, in a normal case the solution is found in less than two seconds. There's a demo captcha on altcha.org
This entry was edited (1 month ago)
in reply to Bichinho de matar com cuspe

Thank you very much for your kind words. Yes, client integration is available at altcha.org/captcha/, which is why I decided to not reiterate what's there already, including integration examples for popular frameworks.

For example, the non-floating UI integration goes like this:

  • A developer adds the Altcha JS module, either via import or a script tag.
  • A simple altcha-widget tag defines where the captcha is in a form, as well as defines properties, e.g. where to reach the Altcha server. This is the challenge URL (/api/v1/challenge) in the case of Verity.
  • A user checks a checkbox to initiate acquiring a challenge.
  • The Altcha JS module fetches a challenge from the challenge URL and begins working on the challenge. When a solution is found, the checkbox is checked, screen readers are notified. The form can be submitted now.
  • Upon form submission, the server checks if the form contains an altcha field, which is defined by the Altcha module. The name of the field can be changed. If yes, the server sends a post request to the verify endpoint of the Altcha server (/api/v1/challenge/verify in the case of Verity).
  • If the verification is successful (code 200 and the message is OK in the case of Verity), the submission is valid. If the altcha field is empty or verification is invalid, the submission should be rejected.

This is very similar to the way Recaptcha works, so quite often creating a drop-in replacement is straight forward.

Hope this helps!

This entry was edited (1 month ago)