Comment

Comment by poyu

It's gotta be something simpler than that. Perhaps there's a database rollback and now they have mismatched ID somewhere. Or perhaps the caching scheme wasn't thought out thoroughly and the caches got delivered to the wrong person. There's literally a million ways things could go wrong, and hash collision is the last thing I'll suspect.
parent poyu 6 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton