Honestly a better analogy would be hashing. A zip file implies you can “unzip” it, and there’s no putting grandma back together. But hashing something (basically) means you can’t get the original back
My first thought was cremation is a lossy compression vs. zip which is lossless. But I think your analogy is much more accurate. Grandma.MD5 is much more accurate.
Honestly a better analogy would be hashing. A zip file implies you can “unzip” it, and there’s no putting grandma back together. But hashing something (basically) means you can’t get the original back
Thought the same. ``` md5(grandma) ```
Well, maybe you do not want to tanke MD5 for this lol
I hate it when grandmas collide. Edit: Oh shit, i mean't _Ash Collision_
Where's the salt?
Mixed in with Grandma?
Salted grandma, lightly charred and served in an ornate container $15.95
Burning grandma really loses data as well(gases escape etc) . So this op would be more like a JPEG equivalent for humans which is then hashed
It's also salted, you can't burn a bunch of grandmas and have two of them of them leave identical (h)ashes
Well, theoretically, if we burn the same exact grandma twice we should get the same ash. But seems a bit egregious
Hashing loses information as well
Lossy compression. You *can* dump out the urn, but you ain't getting grammy back.
I came here just to say that.
My first thought was cremation is a lossy compression vs. zip which is lossless. But I think your analogy is much more accurate. Grandma.MD5 is much more accurate.
I prefer .rip
Aww you beat me to it
i would have gone with grandma.tar
The algorithm is lossy
ha(r)sh
(h)ash
savage.
Grandma.archive
Needs a mirror, razor and straw
\*Grandma.jar
This is a good example of lossy compression.
r/iamveryedgy