1.0.9 — bytes on their way, said so

   ·  ✦   ·        ╭──────────────╮       ·   ✦
 ✦    ·      ·     │  1 . 0 . 9   │  ·        ·
   ·    ✦          ╰──────────────╯     ✦   ·

The owner, reading a fresh post on another device: a picture slot with the browser’s broken-image glyph, a video slot as a black box with a dead play button, and — a long while later — media temporarily unavailable. The bytes were honestly on their way through the relay the whole time. Nothing said so.

A stand-in where the picture will be. While a post’s image, video, audio or cover is being fetched, the element stays sourceless and takes no room, and a quiet note stands in its place: fetching from relay…, with the chunk count and the rail once a round has answered. The note leaves the moment the fetch ends either way — the bytes arrive and the media takes the note’s place, or the unavailable sentence takes it. A picture already on the device shows at once, no flash of the note.

What did not change. The verdict itself. No online source still means what it meant: two minutes with nobody answering. The node keeps asking on its own schedule after that, and the sentence comes down by itself when somebody does.

Measured on the stand. An 8 MB video through the Moscow relay from the catalog on the Amsterdam one: the note at once, the player in nine seconds. A 240 KB image: five.

🐛 Broken, or claiming more than it can prove? → Field notes.