diff --git a/CHANGELOG.md b/CHANGELOG.md index c128dd8..32ce08a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -13,10 +13,19 @@ needs an update, and ignore its playback commands while the queue has them. - Store the protocol version each device reports itself instead of this server's version; invites carry the inviter's version. +- An episode that the web player selects without knowing its position (Next, + auto-advance, a click) resumes from its synchronized progress on the next + device instead of restarting at 0. Repeat all and shuffle continue past + episodes; Prev and seeking work on them. - Jam guests see podcast episodes of the host as private items, without their - duration, and cannot add, remove or clear them. + duration, and cannot add, remove or clear them; the host browser enforces + this on its own queue. Guests do not keep the placeholders after the Jam. - Metadata Repair can still undo deletions recorded before the typed queue column was added. +- Rolling back to 0.12 requires removing the relayed podcast operations first; + see "Rolling back to 0.12" in `docs/administration.md`. After a rollback, the + typed queue is used again only if 0.12 left the queue and its current track + unchanged. ## v0.10.6 — 2026-09-02 diff --git a/docs/development.md b/docs/development.md index 6c38964..f87d3ff 100644 --- a/docs/development.md +++ b/docs/development.md @@ -50,7 +50,17 @@ features yet, but it keeps every v4 element it receives: placeholders survive peer → server → browser → server → peer unchanged; - `furumusic__playback_state.queue_items_json` stores the typed queue next to `queue_json`. `queue_json` (library ids) is still written for rollback; the - typed value is used only while its recorded ids match `queue_json`. + typed value is used only while the legacy columns it recorded + (`queue_json`, `current_track_id`, `queue_position`) match the row. Jam + placeholders are never stored in a user's own queue. +- a browser that selects a podcast episode it cannot play does not know the + episode's position. It reports `position_unknown`, and the server sends the + resume position of the relayed progress register instead of 0. Jam + participant commands carry `jam_participant`; the host browser checks them + against its own queue. + +Rolling back to 0.12 needs the podcast operations removed from the operation +log first; see "Rolling back to 0.12" in `administration.md`. Everything sent to a device is gated by the version that device reported itself (`profile_protocol_version`; relayed profiles only raise it). See the podcast