challenge-bypass-extension VS Frontpage

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/

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

Terms of service are generally pretty shitty, yes. But this is egregiously shitty.

https://tosdr.org/ is a good site to compare. Any service over Grade E (Spotify, Facebook, the usual suspects) is (very likely to be) less bad. DeviantArt for example is a D, and doesn't include waiving your moral rights among some of the other overreach.

Some service terms are actually quite good (DuckDuckGo, Mullvad, off the top of my head). Though these aren't content sharing platforms so it's not really as fair of a comparison.

This is super useful https://tosdr.org/

> Meaningful consent is becoming increasingly difficult for consumers; for instance ...

https://tosdr.org is good for that, why don't Mozilla just contribute to an existing project

I can't give you a complete guide here, but I recommend you go to privacy subreddits or watch relevant Youtube videos for more info. I also recommend sites like privacytools.io and privacyguides.org They contain lists of alternatives and tools. Also check out tosdr.org which contains summaries of the TOS of a ton of sites. Also try email aliases like simplelogin or anonaddy. Use burner emails for throwaways if possible emailnator.com or tempail.com . Try to use as many open-source applications as possible. You can even self-host certain things.

I think what you're looking for is TOSDR (Terms of Service, Didn't Read): https://tosdr.org

It's been going for several years and has very thorough analysis of various ToS, done by volunteers who are often legal professionals.