Navidrome Daily: Weekly Recap - Backing Off Gracefully, Failing Loudly
This week's work centered on making Navidrome respect external rate limits instead of hammering providers, and on making failures visible instead of silent — from truncated streams to Linux file timestamps to alphabetized genre tags. Twenty-three pull request items and twenty-one additional commits landed, including a Go 1.27 upgrade and a batch of small server fixes it surfaced.
Duration: PT2M58S
Episode overview
This episode is a short developer briefing from Navidrome Daily.
It explains recent repository work in plain language.
- Show: Navidrome Daily
- Published: 2026-08-31T09:45:34Z
- Audio duration: PT2M58S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Welcome to Navidrome Daily, covering August twenty-fourth through August thirty-first. Twenty-three pull request activity items and twenty-one additional commits this week.
The strongest thread: Navidrome learned to take "not now" for an answer. PR six-oh-two-eight is the centerpiece — when ListenBrainz or Last-dot-F-M ask the server to back off, that signal now flows through scrobbling, metadata lookups, and artwork fetching alike, instead of each path silently retrying and burning…
Second theme: silent failures becoming loud ones. PR six-oh-three-one and its follow-up, PR six-oh-three-five, fix a case where a failed transcode used to hand back what looked like a complete audio file — Symfonium users saw five to ten percent of synced tracks come out truncated and unplayable. Now a failed stream…
Third theme: a wide fix batch riding on the Go one-point-two-seven upgrade. PR five-nine-nine-zero moved the toolchain forward — note it drops support for older mac-OS versions — and PR six-oh-five-zero swept up issues found along the way: pprof profiles unreachable behind a configured base path, tag truncation…
On the product side, listeners get a few visible additions: PR six-oh-three-six…
N…