Commit Graph
19 Commits
Author SHA1 Message Date
sanapachandClaude Opus 5.5 681ff7af89 Sync podcast state through the store instead of the relay
Received podcast operations and snapshot sections are applied to the
podcast store, this device's snapshots are filled from it, and an
unknown episode position resumes from its progress register. The
relay module is removed; operations, gating and snapshot bounds on the
wire are unchanged. The device-sync Postgres tests now migrate their
database themselves and cover locally emitted podcast operations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-20 15:12:38 +02:00
sanapachandClaude Opus 5.5 b558cf381e Relay device-sync v4 and keep podcast queue items
Use the shared music_dht::device_sync types instead of private copies
(byte-identical for v3 content, checked against the 0.12.x types and a
golden fixture) and announce protocol 4, because every v4 element is
kept:

- podcast operations stay in the operation log and are relayed only to
  peers that reported v4; their registers and the podcast snapshot
  sections are merged with the shared rules into an opaque relay table
  and returned in this server's snapshots (m_0055);
- the browser bridge carries PlaybackTrack.source: items that are not
  library tracks keep the verbatim wire item, so podcast episodes and
  Jam placeholders survive the round trip; the player labels and skips
  them instead of dropping them;
- the typed queue is persisted in queue_items_json next to queue_json,
  which is still written for rollback (m_0054).

Peer versions come from self-reports (profile_protocol_version); relayed
profiles only raise them and DeviceProfileSet no longer stores this
server's constant. Invites carry the inviter's version and a
DeviceProfileSet announces v4 once. Handoffs of a podcast queue to a
device below v4 are refused with an update message, and its playback
commands are ignored while the queue has podcast items. Jam guests see
podcast items as private placeholders, which are mapped back on their
commands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 16:58:29 +02:00
Aleksandr Bogomiakov 8c0ea444f0 Fixed SQL insert shtorm and connected devices migration 2026-10-06 18:09:47 +01:00
ab ba1c565bdc Integrate shared playback coordination and release 0.10.7 2026-09-10 17:08:34 +03:00
Ultradesu c9266bad22 fix federation recovery after sleep 2026-09-02 15:10:30 +01:00
Ultradesu 69883af8bd Reworked settings page 2026-08-11 12:26:16 +01:00
Aleksandr Bogomiakov 6f337ee626 Add DHT routing for similarity search 2026-08-10 19:54:40 +01:00
Aleksandr Bogomiakov 77cbb62d84 Added similarity search 2026-08-10 01:44:40 +01:00
Ultradesu d61d7a6bac Bump protocols. Added proto status 2026-07-28 22:20:33 +01:00
Ultradesu 624e75839d Reworked federation. Added settings page. Fixed connected devices. 2026-07-27 16:44:16 +01:00
Ultradesu ee4990e2f1 Fixed control mode tracks art 2026-07-25 00:47:00 +03:00
Ultradesu c2bdd62a51 Added FED devices 2026-07-24 16:45:11 +03:00
Ultradesu 5b339aa921 Fixed content_id persistence 2026-07-20 18:40:32 +03:00
Ultradesu 42c772f735 Fixed blake3 computation 2026-07-20 18:24:39 +03:00
Ultradesu 4b7756c36e Extend DHT scheme with content_id 2026-07-20 18:05:16 +03:00
Ultradesu 4381750c6e Extend DHT scheme 2026-07-20 16:29:21 +03:00
Ultradesu 3485f643f4 Fixed DHT republish-after-ttl 2026-07-20 14:19:11 +03:00
Ultradesu 53b2ff29f8 Moved DHT state in psql 2026-07-20 01:59:45 +03:00
Ultradesu 0615356785 Added federation 2026-07-17 13:30:55 +03:00