forked from Furumi/furumi-web
126 lines
7.8 KiB
Markdown
126 lines
7.8 KiB
Markdown
# Changelog
|
|
|
|
## v0.15.0 — 2026-11-19
|
|
|
|
- Find podcasts in the federated search: cards shared by federation members
|
|
appear in the search results as **Podcasts**, typed apart from music
|
|
(`federation.podcast` events, `"type": "podcast"`; music events are
|
|
unchanged and now carry `"type": "music"`), with **Already subscribed**
|
|
when you follow the podcast, also under another feed address. A card
|
|
opens with its metadata and the seasons and episodes read from the feed
|
|
(`POST /api/podcasts/discovery/preview`), and **Subscribe**
|
|
(`POST /api/podcasts/discovery/subscribe`) creates your own private
|
|
subscription from the card's original feed address with the card's
|
|
podcast id; the publishing member is never contacted. Card texts and
|
|
links are untrusted: shown as text, links and artwork only as checked
|
|
`http(s)` (artwork `https`) addresses.
|
|
- Share a podcast in the federation: a **Share in the federation** toggle on
|
|
the podcast page publishes a public card of the podcast (title, author,
|
|
description, artwork, feed URL, episode count; never progress, history,
|
|
devices or the account) through the server's federation node on the
|
|
separate `podcast_dht` overlay of `music-dht` 0.6. Sharing is the
|
|
account's synchronized decision; turning it off or unsubscribing on any
|
|
device revokes it, and a late state of another device cannot publish it
|
|
again. A feed URL that looks private (token or key in the address, a
|
|
member-feed host) needs a confirmation of the exact address first; the
|
|
confirmation is local to the server (`m_0058`,
|
|
`furumusic__podcast_share_confirmation`) and asked again for a new share
|
|
decision or a moved feed. Accounts sharing the same podcast share one
|
|
card, published while any of them shares it; at most 192 podcasts per
|
|
server. New endpoint `POST /api/podcasts/feeds/{id}/share`
|
|
(`{"shared": bool, "confirm"?: {...}}`, 409 when a confirmation is
|
|
needed); `GET /api/podcasts/feeds/{id}` reports the share state.
|
|
- The federation node serves the podcast-discovery overlay
|
|
(`furumi-fd/podcast-dht/1`, cache `podcast-dht.sqlite3` in the federation
|
|
data directory), advertises `podcast_dht` in its capability manifest only
|
|
while it runs, and probes peers' manifests so the overlay skips peers
|
|
without it. If the overlay cannot start, only discovery is disabled.
|
|
|
|
## 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. Play (also after a reload or a pause) continues from
|
|
the newest saved position of any device; a player that keeps listening
|
|
after another device wrote the episode saves again as a new session, and
|
|
one that loses the playback role records what it listened. Previous goes
|
|
back 15 s within an episode instead of resetting it.
|
|
- New endpoints under `/api/podcasts` (`/feeds`, `/feeds/{id}`,
|
|
`/feeds/{id}/episodes`, subscribe/unsubscribe, `/episodes/{id}/playback`,
|
|
`/progress`, `/restart`, `/played`, `/unplayed`). Request bodies must be
|
|
`application/json`.
|
|
- 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; accounts take turns within a run of up to 200
|
|
feeds. `POST /api/podcasts/{podcast_id}/refresh` refreshes one feed on
|
|
demand. Only metadata is fetched, never audio. An account can have up to
|
|
1000 subscriptions and two user-started feed downloads at once.
|
|
- 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 only
|
|
(a generic binary type needs an audio file extension or audio content; the
|
|
feed's enclosure type is not trusted), size/time limits and four streams
|
|
per account. `GET /api/podcasts/episodes/{episode_id}/source`
|
|
tells the player which URLs to use.
|
|
- Feed and proxy requests only reach public addresses on ports 80, 443, 8080
|
|
and 8443: 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. Users see only the kind of a
|
|
failure; details go to the logs without URLs. A host name that resolves to
|
|
a blocked address gets the same answer as one that does not resolve.
|
|
- The browser can add at most 10 000 episodes outside the account's feeds
|
|
(handed-off queue items) through the playback endpoint (HTTP 422 beyond).
|
|
|
|
## 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.
|