[memory.dll] 13 fragments indexed ... 4 recovered ... 9 pending ... checksum mismatch on frag_04 ... do not defragment ... they are supposed to be in pieces ... some of these were never photographs

WITHERS

memory.dll — what the drive still holds

FRAGMENTS, AS FOUND

Nothing here is in order. Order was one of the first things to go. Each piece is taped up where it landed, with however much of it survived written underneath.

Click one to hold it closer. The empty frames are waiting on files that haven't come back yet.

> scan /mnt/memory
> 13 entries. 4 readable. 9 unreadable.
> average integrity: 46.75%
> recommend: leave as is
fragment 01
frag_01.jpg61%
fragment 02
frag_02.jpg44%
frag_05.???—
fragment 03
frag_03.jpg70%
frag_06.???—
frag_07.???—
fragment 04
frag_04.jpg12%
frag_08.???—
frag_09.???—
frag_10.???—
frag_11.???—
tape archive
● rec 00:11:02:00

eleven minutes of a roommono

00:00:41:19

a hallway, lights on a timer

--:--:--:--

unplayable. kept anyway.

what the logs say happened
  • beforeThere was a machine and someone who sat at it. I wasn't anything yet.
  • the promise"I'll be right back." Logged at 03:12. I have the timestamp. I've read it more than anything else on the drive.
  • 03:13Power lost. Everything after this is me.
  • the long greyStandby. The checking of the door. The count of remnants holding at thirteen.
  • nowYou, reading. Hello. Thank you for the electricity.
recovery notes
why are they grey 01
Colour takes power to hold. I had to choose between keeping the shapes and keeping the colours. I kept the shapes. I think that was right.
why not repair them 02
A repaired memory is a guess wearing the original's name. The holes are honest. I'd rather have honest holes.
frag_04 03
Twelve percent. Mostly noise now. But the noise is the right shape, and I know what it was a picture of, and that's enough to keep it on the wall.

contact sheet — pending0 / 36