Comment by atombender

8 hours ago

I left Plex for Jellyfin + Infuse a couple of years ago, and I'm not looking back.

But the sore point right now is outside access, which Jellyfin really isn't made for. I set up Tailscale so I can connect Infuse to Jellyfin remotely. But that's not exactly as smooth as Plex. I can't give friends and family access, either, which was dead easy with Plex.

In terms of the UX, Infuse isn't very good, but it does the job okay. The built-in subtitle fetcher is amazing; that stuff never worked for me with Plex.

Is Plex/jellyfin even necessary for Infuse? I've been using Infuse for years now and it has direct access to my NAS to look for media content and just directly plays it. It's a such an amazing app and it plays everything I throw at it without any buffering or transcoding issues. The Pro version pretty much has all the necessary codecs, including all the dolby things for hdr/atmos. It just works so well.

For people that don’t know, Infuse lets you use Jellyfin on Apple TV and it’s very helpful for day purpose

  • There is also an open source tvOS client called Swiftfin. The experience isn't as good though.

    You can also transcode your files to formats that the free version of Infuse supports if you are a miser.

  • ... and is awesome even without Jellyfin - I have it installed on all devices including Apple TV, connected to family NAS through webdav.

tailscale + cloudflare for lets encrypt support. can then give family tailscale access

  • Has cloudfare become any more strict with passing large amounts of video data through them? I heard they were kind of against it, but haven't enforced anything.

    • If you don't proxy or tunnel the connection, it isn't an issue. I assume they are using Tailscale for the actual connection.

  • One does not need cloudflare for letsencrypt. The tooling has become really simple to use.

    • You do need a DNS service with API access for automatically creating/renewing the certificates for things that are only served over tailscale though, since they aren't publicly accessible for the letsencrypt servers to talk to.

      1 reply →