NHacker Next
- new
- past
- show
- ask
- show
- jobs
- submit
login
In smhasher I'll add a CollisionProver soon, which reverses each hash and runs it through a solver for a couple of minutes to find the likelyness of collisions automatically. Which is relevant if you use them for only a couple of bits in a hash table.
This website is ridiculous.
Claude Design you think?
Seems likely. Lot of web design looking like this with this font suggests LLM assisted design to me.
[dead]
One of my favorite niches for hashing is in a/b testing where you expect and want collisions, particularly in a deterministic way.
So "pinning" a byte just makes it get listed on one random line? And it doesn't show anything about how the collision happens in the rounds, it's just the two inputs rendered in ~ultra fancy wobble vision~ and the final hash?
Yes. And most of the examples don’t actually collide. They just have the same intermediate result at some point in the hashing process, but the final hash is different.
Rendered at 06:25:50 GMT+0000 (Coordinated Universal Time) with Vercel.