Gavin John

> erc223 ~~["ERC-223"](https://github.com/ethereum/eips/issues/223) isn't an official standard. It's not even merged into the EIPs repository.~~ There's https://eips.ethereum.org/EIPS/eip-1363 (which is final and therefore usable in immutable contracts) and there's https://eips.ethereum.org/EIPS/eip-4524. UPDATE...

Yea, I would like to see an EIP-1363 implementation, but a new issue should be created for that.

Not sure if this issue is still active, but how about https://eips.ethereum.org/EIPS/eip-4524?

Wouldn't it be easier for the file to directly specify which files use which licence? SPDX could be used: https://spdx.dev/ids/ Software Package Data Exchange (SPDX)IDs - Software Package Data Exchange...

This is not needed. hCaptcha supports an accessibility system that automatically bypasses captchas for you: https://www.hcaptcha.com/accessibility Edit: Quote from their website > How it works: first, an accessibility user signs...

The accessibility cookie is (supposedly) rate limited. This will (likely) not work.

I still don't understand what's wrong with just bookmarking the HCaptcha accessibility URL. If all else fails, maybe the extension could force-whitelist that 3rd party cookie and automatically refresh it...

> the most this extension will do is to refresh the cookie if you have already signed up. I'd argue that it should probably implement https://github.com/privacypass/challenge-bypass-extension, if only to reduce...

It doesn't work because the privacy pass extension broke their code when they added cloudflare and haven't realized it yet. There's an open PR in their repo that fixes it,...

Assuming the solver solves it 99% of the time, implementing privacy passes will improve that accuracy to 99.91%. I don't see any downside.