btw no, cap does not contribute to any "fed botnet". you can build the WASM binaries yourself and compare the hashes. added a clarification about that to the docs.

> Also users may be at a disadvantage as JS crypto would not be optimized for PoW (for example lack parallel crypto capabilities or context switching between calls).

JS crypto is only used as a fallback, Rust WASM is used for solving.

Yes, the code is open-source for you to check

Cap does not send any of the calculated hashes ANYWHERE, the white paper just details a bit how proof-of-work works and I thought that it would be interesting to share.

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 something like this is a hard sell.

> a blue hat is typically associated with law enforcement in the US

what it's literally just the default emoji for cap

> lack of acknowledgement on your site (until now)

i've added a note

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

feel free to make a pr to add a worker, currently not my first priority tho

> how much more CO2 this is going to produce extremely minimal emissions, you're only solving a small cryptographic challenge after all.

Not at scale, however. Like another comment said, this is going to turn out like cryptocurrencies.

(I really couldn't care less about the climate debate, but waste is waste.)

even at a huge scale the emissions are still extremely small.

i wrote a bit about it here: https://capjs.js.org/guide/effectiveness.html

ahh, that makes sense, thanks

I do think that calling this a CAPTCHA when it's not actually intended to distinguish humans from computers is a bit misleading, but I can see why you would do that

scrapers usually don't render a webpage, else their scraping wouldn't be efficient at all.

Is that still true? There are so many SPAs out there now that if I were to create a web spider today, I would plan to just render a lot of the pages in a browser rather than fight the status quo. Efficiency wouldn't be my top concern.

That’s bullshit

yeah i also recommend trying out the invisible mode

anubis is more like Cap's checkpoint, but still the implementation is very different.