92
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Sep 2023
92 points (97.9% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54420 readers
426 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
If Jellyfin would do such stupid thing, somebody would fork it to a new project
in fact this did already happened in the past: Jellyfin was forked of Emby after they changed their license
Jellyfin is unable to do that because they don't have centralised auth like Plex does.
Not like it could be implemented.
But the the community would (as OP said) fork the project.
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.