The server keeps one small relay (32 MiB ahead, 8 behind) for Up next's
first relayed item, keyed by its queue id at a URL that stays the same
after the swap: fetched by the server for server-fetch links, fed by
the adder's app for through-me links and files, by a member with an
account for member-passed Jellyfin items. Every app preloads from it;
the swap promotes it with its buffer. Dropped when the item stops
being first or its adder leaves. Measured switch: ~1.6 s cold, 20-40 ms
preloaded. ROADMAP gains the research item on server-side fetching of
member-resolved URLs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every app gets the first Up next item ready itself (own Jellyfin plan,
direct links, guests via /j when state.relayNext says the server's
login can pass it on) and opens it in a hidden, muted, paused second
player; the swap promotes that player instead of opening cold, so its
buffer counts at once. Reports go out on open and when the buffer
reaches the gate's need. SwitchTrace times each phase. Measured in the
e2e harness: 1.5-3 s before, 35-103 ms with a preload. Relayed items
still open cold for everyone but their source (ROADMAP).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Overlay: one layout for both designs (top bar with Up next as one of
its buttons; one action band above the controls for the status pill,
skips, next episode and end cards), one glass recipe (AppGlass) and
one pill (FloatingPill); hovering any of them, or the open queue,
holds the controls up.
- Up next: the first item (or the first continuation episode) is kept
resolved on the app that puts it up, refreshed before it expires;
Schedule and drop/paste can queue too.
- Jellyfin: WatchSession (core) counts real watched coverage; an
episode is watched at 80 % or at its ending after half; a played one
is re-marked after Playing (10.11 unmarks on open) and never gets a
position; a peek leaves the old resume point; part-way resume points
stay under 85 %.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Up next: a server-side queue anyone edits by item id (add at end or
next, move, remove, play now, skip); each item says who added it and
how it plays. At the real end the first item swaps in after the end
card's countdown, put up by whoever can (its adder for through-me links
and files, someone with access for Jellyfin, else anyone); items that
can't play are skipped with the reason. The next item's link is
resolved ahead. Greyed "Continues with" episodes below. A chip with the
controls opens it as a popover (leaf_widgets, local path dependency for
now); "Add to queue" next to Put it up everywhere.
Delivery: the server measures the source's rate, the media's bitrate
and each member's read rate; the members card shows a source line
(who passes it on, through what, keeping up or not, source left) and
each member's route and buffer. A slow source is told once per media.
A failed server fetch is announced to everyone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
