this post was submitted on 27 Nov 2025
205 points (99.5% liked)

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

65359 readers
494 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):

🏴‍☠️ Other communities

FUCK ADOBE!

Torrenting/P2P:

Gaming:


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 2 years ago
MODERATORS
 

Plex has confirmed that it will require a Remote Watch Pass or Plex Pass for remote streaming on its TV apps. The change is going into effect for the Roku app first, followed by all other TV apps and third-party clients in 2026.

Earlier this year, Plex increased its pricing for Plex Pass and stopped supporting all options for free remote streaming in the Plex apps, such as adding a custom server connection in the app settings. The company said at the time, "The reality is that we need more resources to continue putting forth the best personal media experience, and as a result, we will no longer offer remote playback as a free feature." That's also when Plex introduced the Remote Watch Pass as a less expensive way to enable remote streaming again.

Plex is now rolling out the remote watch changes to its Roku TV app. If you have Plex Pass, or the owner of the server you're streaming from has Plex Pass, you don't need to do anything. Otherwise, if you are streaming on a different network from the server's home network, you need Plex Pass or Remote Watch Pass.

you are viewing a single comment's thread
view the rest of the comments
[–] CmdrShepard49@sh.itjust.works 2 points 3 hours ago (1 children)

This seems like a naive viewpoint as you're exposing your whole network and everything connected to it to the open internet. Just because the port connects to Jellyfin doesnt mean there isn't some exploit or vulnerability that can allow for greater access. This is media software written by volunteers and offered for free, so I wouldn't expect Fort Knox security from it just because its FOSS. In fact, they specifically put the onus on the user to do this themselves if they so chose.

[–] turdas@suppo.fi 1 points 1 hour ago (1 children)

I would trust the FOSS software's actually auditable security any day of the week over the sketchy proprietary solution targeting an extremely niche market.

[–] CmdrShepard49@sh.itjust.works 1 points 25 minutes ago (1 children)

Fair enough but has anyone actually audited how secure Jellyfin is when exposed directly to the open internet? Not even the actual developers of the software recommend that, yet the majority of the replies here are being overly smug and cocky thinking it's perfectly safe to do so.

[–] turdas@suppo.fi 1 points 7 minutes ago

People have audited the APIs and it is a known issue that if you know the correct URL to certain resources on the server (e.g. specific files) you can fetch them without authentication. Nothing more serious than that has been found.