<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>oefrha</author><text>Every day there are at most around a hundred articles that generate any meaningful discussion at all (see past). Let’s say each article takes up &amp;lt;=200 bytes (URL + title + some stats, a very generous limit actually), then one year worth of data is at most ~7 MB. That might be a bit too much but not by far. If you gate submissions by votes&amp;#x2F;comments threshold as a function of time, it’s conceivable to store metadata of all the good discussions on HN within 20 MB or even 10 MB.&lt;p&gt;Chrome and Firefox extensions can request the unlimitedStorage permission, btw. (Chrome has a 5MB default limit, Firefox doesn’t seem to have one.)</text><parent_chain><item><author>joshstrange</author><text>Love the idea, I have thought about this before and the main issue is training my self to click an extension to check. If an icon flashed when there was a HN submission (ideally only if I didn&amp;#x27;t come directly from HN since I already know) it would be way more useful.&lt;p&gt;That said we all know the big issue with that is privacy. I don&amp;#x27;t want an extension sending every url I visit to any service (directly to the API or through some third-party). I&amp;#x27;ve mulled over this issue before and I&amp;#x27;m not sure how much space it would take up to store a list of urls that have been submitted to HN (Maybe keep 1 month plus all submissions that got over 100 upvotes or something) and check against that local list.&lt;p&gt;Then, and only then, when you get a match you can call out to the Algolia API to get the HN url (or store that as well depending on size).&lt;p&gt;I have no idea, off the top of my head, what the storage requirements for this look like but I don&amp;#x27;t think they would be huge. The other issue (which I want to look into the source to see how this handles it) is the stupid social&amp;#x2F;ads tracking params that are added to URLs. Maybe there is a good list of these that you can remove (from both the current URL and the HN submission) so you can see if it&amp;#x27;s the same base URL.</text></item></parent_chain></comment><story><title>Show HN: Find HN threads about the page you&apos;re browsing</title><url>https://github.com/pinoceniccola/what-hn-says-webext</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>relate</author><text>You could allow for errors and use a bloom filter to avoid the space issue:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Bloom_filter&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Bloom_filter&lt;/a&gt;</text><parent_chain><item><author>joshstrange</author><text>Love the idea, I have thought about this before and the main issue is training my self to click an extension to check. If an icon flashed when there was a HN submission (ideally only if I didn&amp;#x27;t come directly from HN since I already know) it would be way more useful.&lt;p&gt;That said we all know the big issue with that is privacy. I don&amp;#x27;t want an extension sending every url I visit to any service (directly to the API or through some third-party). I&amp;#x27;ve mulled over this issue before and I&amp;#x27;m not sure how much space it would take up to store a list of urls that have been submitted to HN (Maybe keep 1 month plus all submissions that got over 100 upvotes or something) and check against that local list.&lt;p&gt;Then, and only then, when you get a match you can call out to the Algolia API to get the HN url (or store that as well depending on size).&lt;p&gt;I have no idea, off the top of my head, what the storage requirements for this look like but I don&amp;#x27;t think they would be huge. The other issue (which I want to look into the source to see how this handles it) is the stupid social&amp;#x2F;ads tracking params that are added to URLs. Maybe there is a good list of these that you can remove (from both the current URL and the HN submission) so you can see if it&amp;#x27;s the same base URL.</text></item></parent_chain></comment><story><title>Show HN: Find HN threads about the page you&apos;re browsing</title><url>https://github.com/pinoceniccola/what-hn-says-webext</url></story>