<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wally: Batched Private Nearest Neighbor Search at Scale · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2406.06761/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2406.06761/feed.xml" rel="self" type="application/rss+xml" /><item><title>Wally: Batched Private Nearest Neighbor Search at Scale — HN submission</title><link>https://news.ycombinator.com/item?id=42711301</link><guid isPermaLink="false">urn:hackerpapers:submission:2406.06761:42711301</guid><pubDate>Wed, 15 Jan 2025 14:43:06 GMT</pubDate><description>&lt;p&gt;Scalable Private Search with Wally&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2406.06761/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Wally: Batched Private Nearest Neighbor Search at Scale — mentioned by abalone</title><link>https://news.ycombinator.com/item?id=42649648</link><guid isPermaLink="false">urn:hackerpapers:mention:2406.06761:42649648</guid><pubDate>Thu, 09 Jan 2025 20:44:38 GMT</pubDate><description>&lt;p&gt;This has gone a bit under the radar but Apple went and built a private search engine that doesn’t know what you’re searching for. It’s called Wally and it powers queries like caller ID and landmark recognition in photos. * Homomorphic encryption is nothing short of dark magic that makes it impossible for the server to know what you are searching for or what it’s responding with (at considerable greater computational expense). * To make it scale they added differential privacy techniques that generate fake queries from clients to hide which shards are being queried. So rather than always…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2406.06761/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Wally: Batched Private Nearest Neighbor Search at Scale — mentioned by internetter</title><link>https://news.ycombinator.com/item?id=42545756</link><guid isPermaLink="false">urn:hackerpapers:mention:2406.06761:42545756</guid><pubDate>Mon, 30 Dec 2024 02:15:39 GMT</pubDate><description>&lt;p&gt;I don&amp;#x27;t completely understand the maths of how this works, but no, they don&amp;#x27;t. Here&amp;#x27;s a theoretical way I wrote in another comment: &amp;gt; I think they have more efficient ways, but theoretically what you could do is apply each row in your database to this encrypted value, in such a way that the encrypted value becomes the name of the POI of the best match, or otherwise junk is appended (completely changing the encrypted value) Again, the server has not read the encrypted value, it does not know which row won out. Only the client will know when it decrypts the new value. They do something like…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2406.06761/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
