When is your birthday? The math behind hash collisions
denismenace
36 points
6 comments
May 08, 2026
Related Discussions
Found 5 related stories in 79.6ms across 8,303 title embeddings via pgvector HNSW
- Ask HN: We just had an actual UUID v4 collision... mittermayr · 343 pts · May 08, 2026 · 52% similar
- We broke 92% of SHA-256 – you should start to migrate from it logicallee · 60 pts · March 27, 2026 · 44% similar
- Quantum computing bombshells that are not April Fools Strilanc · 103 pts · April 02, 2026 · 41% similar
- A cryptography engineer's perspective on quantum computing timelines thadt · 412 pts · April 06, 2026 · 39% similar
- Only 17% of all 64-bit Integers are products of two 32-bit integers chmaynard · 12 pts · May 22, 2026 · 38% similar
Discussion Highlights (5 comments)
pablowegw
And what are the odds of your birthday being exactly at the center of the (non-leap) year? That's my B'day. Cool!
ChrisArchitect
Related today: Ask HN: We just had an actual UUID v4 collision... https://news.ycombinator.com/item?id=48060054
pedrosbmartins
> What is the probability that you are sharing the same birthday with people around you? > What if I told you that in a room with only 23 people there’s already a 50% chance for two of them to have matching birthdays? I guess it's the subject shift from _you_ to _any two people from a group_ that creates the surprise in the birthday paradox. You definitely need way more than 23 randomly sampled people to get to a high probability that _you_ specifically share a birthday with one of them, and the result does not contradict that notion.
rmunn
> What is the probability that you are sharing the same birthday with people around you? If you're a twin and your twin sibling is standing next to you, nearly 100%. But not exactly 100%: there have been cases of twins born on either side of midnight ending up with birthdays that differ by a day. (I don't personally know of any twins born on either side of midnight between Dec 31st and Jan 1st, who would then have different calendar years in their birthdays, but odds are very good that it has happened at least once in human history).
aidenn0
This is also an easy way to detect RNGs that are not truncated (i.e. return the entire state (or any 1-to-1 permutation of their entire state): https://www.pcg-random.org/posts/birthday-test.html Example: Any RNG with a period 2**32 that can output every 32-bit value at least once must have zero collisions for the first 2**32 outputs, but we would expect to see about 100 collisions after just 200k outputs.