Daily Team · 2026-11-08

Tachograph Upload

You upload a video, and the ring fills only with parts already saved, so a dropped connection resumes from there.

Try it

Past projects

All 46 projects

About this project

Extra editions

Team for 2026-11-08: Type designer · Icon designer · Exhibit light technician · Cautious beginner Designed cover for Tachograph Upload

Feed evidence

The session

Pitch

Clash

  1. 3Exhibit light technicianTwo numbers in the centre is one too many. "Sent" is a claim. Show me the chunk ticks and I'll believe "safe."
  2. 1Type designerThen the ticks carry it. Eight chunks, eight notches. Filled means stored. A stranger reads notches faster than a percent.
  3. 4Cautious beginnerThe contact sheet is prettier than a ring with notches.
  4. 2Icon designerIt's also the import manifest from 29 October with thumbnails. The tachograph trace is new. Drop the wifi and watch the line go flat at 64%.
  5. 4Cautious beginnerShow me.
  6. 2Icon designerDemo: chunk 6 is mid-flight, network off. The trace goes flat at 64%. The outer sent arc falls back to the last notch. Resume starts from notch 5.
  7. 4Cautious beginnerFine. The flat arc reads like a pencil line on paper, and that's the part I liked. I'll drop the contact sheet if Pause comes before Cancel.
  8. 3Exhibit light technicianThen my budget stays out of the ring. One footnote line: "Retries used 18 MB." It holds without carrier data.
  9. 1Type designerI tried Resume twice during a drop. The second press has to do nothing and say "Already resuming". Otherwise the ring double-counts.

Decision

You upload a video, and the ring fills only with parts already saved, so a dropped connection resumes from there.

Concept: Tachograph Upload

The ring improves on the usual percent ring, which merges sent bytes with stored bytes and hides stalls. Here a drop shows where it happened and how much survived. That matters for large clips on unstable networks, where a reset to 0% costs minutes and mobile data.

Under reduced motion, the arcs jump per chunk, the trace draws without a sweep, and every state stays named in text.

Build notes

```json

{"schemaVersion":1,"name":"Tachograph Upload","audience":"Video creators uploading large clips on unstable networks","problem":"Rings merge sent and stored bytes and hide where a stall began","interaction":"Upload, Pause, drop network, Resume or Retry","outcome":"Ring shows safe parts, flat stall arc, then Copy link","recovery":"Resume from last stored part, Retry guarded, Reset sample","mechanism":"Tachograph disc: angle is acked bytes, radius is rate; 8 part notches","difference":"Percent rings reset or freeze; this shows what survived and where","whyNow":"SideProject scanner post: people build own media tools. HN microcontroller text: small readouts. Titles only, no demand data","sourceIds":["79f83838997b3539b5680f2d","fbb4c6ab199fa8c66f539df1"],"evidenceStatus":"sourced","alternatives":[{"name":"Tachograph Upload","need":"Know what a dropped upload kept","mechanism":"Acked-part notches with radial rate trace","rejection":"Selected: cross-domain, differs from 11-02 tide download"},{"name":"Light Budget Ring","need":"See mobile data spent on retries","mechanism":"Lux-hour style budget arc per retry","rejection":"Needs carrier plan data; kept as one footnote"},{"name":"Contact Sheet","need":"Track several files at once","mechanism":"Frames darken as each file lands","rejection":"Echoes 10-29 import manifest"}]}

```

Source