challenge-bypass-extension VS adblock-rust

I'd be fine if "ID for the web" was implemented with privacypass https://privacypass.github.io/

https://privacypass.github.io/ should help with Cloudflare verification. Works on Chrome and FireFox.

Cloudflare's Privacy Pass may help here: https://privacypass.github.io/

It should significantly reduce the amount of CAPTCHAs you see in a way that's not terrible for privacy.

For Safari, you can enable Private Access Tokens: https://blog.cloudflare.com/how-to-enable-private-access-tok...

Both of these mechanisms are similar to Google's web DRM proposal in that they rely on external issuers to generate tokens, but unlike Google's attempt they don't guarantee that ad blockers are disabled on pages that try to use tokens.

The author is referring to this standard: https://privacypass.github.io/

Apple uses it for its iCloud Private Relay service. The blind token is used so that Cloudflare can verify that a given device pays for iCloud Private Relay without revealing their identity.

Attestation is when such a blind token is proving the integrity of the software running on the device, not proving arbitrary properties. Privacy Pass could actually enable a fast, semi-decentralized system of anonymizing proxies.

If Apple exposed the “is System Integrity Protection enabled” bit to the web, then that amounts to attestation to me, and yes: Apple can do it whenever it wants, and people want Apple to do it.

Use Privacy Pass then if you don't want to use Chrome. https://privacypass.github.io/

Most hCaptcha and many Cloudflare -> https://privacypass.github.io/

That's weird, I haven't used it recently but will take a look. Looks like you're not the only one having issues though: https://github.com/privacypass/challenge-bypass-extension/issues/389

This wouldn't be at the network level, but there is this amazing extension at the browser level: https://privacypass.github.io/

Brave has written their own (open source) adblock engine (in rust) that is directly integrated into the browser (ie. not an extension, so is not affected by Manifest V3).

https://github.com/brave/adblock-rust

Here is a (somewhat dated) article describing it by the authors:

https://brave.com/improved-ad-blocker-performance/

Brave has its own Rust implementation of an adblocker embedded in the browser: https://github.com/brave/adblock-rust; so it does not embed uBlock Origin (but the filters are mostly compatible)

Disclaimer: I work at Brave but not on the browser.

We support :has currently, which impacts many filters in EL and uBO. Some non-supported filters such as upward() can be manually converted over to use :has instead. The other unsupported procedual filters are a WIP will depend how easy/hard they are implement. No ETA, but have opened a ticket https://github.com/brave/adblock-rust/issues/293

ublock on chromium and brave itself can't use all of the filters in that list: https://github.com/brave/adblock-rust/issues/4

It's open source https://github.com/brave/adblock-rust

I've fixed this in the adblock engine as of https://github.com/brave/adblock-rust/commit/8a755bdb190bb55a3a3acee1e6507085051bdeec, and I'll push to get this patched in 1.47 soon. Thanks for the reports!