zlacker

[parent] [thread] 6 comments
1. s0rce+(OP)[view] [source] 2025-12-05 19:58:12
I found Jellyfin was super easy but I came from XBMC/Kodi which was a big struggle.
replies(2): >>Forget+W1 >>tills1+QG
2. Forget+W1[view] [source] 2025-12-05 20:08:19
>>s0rce+(OP)
I think what trips people up with jellyfin is making sure they aren’t exposing their network. Getting it to work at home is one thing, getting it to work outside your home is a different beast
replies(1): >>s0rce+u52
3. tills1+QG[view] [source] 2025-12-06 00:13:45
>>s0rce+(OP)
isn't Plex literally an XBMC fork? And Jellyfin a Kodi fork? Something like that.
replies(2): >>russel+SM >>s0rce+Y52
◧◩
4. russel+SM[view] [source] [discussion] 2025-12-06 01:07:41
>>tills1+QG
Jellyfin is a fork of Emby. Can't speak for Plex.
◧◩
5. s0rce+u52[view] [source] [discussion] 2025-12-06 16:23:40
>>Forget+W1
Ah, I have no use/interest in remote access to my library. I just have one tv in the house with an NVidia shield that accesses the Jellfin library on a miniPC on the network.
replies(1): >>Forget+1O2
◧◩
6. s0rce+Y52[view] [source] [discussion] 2025-12-06 16:27:14
>>tills1+QG
Yes, I think Plex was an XBMC fork and Kodi is the new name of XBMC. Jellyfin forked from Emby, I think when it became closed source. I never used Emby. Plex always seemed to cost money in confusing ways and that turned me off. My initial TV just used NFS shares on a unix machine and a Netgear NeoTV box (~2009) but eventually the codec support was too poor so I moved to XBMC on the Shield and then a number of years later to Jellyfin server on Linux with Jellyfin client on the Shield.
◧◩◪
7. Forget+1O2[view] [source] [discussion] 2025-12-06 22:43:18
>>s0rce+u52
I got kids so accessing it when traveling is pretty critical, as is the ability to quickly locally download to a tablet lol
[go to top]