Replace hCaptcha with Altcha #235

[tdruez]

No description provided.

[pombredanne]

@tdruez 👍

• Can we / should we self host the server?
• What could we do to also deploy the same to SCIO, VCIO and FederatedCode?
• You are missing an about file for the library

[tdruez]

Can we / should we self host the server?

Yes, this implementation is self-hosted:

• The challenge is requested on an internal Django view https://github.com/aboutcode-org/dejacode/pull/278/files#diff-b424c7e3ed5fb8826e80974d11a6ce64add98dac9fffdd41d17835015c881de0R52-R66
• The token is validated in the field/form validation https://github.com/aboutcode-org/dejacode/pull/278/files#diff-b424c7e3ed5fb8826e80974d11a6ce64add98dac9fffdd41d17835015c881de0R31-R48

There are no dependencies on an external server and no need for extra accounts or API keys.

---

What could we do to also deploy the same to SCIO, VCIO and FederatedCode?

I'm thinking about packaging this PR content (field and view), once stable, as a Django library, similar to the https://pypi.org/project/django-hcaptcha-field/ we've been using until now.

The implementation in our various apps would be quite simple:

1. Add the AltchaField to your (registration) form:

from django_altcha import AltchaField

class RegistrationForm(forms.Form):
    altcha_token = AltchaField()

2. Add the challenge view to your URLs (only required for the self-hosted mode, the alternative is to provide settings to the external server, URL and API key)

from django_altcha import get_altcha_challenge_view

urlpatterns += [
    path("altcha/", get_altcha_challenge_view, name="get_altcha_challenge"),
]

This should probably be released under MIT to match the current license on the Python lib https://github.com/altcha-org/altcha-lib-py and the JS "Web Component" https://github.com/altcha-org/altcha included in the HTML rendered page.

---

You are missing an about file for the library

Yes, this PR is still in Prototype mode, making sure this approach will work end to end first.
I usually add the .ABOUT files once the set of new libraries, and their versions, are pinned down.

---

@pombredanne Let me know your take on releasing this as a library as suggested above.