privacypass-extension

Man, if only the article I had posted had answered those questions. That sure would be nice https://blog.kagi.com/kagi-privacy-pass https://github.com/kagisearch/privacypass-extension https://news.ycombinator.com/item?id=43040521 Yes and yes, since you you apparently aren't capable of reading for yourself -edit- I decided I didn't like the tenor of the comments I made. This tone serves nothing but to degrade the quality of online discourse so I will say this: I don't personally have the technical chops to verify the claims that Kagi is making. And no one should blindly trust the statements of faceless companies. For me personally, the claims, discussion in the linked hacker news post, and the direction of Kagi's economic incentives are enough to satisfy me personally. Nothing says that someone else must be satisfied by that level of evide

Big yikes? Is it not open source? https://github.com/kagisearch/privacypass-extension

[I work at Kagi] The extension is open-source [1], including the Rust code that produces the WASM [2]. You should be able to produce a bit-compatible binary from these repos, and if not, please file a bug! [1] https://github.com/kagisearch/privacypass-extension [2] https://github.com/kagisearch/privacypass-lib/

Implementor here. During the Privacy Pass "issuance" protocol, the client will generate a "message" that the server will process. The output from the server is returned to the client, that further modifies this output to produce the final tokens. The last client modification randomises these tokens in such a way that the server will be unable to identify to what issuance they belong. The very cool thing is that this is the case even if the server tries to misbehave during their phase. This means that users only need to trust the client software, which we open sourced: https://github.com/kagisearch/privacypass-extension Some posters are mentioning blind signatures, and indeed Privacy Pass can utilise these as a building block. To be precise, however, I should mention that for Kagi we use "Privately Verifiable Tokens" (https://www.rfc-edito