<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Invertible Bloom Lookup Tables · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1101.2245/</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/1101.2245/feed.xml" rel="self" type="application/rss+xml" /><item><title>Invertible Bloom Lookup Tables — mentioned by thomasmg</title><link>https://news.ycombinator.com/item?id=43872775</link><guid isPermaLink="false">urn:hackerpapers:mention:1101.2245:43872775</guid><pubDate>Fri, 02 May 2025 17:43:50 GMT</pubDate><description>&lt;p&gt;This is a bit similar to count-min sketch, which can be used to calculate frequencies in a stream. Also interesting are &amp;quot;Invertible Bloom Lookup Tables&amp;quot; (IBLT), https://arxiv.org/pdf/1101.2245 , which allow to add and remove data, and allow to retrieve the remaining data if &amp;quot;little&amp;quot; data remains. That means, it can be used for error correction: all all the _correct_ data (let&amp;#x27;s say 1 GB of correct data) into a 1 MB IBLT. Let&amp;#x27;s say a downloader finds that the checksum doesn&amp;#x27;t match: he can download that 1 MB IBLT, and remove the data from his (invalid) download. What remains is the delta: the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1101.2245/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DS</category></item><item><title>Invertible Bloom Lookup Tables — mentioned by sgentle</title><link>https://news.ycombinator.com/item?id=11289293</link><guid isPermaLink="false">urn:hackerpapers:mention:1101.2245:11289293</guid><pubDate>Tue, 15 Mar 2016 13:08:29 GMT</pubDate><description>&lt;p&gt;I was recently reading about some of the interesting work with invertible bloom filters/invertible bloom lookup tables, eg [0] [1]. There might be either a clever way to exploit IBLTs to to make a low-information query of the data (like &amp;quot;Oblivious Selection from a Table&amp;quot; in [1]), or otherwise there may be a way to use them to more efficiently implement the bloom filter/sharded bloom filter options. My information theory/coding theory is not strong enough to really know, but it might be worth looking into! [0] https://www.ics.uci.edu/~eppstein/pubs/EppGooUye-SIGCOMM-11.... [1]…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1101.2245/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DS</category></item><item><title>Invertible Bloom Lookup Tables — HN submission</title><link>https://news.ycombinator.com/item?id=8244086</link><guid isPermaLink="false">urn:hackerpapers:submission:1101.2245:8244086</guid><pubDate>Fri, 29 Aug 2014 19:18:14 GMT</pubDate><description>&lt;p&gt;Invertible Bloom Lookup Tables (2011)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;92 points; 24 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1101.2245/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.DS</category></item></channel></rss>
