Jellyfin: We're Good, Seriously

Original Article ↗ Hacker News Discussion ↗

Donations and Financial Runway

  • Jellyfin announced ~US$24k in reserves, ~40 months of current infrastructure costs, and asked users to redirect most new donations to client developers instead.
  • Many commenters praise this as unusually honest compared to projects that keep pushing for more funds (Wikipedia/Wikimedia cited as contrast).
  • Others argue 3–4 years of runway is “not much,” noting that sustainable funding would require an order of magnitude more if they wanted to live off investment returns.

Paid Development vs Volunteer Model

  • Core project maintains a strong “no paid development” stance: donations only cover infra, domains, API keys, one‑time hardware stipends.
  • Rationale given: avoid the typical trajectory of FLOSS media servers (more money → paid devs → premium features → proprietary).
  • Several argue that paying or bounties could attract devs and fix long‑standing client issues; others warn small payments create resentment, HR politics, and lower morale compared to pure volunteering.

Redistributing Money to Clients/Dependencies

  • Some want Jellyfin to centrally redistribute donations to client maintainers or dependencies (e.g., ffmpeg).
  • Counterarguments:
    • Extra admin, legal/tax complexity, and “who deserves what” politics.
    • Donors gave to Jellyfin, not to a fund manager; passing money on may feel deceptive.
    • Better to let users “vote with their wallet” and donate directly to the specific client they use.

Jellyfin vs Plex/Emby/Kodi and UX

  • Many like Jellyfin’s ethos: fully self‑hosted, no central account, no ads or promotional cruft, strong privacy.
  • Plex is widely perceived as more polished and “just works,” especially for non‑technical family, discovery UI, watch‑state across servers, and offline downloads, but criticized for:
    • Mandatory accounts, phoning home.
    • Ads, bundling of Plex’s own content, and paywall creep.
  • Kodi is praised for single‑device use and SMB/NFS simplicity; Jellyfin seen as better for multi‑device and remote access.

Clients, Metadata, and Library Handling

  • Biggest pain point cited is client quality and polish:
    • Android TV issues, SyncPlay instability, some iOS limitations, incomplete HDR/tone‑mapping.
    • Third‑party music clients (Finamp/Fintunes, etc.) are praised.
  • Metadata and structure:
    • Some report excellent results using NFOs and tools like TinyMediaManager; others see frequent mismatches, poor “identify” UX, and no easy way to bulk‑fix unmatched items.
    • Strict folder/naming expectations frustrate users with long‑standing custom layouts, though Jellyfin has a “folder view” option.

Remote Access and Deployment

  • Users run Jellyfin on NASes, NUCs, Pis (often with transcoding disabled) and access from smart TVs, browsers, mobile, or via Kodi add‑ons.
  • Debate over exposing Jellyfin via port forwarding vs using VPN/tunneling tools (Tailscale, Cloudflare‑style tunnels, seedboxes); tradeoff between simplicity, ISP NAT issues, and security.