Selfhosted

60588 readers

1789 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the link in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post. )

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

561

Plex’s crackdown on free remote streaming access starts this week - Ars Technica (arstechnica.com)

submitted 7 months ago by otters_raft@lemmy.ca to c/selfhosted@lemmy.world

284 comments fedilink hide all child comments

Plex is starting to enforce its new rules, which prevent users from remotely accessing a personal media server without a subscription fee.

If anyone needs it: https://jellyfin.org/

you are viewing a single comment's thread
view the rest of the comments

[–] ShortN0te@lemmy.ml 15 points 7 months ago (2 children)

If it becomes an issue, then you're in the exact same position you'd be in today if you decided to move away from Plex now.

I disagree. Right now you got time to do the research, plan the move and test it out with a demo setup. You do not know if you got the time if Plex decides to screw their lifetime users.

Yes this is hypothetical.

[–] moseschrute@lemmy.world 13 points 7 months ago (1 children)

The steaks are very high. I could lose access to my media library for 1-2 evenings (the time it would take me to switch to Jellyfin).

[–] lando55@lemmy.zip 1 points 7 months ago (1 children)

Plex are trying to start a beef

[–] kalpol@lemmy.ca 1 points 7 months ago

Locking horns with users

[+] Kushan@lemmy.world -8 points 7 months ago (2 children)

It's entirely hypothetical. Jellyfin could also close source tomorrow, hypothetically (It happened with Emby so there's precedent).

[–] festus@lemmy.ca 18 points 7 months ago* (last edited 7 months ago)

Jellyfin can't go closed source as it's a fork of Emby from before it was closed source, licensed under the GPL. They don't own that code so they can't change that license, thus the whole project is GPL. In addition, Jellyfin isn't being developed by just one company (it's all volunteers), so every new contribution is also GPL licensed, owned by each contributor. The only way Jellyfin could go closed source would be to cut out the Emby backend and for every single contributor ever to agree to change the license, or have their code cut out. In short it's not happening, and if somehow it did the project would just get forked regardless for everyone to switch to (the community did it once already!).

[–] ShortN0te@lemmy.ml 10 points 7 months ago

No, you have not understood anything. Assuming Jellyfin would go closed source, (ignoring the GPL license and so on) you would not notice anything. Your server and service would be unchanged by this.

Emby is the best example, the community will fork it and you server lives on. Even if not, then the server and software is still yours.