How does this compare to Anubis, another similar PoW based CAPTCHA? Paired with this, and if there is a way to block out DDOS https traffic then we might be able to stop dependence on Cloudflare altogether.
I'd be so happy if the Internet moved away from Cloudflare for Captcha. I got on their "bad list" at one point (for who knows why), and no matter how many times I checked the "I am a human" box their Captcha wouldn't let me through for a few days. I was unable to login to the portal of a product that we pay for. It was such a frustrating experience.
Cap: Lightweight, modern open-source CAPTCHA alternative using proof-of-work
121–125 of 125 posts
Re: Cap: Lightweight, modern open-source CAPTCHA alternative using proof-of-work
#122Earlier quoted context omitted.
added a note saying that to the docs, should hopefully clarify stuff a bit!
In case you weren't aware, a blue hat is typically associated with law enforcement in the US. On its own it'd be no problem, but the logo, the paper, and the comment above correctly pointing out concerns/lack of acknowledgement on your site (until now) really comes off as suspicious. FWIW, I do believe you just made a few unintentional awkward choices instead of being malicious... But a product associated with someth…
what it's literally just the default emoji for cap
> lack of acknowledgement on your site (until now)
i've added a note
Re: Cap: Lightweight, modern open-source CAPTCHA alternative using proof-of-work
#123Earlier quoted context omitted.
2030: to enter the site you must allow us to mine few ethereal on your pc...
You better not show me any ads if you want my system to make some crypto for you then. We’ll, who am I kidding
Re: Cap: Lightweight, modern open-source CAPTCHA alternative using proof-of-work
#124Earlier quoted context omitted.
you can compare the hashes of the wasm lmao the build script is very much public
It's not a good practice to commit binary blobs in a repository. And I don't think it would be difficult to add a prepublish step to your npm packages so that you can remove them. The end user shouldn't need to run the build script and compare hashes whenever the source code changes. Very surprised to get pushback on what I thought was an industry standard lmao