forked from Furumi/furumi-web
Document podcast queue support and release 0.13.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
b558cf381e
commit
c14ab8dfea
5 files changed
+58
-2
No files matched your search
@@ -71,6 +71,14 @@ Trusted-device pairing is separate from public catalog discovery. It connects
|
||||
a user's own Furumi players so likes, playlists, playback state, and control can
|
||||
move between approved devices.
|
||||
|
||||
Queues synchronized from other Furumi players can contain podcast episodes. The
|
||||
web player keeps them in the queue, in order and with their position, and shows
|
||||
them as **Podcast · not playable in the web player yet**; local playback skips
|
||||
them. A device that does not support podcasts yet (device-sync protocol below
|
||||
4, for example an older terminal player) cannot receive such a queue: selecting
|
||||
it as the playback device shows that it needs an update, and the episodes stay
|
||||
in the queue. Jam guests see podcast episodes of the host only as private items.
|
||||
|
||||
## Admin statistics
|
||||
|
||||
The only admin interface is `/admin/v2`, also reachable from `/admin/`.
|
||||
|
||||
@@ -35,6 +35,39 @@ source code, templates or prompts reuse the dependency layer when its recipe and
|
||||
toolchain are unchanged. Both dependency and application builds use `--locked`.
|
||||
Update the pinned build tools in `Dockerfile`; changing them rebuilds the cache.
|
||||
|
||||
## Connected devices and podcast queue items
|
||||
|
||||
Trusted-device sync uses the shared `music_dht::device_sync` types (no local
|
||||
copies) and announces protocol version 4. The web player has no podcast
|
||||
features yet, but it keeps every v4 element it receives:
|
||||
|
||||
- podcast operations stay in the operation log and are relayed to v4 devices
|
||||
only; their registers and the podcast snapshot sections are merged with the
|
||||
shared `music_dht::podcast` rules into `furumusic__fed_podcast_relay`
|
||||
(opaque contract JSON) and returned in this server's snapshots;
|
||||
- queue items that are not library tracks become external browser items
|
||||
(`source` plus the verbatim `wire_track`), so podcast episodes and Jam
|
||||
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`.
|
||||
|
||||
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
|
||||
contract (`PODCASTS.md`) and `PLAYBACK_PROTOCOL.md` in the Frid repository.
|
||||
|
||||
```bash
|
||||
cargo test devices:: queue_items podcast_relay queue_persistence
|
||||
node --test tests/player_queue_sources.test.cjs
|
||||
# Migrated disposable PostgreSQL (start the server against it once):
|
||||
FURU_DEVICE_SYNC_TEST_DATABASE_URL=postgresql://... \
|
||||
cargo test postgres_podcast_relay_gating_and_peer_versions -- --ignored
|
||||
```
|
||||
|
||||
`wire_compat_tests` compares the shared types with the private copies of
|
||||
0.12.x byte for byte; `fixtures/v3_hello.golden.json` is the v3 shape. Rewrite
|
||||
it only for a deliberate change, with `FURUMUSIC_BLESS_GOLDEN=1`.
|
||||
|
||||
## Contributing
|
||||
|
||||
Bug reports, design discussions, and patches are welcome. Before submitting a
|
||||
|
||||
Reference in new issue
Block a user