WiiFin – Jellyfin Client for Nintendo Wii

Original Article ↗ Hacker News Discussion ↗

WiiFin, Wii Capabilities, and Retro Use-Cases

  • Surprise and delight that a Jellyfin client exists for Wii before PS5/tvOS.
  • Wii’s analog/component output and support for 240p/480i seen as ideal for CRTs and classic content, though its CPU struggles with 480p decoding.
  • Some note it’s useful as a “Swiss army knife” for older resolutions despite limited performance.
  • Ideas to pair WiiFin with Dolphin emulator and custom Wii menus for a living‑room “media + games” box controlled by a Wiimote.

Jellyfin vs Plex and Ecosystem Trends

  • Observations that Jellyfin is overtaking Plex in some app catalog metrics; interpreted as Jellyfin’s ecosystem strengthening.
  • Plex criticized for pricing changes, paywalling core features, pushing ad-supported content, removing plugins, and requiring cloud accounts even for self-hosting.
  • Jellyfin praised as open source and forkable (contrast to Plex/Emby “rugpulls”), with broad client availability and generally “it just works” experiences.
  • Some users still stick with Plex or abandon both in favor of simpler stacks like SMB + local players, Kodi, UPnP/DLNA, or specialized servers (for books/comics/audiobooks).

Security, Remote Access, and Risk Tradeoffs

  • Significant concern about exposing Jellyfin directly to the internet; several recommend VPN-only access (WireGuard, Tailscale) especially for app-based clients.
  • Others argue the official docs endorse simple HTTPS reverse proxying (e.g., Caddy) and see this as adequate if passwords are strong and TLS is configured.
  • Debate over Jellyfin’s security posture: mentions of known but mostly low-impact unauthenticated endpoints vs claims of “pages of non-fixed confirmed exploits.”
  • Techniques discussed: reverse proxies with long path prefixes, HTTP auth, IP whitelisting, auth gates (Authelia/Authentik + OIDC), and VPS/exit-node setups; complexity and usability for non‑technical family (Roku users, elderly parents) is a recurring pain point.

Client Quality, Bugs, and Operability

  • Many positive reports (especially on Samsung Tizen and Roku), but others complain of:
    • Clients losing server connection, misleading login prompts, UI glitches, and missing seasons.
    • TV apps forgetting server IPs, fragile mobile behavior, and non-obvious error messages.
  • Jellyfin server noted as single-node, SQLite-based, and not HA-ready; database refactor toward pluggable engines introduced regressions for large libraries.

Transcoding, Hardware, and Scaling

  • WiiFin forces server transcoding; most consider 480p trivial for modern hardware.
  • Strong recommendations for Intel Arc GPUs (no artificial stream limits) over Nvidia for heavy multi-stream transcoding.
  • For ~20 households, consensus is Jellyfin is not designed for horizontal clustering; suggested workarounds include multiple instances sharing media storage and remote hardware acceleration.