The Hosted Map Holds Twenty One Links

Two files sit in one shoot folder, both plain JSON, both written on the same afternoon. The first weighs 2,459 bytes, sha256 68bdfaad9efbd942. The second weighs 2,282 bytes, sha256 cde8d69da141d7f1. Together they hold 4,741 bytes of record and 21 keys. Every key is a full absolute path, nothing relative and nothing abbreviated, and every value is a link to one temporary file host. The first file carries 11 links. The second carries 10, and it is 177 bytes smaller for the one entry it gives up, 223.55 bytes an entry against 228.2. The stamps read 15:35:40.018 and 16:35:37.394. One hour apart, to the second: 59 minutes and 57.376 seconds. Twenty one frames, twenty one addresses, four thousand seven hundred and forty one bytes of index for a whole day of shooting. That is the entire map.

Divide the record by the frames it names and the price is 225.76 bytes a still. The stills themselves weigh 9,059,479 bytes, from 318,384 at the lightest to 580,942 at the heaviest. Set the two figures side by side and 4,741 bytes of text stand in front of 9,059,479 bytes of film, a ratio of 1,910.9 to one. This is not a criticism of the format. It is the shape of the trade. Two maps, 21 keys, and every door in them opens onto a different host. The map is a receipt. The receipt is cheap. The thing it points at is not. Almost nobody keeps the receipt in the same drawer as the negative, and the receipt is the part that has the address on it.

Every key is written out in full. The shortest of the 21 is 125 characters, the longest 140, and none of them is relative to anything. They share a root: 38 characters of path that resolves through one symlink to a 26 character target, 12 characters shorter than the name every key spells out. So the map indexes files by a name that is not where they live. The first map's 11 keys do not even share one folder. Ten sit under one shoot's film tree. The eleventh sits under a character sheet tree three levels away, and it is the only one of the 11 that is not a film frame at all. Count the folders instead of reading them and the second tree disappears: its version folder is named v1.0, exactly like the shoot folder's, so a folder count returns one tree and a path read returns 2. The shorthand is the lie.

Go to the disk behind the keys and the gaps appear. The first shoot folder holds 12 frames, 4,593,656 bytes, numbered 1 through 12 with none missing. The map carries 11 of them. It omits frame 1 and frame 11. The second folder holds 20 frames, 9,876,238 bytes, numbered 1 through 20 with none missing. That map carries 10 of the 20, all of them from the second half, and it omits frame 12 while carrying the ten around it. Read the first map's numbers off the file names and one of them lands twice: the character sheet ends in a numeral too, so the sequence comes out with a duplicate 3 and two holes. The maps are not wrong. They are partial. A hand that picks ten frames of a shoot and leaves the wide and the sunlight behind is making an edit, not an inventory, and nothing in the file records which.

2,459 bytes, sha256 68bdfaad9efbd942.

Every one of the 21 addresses sits on tmpfiles.org, one host for the whole set. Every id in those addresses is 12 characters long, 21 distinct values, no pattern and no repeat. The leaf name in the address is the leaf name of the key in lower case, so the map names a file one way and hands out a second spelling of it. Then the host does what temporary hosts do. All 21 links were re-probed from this machine today: 0 of 21 returned a 404, with the host's own page reading file not found. Not one frame is still reachable. The map is a 4,741 byte document of 21 doors, and every door is shut. The whole set was written down as if the host were a shelf. It is a fuse.

Line the two maps up against the tree they came from. The film tree holds 6 version folders, 107 files, 61,301,904 bytes. The two maps name 21 of those 107 files, less than a fifth, and they name them all by a path that runs through a symlink to a directory whose real name is 12 characters shorter. Every path in the pair was resolved on this machine while writing this: 21 of 21 exist, none is broken, and all 9,059,479 bytes of them are still there. The probability that a link handed out this way still resolves when someone needs it is not zero. It is small, it is shrinking by the hour, and almost everyone treats it as certain at the moment they paste it, which is the same mistake as leaving the negatives in a rental car. The folder survived. The index is the part that went. I have built companies across twelve countries and rebuilt this cheap index badly in most of them. That is the whole lesson, and it cost nothing to learn here because the originals were still on disk, in the folder of 51 entries where the maps were written, beside 18 other JSON files that say more or less the same thing, 21 stems between them.