Files
furumi-web/CHANGELOG.md
T
2026-11-20 15:12:38 +02:00

4.5 KiB

Changelog

v0.14.0 — 2026-11-19

  • Podcasts in the web player: a Podcasts section to add RSS feeds, browse podcasts with unplayed counts and fetch errors, seasons, episode search, filters and paging, refresh, unsubscribe (progress and history are kept) and subscribe again, with Resume, Start over, Mark played/unplayed and the recent listening history.
  • The web player plays podcast episodes from the publisher (or the optional proxy), resumes them from the synchronized position and saves progress in the background: every 20 s and on pause, seek, item change, page hide and handoff, with listening sessions and automatic completion by the shared rule. A source that cannot seek to the saved position is shown as such instead of playing from elsewhere. Handoffs to and from other devices keep the episode, position and pause state; outgoing states carry the newest progress generation.
  • New endpoints under /api/podcasts (/feeds, /feeds/{id}, /feeds/{id}/episodes, subscribe/unsubscribe, /episodes/{id}/playback, /progress, /restart, /played, /unplayed).
  • Jam guests still see the host's episodes only as private items and cannot add episodes from the Podcasts section.
  • Store podcast subscriptions, feed aliases, episodes, seasons, progress and listening sessions of each account in PostgreSQL (src/podcasts/), with the shared music-dht podcast rules. Received podcast operations and snapshot sections are applied to this store, and snapshots are built from it; the wire behavior towards other devices is unchanged. Migrations m_0056 and m_0057 import the state that 0.13 relayed (furumusic__fed_podcast_relay, kept but unused).
  • Refresh subscribed podcast feeds in the background (podcast_refresh job, every five minutes; each feed about hourly) with conditional requests, permanent redirects learned as feed aliases, size and time limits and an exponential backoff up to a day on errors. Accounts subscribed to the same feed share one request. POST /api/podcasts/{podcast_id}/refresh refreshes one feed on demand. Only metadata is fetched, never audio.
  • Optional podcast audio proxy (podcast_audio_proxy_enabled, off by default; browsers stream from the publisher otherwise): GET /api/podcasts/episodes/{episode_id}/audio streams an episode of the signed-in account from its publisher with Range pass-through, audio content types only and size/time limits. GET /api/podcasts/episodes/{episode_id}/source tells the player which URLs to use.
  • Feed and proxy requests only reach public addresses: names are resolved and checked once per connection (no DNS rebinding), IP literals and every redirect hop are checked, and no cookies, credentials or system proxies are used.

v0.13.0 — 2026-11-19

  • Use the shared music-dht 0.6 device-sync types and announce device-sync protocol 4. Podcast operations and snapshot sections from other devices are kept and relayed; devices below protocol 4 never receive them.
  • Keep podcast episodes and other non-library queue items through the web player, with their explicit source. The player labels and skips them; the typed queue is stored next to queue_json (migrations m_0054, m_0055). A handoff through the web player keeps the position of the current episode.
  • Refuse a playback transfer of a queue with podcast episodes to a device that 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; 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

  • Recover federation automatically after sleep, prolonged idle, or a degraded rendezvous transport.