Replicas count unexpired tombstones toward the 256 records per
publisher and refuse new keys beyond it. A round now admits at most as
many podcasts that need a new key as that room allows, so a fair-share
rebalance never displaces cards for newcomers the replicas would refuse.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A reload or a Play after a pause continues from the register instead of
this page's saved position, a seek during preparation is kept, a player
that keeps listening after being superseded writes again as a new
session, a player that loses the playback role records its listening,
marking the loaded episode closes its session, and Prev no longer
resets an episode to 0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The enclosure type of a feed or of a client-sent episode reference no
longer makes an application/octet-stream response acceptable.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Feed downloads and proxy streams have per-account and server-wide
limits, new subscriptions stop at 1000 per account, and scheduled
refreshes take accounts in turns.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Users see the kind of failure only; resolved addresses and transport
details go to the logs, without URLs. Feed and audio requests are
limited to the web ports.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
README and the administration guide describe the Podcasts section,
resume and completion, handoffs, unsubscribing, what stays private and
what the publisher sees, and the security model of the optional audio
proxy. The development guide lists the endpoints, how the player
writes progress and the node tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The ignored device-sync PostgreSQL test now also covers a handoff and a
remote Next onto an episode with an unknown position (the relayed
progress register supplies 1200 s and its generation), and checks that
0.12's operation types fail on a relayed podcast operation and read the
log again after the documented cleanup statement, which the m_0055
backwards operation now shares.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Release 0.12 fails a whole sync batch on a podcast operation kind, so
rolling back is only safe after the relayed podcast operations are
removed: document the step in docs/administration.md and run it in the
m_0055 backwards operation.
The typed queue now records the current track id and queue position
written with it, next to the legacy ids. A 0.12 release that only moved
to another track in the same queue no longer leaves a stale typed
position that the next upgrade would restore. Jam placeholders are never
stored in a user's own typed queue.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>