Document podcast feed refresh and the audio proxy

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
sanapachandClaude Opus 5.5 committed 2026-11-20 15:12:38 +02:00
1 parent 2c0c3d21aa
commit 5aaea8a8eb
3 files changed
+78

No files matched your search

+22
View File
@@ -79,6 +79,28 @@ them. A device that does not support podcasts yet (device-sync protocol below
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.
### Podcast feeds and audio
The `podcast_refresh` job (every five minutes, listed under Jobs) checks the
feeds of subscribed podcasts: each feed about once an hour with conditional
requests, failing feeds less and less often (up to once a day). It downloads
feed metadata only, never episode audio. A failing feed keeps its known
episodes. Accounts subscribed to the same feed share one request.
The server therefore makes outgoing HTTP(S) requests to podcast publishers.
It only connects to public addresses: feed or audio URLs that point to
loopback, private, link-local, CGNAT or cloud metadata addresses, directly,
through DNS or through a redirect, are refused. System proxy settings are not
used for these requests.
Episode audio is streamed by the browser directly from the publisher. Some
publishers cannot be played that way (no CORS, or plain HTTP while this
server uses HTTPS). For them, enable **Settings → Podcasts → Podcast audio
proxy** (`FURU_PODCAST_AUDIO_PROXY_ENABLED=true`): the server then fetches
the audio of an episode from the publisher when a signed-in user's player
requests it and passes it through without storing it. This uses the server's bandwidth. Only
audio responses are passed through, up to 1 GiB and 4 hours per request.
### Upgrading from 0.13
Podcast state synchronized from other Furumi players is kept in per-account