Thibault
Thibault
@fedecarpy apologies for the delay. I'll add some more details on next week.
Thanks @kamilogorek for the review and the merge. Are there information about the release process available? I'd be interested to know when this change would land in the upstream npm...
Thanks @kamilogorek. That's was super fast!
Closing this issue in favor of https://github.com/privacypass/challenge-bypass-extension/issues/400, where a major reshape is being centralised to support IETF version.
The original issue being reported does not happen anymore. Closing this issue. Regarding the changes to the extension allowing it to better signal a challenge has been solved, it's being...
The fact that Cloudflare blocks the request with 403 forbidden is the expected behaviour. This is how the extension always asks for a new challenge. I understand the little updates...
Closing for inactivity
The initial edge service implementation was open sourced in [privacypass/challenge-bypass-server](https://github.com/privacypass/challenge-bypass-server), as you correctly linked to, and armfazh confirmed. There has been no activity after their comment, therefore closing. If this...
While I agree having an open source Workers implementation would be valuable, this is an issue with the origin server, not the extension. The README has been updated in [this...
hCaptcha [announced](https://www.hcaptcha.com/privacy-pass) the end of their support for the legacy Privacy Pass protocol in favor of the IETF version. I'm closing this ticket.