cooopsspace, 9 miesięcy temu (edited 9 miesięcy temu) angielski There’s absolutely zero way that is going to get pulled into the actual Jellyfin project, hence a fork is unnecessary. It’s unreasonable to take responsibility for apps a user runs on their server. But when you all of a sudden see a heap of Plex IP addresses hitting your provider with mass media sharing rings you’ve got problems. Jellyfin however is just serving HTTP/S. Thats it. You can’t ban Nginx or Apache.
There’s absolutely zero way that is going to get pulled into the actual Jellyfin project, hence a fork is unnecessary.
It’s unreasonable to take responsibility for apps a user runs on their server.
But when you all of a sudden see a heap of Plex IP addresses hitting your provider with mass media sharing rings you’ve got problems.
Jellyfin however is just serving HTTP/S. Thats it. You can’t ban Nginx or Apache.