Navidrome Daily: Jellyfin Rating Safety Fix and Comment Expand Cue

A merged Jellyfin API fix prevents silent rating clears, adds user data endpoints, and tightens ownership validation, while an open UI change fixes undiscoverable overflow in collapsed comments. The two items show no broader pattern — the API correctness change is the highest-impact work.

Duration: PT2M13S

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-10-13T10:01:05Z
  • Audio duration: PT2M13S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning, it's October 13th, 2026, you're listening to Navidrome Daily.

Today's activity doesn't form a single pattern. The standout is a Jellyfin A P I correctness and data safety fix, with a separate user interface fix alongside it.

First, pull request 6315, now merged, corrects how ratings handle the likes flag. Previously the server only read a numeric rating value that upstream Jellyfin does not define, so requests using the standard likes flag, or sending no value or a bad value, could silently clear a user's rating. Now a likes true stores…

Second, open pull request 6326 fixes collapsed comments. A long comment that wrapped past the collapsed height was clipped with no visual cue and could not be discovered or expanded. The fix detects real overflow by comparing heights and rechecks on resize and content changes, so the expand cue appears only when…

What's next for developers: test third-party Jellyfin clients that use likes or user data writes against the stricter validation, and watch for reliance on the old silent-clear behavior. For the interface change, verify expansion across narrow and wide layouts.

That's it for today, thanks for listening.

Nearby episodes from Navidrome Daily

  1. Silent Data Fixes for Playlists, Recommendations, and Jellyfin
  2. Windows Test Parity and About Crash Fix
  3. Defensive Fixes for Queues, Scans, and Backups
  4. Large-Offset Paging Fix and About Dialog Crash
  5. Server Crash Fix and Player Polish
  6. Smart Playlist Date Added Fix
  7. Playlist Artwork Crash Fix
  8. Weekly Recap - Smarter Scanning, Leaner Streaming and Interface Hardening