Nonetheless, the point is that
hard-coded mosaics introduce irreparable data loss.
One final way to look at it: I set fire to three books. One is
Jurassic Park. One is
Doctor Zhivago. And one is
The Divine Comedy with extensive appendices. I present to you one pile of ash. And I ask you, "Can you tell me which book this pile of ash came from?" I take a teaspoon to the pile of ash, raise it before you, and ask you a second question: "Can you tell me which words were formerly printed on the paper that constitutes this ash?" You might be able to
if you were there to see it from the beginning. If you saw the book before I set fire to it, and if you knew what the book's contents were like (to the letter), and if you had the supercomputational skills of Ltnt. Cmdr. Data on
Star Trek: the Next Generation, then sure,
maybe you could pull it off. But the fact that you weren't there to see me burn the books means you're out of luck.
Mosaics do not merely scramble the visual data in a movie file around. If they did, then yes, it would be a simple matter of decoding mosaics to restore movies to their original format. Instead, mosaics are like fire: they
permanently alter the data. And like the fire analogy, the only way you
might be able to undo the damage of a mosaic is if you
knew what the original movie looked like to begin with and could therefore try to figure out how, when, and where pixels were altered. But of course, if you already knew that, then you wouldn't be worried about the mosaic in the first place, now would you?