this post was submitted on 13 Feb 2025
37 points (91.1% liked)
Privacy
894 readers
40 users here now
Protect your privacy in the digital world
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be nice, civil and no bigotry/prejudice.
- No tankies/alt-right fascists. The former can be tolerated but the latter are banned.
- Stay on topic.
- Don't promote proprietary software.
- No crypto, blockchain, etc.
- No Xitter links. (only allowed when can't fact check any other way, use xcancel)
- If in doubt, read rule 1
Related communities:
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
founded 3 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I find it difficult to wrap my head around how Privacy Pass actually works. It seems pretty involved. Kagi‘s implementor actually explained it over on hackernews, but that‘s only a summary.
Since it‘s an RFC standard, I don’t doubt that it works, but I hope someone smarter than me actually checks Kagi‘s open-sourced client code, which should be enough to ensure anonymity, according to the standard.
I'm with you. I couldn't begin to audit something like that, and this article is lengthy (though some of the handshake graphics are kinda funny). The amount of detail in this, what I assume is a summary, left me a bit lost.