also: Google Cloud Fraud Defence is just WEI repackaged - https://news.ycombinator.com/item?id=48063199
Hacker News
Latest
Meta Shuts Down End-to-End Encryption for Instagram Messaging
2026-05-08 @ 21:47:47Points: 229Comments: 135
Non-determinism is an issue with patching CVEs
2026-05-08 @ 21:23:07Points: 44Comments: 12
Mux (YC W16) Is Hiring
2026-05-08 @ 21:02:32Points: 1
When is your birthday? The math behind hash collisions
2026-05-08 @ 20:18:39Points: 36Comments: 6
You gave me a u32. I gave you root. (io_uring ZCRX freelist LPE)
2026-05-08 @ 19:40:39Points: 168Comments: 96
My first in-prod corrupted hard drive problem
2026-05-08 @ 19:35:36Points: 41Comments: 28
Google broke reCAPTCHA for de-googled Android users
2026-05-08 @ 18:45:58Points: 859Comments: 285
Teaching Claude Why
2026-05-08 @ 17:59:41Points: 129Comments: 64
AI is breaking two vulnerability cultures
2026-05-08 @ 17:55:08Points: 304Comments: 127
How do I deal with memory leaks? (2022)
2026-05-08 @ 17:06:59Points: 81Comments: 67
The React2Shell Story
2026-05-08 @ 16:39:48Points: 109Comments: 5
Cartoon Network Flash Games
2026-05-08 @ 16:29:52Points: 314Comments: 102
Can LLMs model real-world systems in TLA+?
2026-05-08 @ 16:21:56Points: 64Comments: 9
Serving a website on a Raspberry Pi Zero running in RAM
2026-05-08 @ 15:10:35Points: 204Comments: 88
PC Engine CPU
2026-05-08 @ 14:14:31Points: 137Comments: 57
Human typing habits and token counts
2026-05-08 @ 13:12:41Points: 20Comments: 4
Poland is now among the 20 largest economies
2026-05-08 @ 12:30:05Points: 949Comments: 753
US Government releases first batch of UAP documents and videos
2026-05-08 @ 12:10:25Points: 257Comments: 426
David Attenborough's 100th Birthday
2026-05-08 @ 12:03:26Points: 555Comments: 106
An Introduction to Meshtastic
2026-05-08 @ 11:22:11Points: 395Comments: 154
Ask HN: We just had an actual UUID v4 collision...
2026-05-08 @ 07:57:14Points: 344Comments: 274
This morning, our database flagged a duplicate UUID (v4). I checked, thinking it may have been a double-insert bug or something, but no.
The original UUID was from a record added in 2025 (about a year ago), and today the system inserted a new document with a fresh UUIDv4 and it came up with the exact same one:
b6133fd6-70fe-4fe3-bed6-8ca8fc9386cd
We're using this: https://www.npmjs.com/package/uuid
I thought this is technically impossible, and it will never happen, and since we're not modifying the UUIDs in any way, I really wonder how that.... is possible!? We're literally only calling:
import { v4 as uuidv4 } from "uuid";
const document_id = uuidv4();
... and then insert into the database, that's it.
Additionally, the database only has about 15.000 records, and now one collision. Statistically... impossible.
Has that ever happened to anyone?! What in the...