this post was submitted on 24 Jun 2026
64 points (89.0% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

69547 readers
234 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

We heartily recommend visiting the free port of freemediaheckyeah (aka FMHY) while you sail the high seas, for all the freshest links the ocean has to offer.

📜 c/Piracy Wiki (Community Edition):

🏴‍☠️ Other communities

FUCK ADOBE!

Torrenting/P2P:

Gaming:


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 3 years ago
MODERATORS
 

you are viewing a single comment's thread
view the rest of the comments
[–] oneser@lemmy.zip 2 points 2 hours ago (1 children)

While you are (probably?) correct, this is significantly beyond what is required to deploy Plex for a standard home server chump like me.

I'm using jellyfin and a few others, but am consciously putting off exposing these services to the web until I can learn enough about security to do so. Given life, this will probably take me the better part of a year...

[–] nibbler@discuss.tchncs.de 2 points 1 hour ago

you are right to be careful here. But it certainly is also not a "requirement to deploy jellyfin" either. It's just a good practice to minimize attack surface, no matter what you expose. Unless it's meant for the general public and advertised, then this makes little sense :-)

Also, most selfhosters have at best one IP to use. This helps with the one-IP-multiple-webservices problem anyway.