Selfhosted

44583 readers

2065 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

586

Plex is locking remote streaming behind a subscription in April (www.plex.tv)

submitted 9 hours ago by Sl00k@programming.dev to c/selfhosted@lemmy.world

370 comments fedilink hide all child comments

We are also changing how remote playback works for streaming personal media (that is, playback when not on the same local network as the server). 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. This—alongside the new Plex Pass pricing—will help provide those resources. This change will apply to the future release of our new Plex experience for mobile and other platforms.

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

[–] mutual_ayed@sh.itjust.works 2 points 7 hours ago (1 children)

A lot of flatpaks early on wouldn't survive a major point release upgrade or worst case would hold on to dependencies and the user would end up with an unbootable mess after an upgrade.

I haven't seen that recently though.

However I regularly run appimages on my fedora silverblue system so take what I say with a grain of salt.

[–] NuXCOM_90Percent@lemmy.zip 2 points 7 hours ago

If dependencies are articulated (and maintained...) properly, it is very doable and is intrinsically tied to what semantic versioning is actually supposed to represent. So appfoo depends in libbar@2:2.9 and so forth. Of course, the reality is that libbar is poorly maintained and has massive API/header breaking changes every point release and was dependent on a bug in libbar@2.1.3.4.5 anyway.

Its one of the reasons why I like approaches like Portage or Spack that are specifically about breaking an application's dependencies down and concretizing. Albeit, they also have the problem where they overconcretize and you have just as much, if not more, bloat. But it theoretically provides the best of both worlds... at the cost of making a single library take 50 minutes to install because you are compiling everything for the umpteenth time.

And yeah... I run way too many appimages too.