<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: fvirdia</title><link>https://news.ycombinator.com/user?id=fvirdia</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 10 Jun 2026 08:18:06 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=fvirdia" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by fvirdia in "Privacy Pass Authentication for Kagi Search"]]></title><description><![CDATA[
<p>I believe you should currently be able to
- create an account under a pseudonymous email address
- pay for a plan using a pseudonymous Bitcoin wallet
- use your login session to generate Privacy Pass tokens
- search with such tokens via the Tor browser on Kagi's .onion domain</p>
]]></description><pubDate>Thu, 13 Feb 2025 21:58:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=43041919</link><dc:creator>fvirdia</dc:creator><comments>https://news.ycombinator.com/item?id=43041919</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43041919</guid></item><item><title><![CDATA[New comment by fvirdia in "Privacy Pass Authentication for Kagi Search"]]></title><description><![CDATA[
<p>Yes, multi-device is definitely not easy. We've played with a few ideas, but it is definitely not a question with an obvious answer. For now, our rate-limiting allows you to use Privacy Pass on a few different devices by having each generate tokens independently. We will see how this goes and listen to user feedback before going back to the drawing board.</p>
]]></description><pubDate>Thu, 13 Feb 2025 21:22:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=43041528</link><dc:creator>fvirdia</dc:creator><comments>https://news.ycombinator.com/item?id=43041528</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43041528</guid></item><item><title><![CDATA[New comment by fvirdia in "Privacy Pass Authentication for Kagi Search"]]></title><description><![CDATA[
<p>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.<p>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: <a href="https://github.com/kagisearch/privacypass-extension">https://github.com/kagisearch/privacypass-extension</a><p>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" (<a href="https://www.rfc-editor.org/rfc/rfc9578.html#name-issuance-protocol-for-priva" rel="nofollow">https://www.rfc-editor.org/rfc/rfc9578.html#name-issuance-pr...</a>) based on "oblivious pseudorandom functions" (OPRFs), which in my personal view are even cooler than blind signatures</p>
]]></description><pubDate>Thu, 13 Feb 2025 20:34:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=43040966</link><dc:creator>fvirdia</dc:creator><comments>https://news.ycombinator.com/item?id=43040966</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43040966</guid></item></channel></rss>