🆕 Software Suggestion | Privacy Pass #2087
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#2087
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Basic Information
Name: Privacy Pass
Category: Browser extensions
URL: https://privacypass.github.io/ (Open source)
Description
The Privacy Pass extension implements the Privacy Pass protocol for providing a private authentication mechanism during web browsing. Privacy Pass is currently supported by Cloudflare (And hCaptcha) to allow users to redeem validly signed tokens instead of completing CAPTCHA solutions.
Why I am making the suggestion
It works quite well, improves privacy, and avoids using too many captchas.
(Especially it is useful if you browse with tor browser)
My connection with the software
No, I am just a user using the extension.
Are there that many captchas to need it with onion-location and their other solution being things?
In tor navigation, there are many captcha because almost all websites use cloudflare (And cloudflare forces many tor users to complete a captcha), with this complement, the captcha protocol is improved.
It works for tor, but also for normal navigation.
It's not just limited to tor.
In addition to this, it is not necessary to fill in so many captcha since they give you "trust tickets" every time you solve a captcha.
Note: The "Trusted Tickets" I mention are actually tokens.
Still I think using this with Tor defeats the purpose, right? It's not like installing uBlock which at least is used by anyone using Tails, here the fingerprint would be close to unique.
Fingerprinting is pretty complicated. But this is not only applicable to Tor users, but hardened FF users too.
There is a lot of work being put into this; it's becoming more than just a browser extension. I can look into it more so, but it already seems to be recommendable to hardened FF users, who also receive large amounts of CAPTCHAs. It's really just a convenience feature while preserving your privacy.