WIP: feat: add cap challenge type - #107
Conversation
This implements native support for Cap. While Cap does offer a reCAPTCHA compatible siteverify endpoint, it requires a different frontend call and, as it's commonly self-hosted, customizable backend URLs. Berghain users should also be encouraged to host the Cap assets by themselves. Signed-off-by: Georg Pfuetzenreuter <mail@georg-pfuetzenreuter.net>
|
So far, this uses the Cap standalone server. |
|
When looking into what Cap does, I think we could even replace the default pow challenge with it |
|
Tho that would mean to port their js backend and stuff to go, which would be also a nice flex |
Is it possible without the captcha part? I would prefer to keep the self-validating POW challenge as default and only have captcha as an optional level ...
Yes this is what I meant above, it would be nice as to avoid having to run another service (and a JS one ...), there are two implementations but they seem to be rather fresh in development. |
As I understood Cap, you can present multiple challenges, one of them being simple POW. Thats why I proposed that.
Yeah, I honstely would just take their JS backend and throw an LLM against it to port to Go, then take the bits and blops we need. |
2 participants
This implements native support for Cap.
While Cap does offer a reCAPTCHA compatible siteverify endpoint, it requires a different frontend call and, as it's commonly self-hosted, customizable backend URLs.
Berghain users should also be encouraged to host the Cap assets by themselves.