HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bitly
dablooms
C2012–2016
bitly / dablooms · Archived

dablooms

scaling, counting, bloom filter library

Libraries & SDKs
Explore on GitHubRead Hacker News discussions
5Distinct people
6Mentions
0Explicit recommenders
961GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

scaling, counting, bloom filter library

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2012-08-03 16:07:09 UTC to 2016-12-09 16:20:55 UTC.

01232012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC220
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC303
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101

What Hacker News says

6 sources
llimllib·Dec 9, 2016
A good example is for a bloom filter: using sha256 is much too slow for good filter performance, you want something like siphash or some other non-cryptographic hash. Here's a good story of the performance benefits of switching from cryptographic to non-crypto hashes: https://github.com/bitly/dablooms/pull/19 (But I don't recommend you use murmur anymore: https://emboss.github.io/blog/2012/12/14/breaking-murmur-has... (although tbh I could be wrong on this one, not an expert)) (Shameless plug for my bloom filter tutorial https://llimllib.github.io/bloomfilter-tutorial/ )
In SeaHash: Explained
tropicalmug·Oct 28, 2013
Another great Bloom Filter library not mentioned in this article is Bitly's implementation on GitHub[0]. It has the best of both worlds: a C implementation and higher-level wrappers (Golang, PHP, Python, and Common Lisp). If you don't want to play around with a fancier DBMS and really just want the damn filters, I would look here. [0] https://github.com/bitly/dablooms
In Bloom Filters by example
ocharles·Jan 24, 2013
Apparently, exactly 168 days ago, I warned about very similar behavior. Remember when a pull request was submitted with tongue-in-cheek comments and a very lax tone? It was https://github.com/bitly/dablooms/pull/19, to jog your memory. Most people couldn't understand why a select few of us were getting in such a huff about this. As I wrote back then: > I worry about a risk of imitation of this culture, but missing the crucial underlying detail and explanation that's hidden in vmg's writing. I worry reasoning with this people will be difficult because they have trained themselves to have such arrogance in their work. This is just a different symptom of the same problem. The open source community is rapidly changing with things like GitHub, mostly for the better, but people have got to learn to leave their ego's behind. Sadly, now that we h
Read the rest
ave more, and more rapid interaction between people, the more that we risk re-enforcing attitudes like these. There's a feedback loop problem, and we've got to start acting now if we want any hope at fixing it. This tweet is an example of things already going too far, that much is obvious. But how did it happen? I feel these things can only happen because we let them happen. Jumping in after the fact isn't a solution, we just all need to be a little more confident pointing out when social behavior isn't acceptable. I'm not asking everyone to become a vigilante, and it doesn't mean that we're all going to get on. The open source community is a sensitive, valuable community, and there's so much passion about it. I'd rather those who get hurt are hurt because they're (politely) informed their attitude is harmful, rather than letting the feedback loop grow.
In I'm sorry

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.