Selfhosted

51865 readers

627 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

708

FFS Plex, the server is on my local network (no.lastname.nz)

submitted 4 days ago* (last edited 4 days ago) by BlueEther@no.lastname.nz to c/selfhosted@lemmy.world

340 comments fedilink hide all child comments

Well I already have jellyfin running in a container, just have to figure out how to get mum's TV to work with it I guess

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

[–] TrickDacy@lemmy.world 5 points 4 days ago (23 children)

Imo Plex is worth the lifetime pass if you get it on sale.

All the comments saying Jellyfin is better always puzzle me. I've given it like three chances now and each time it feels just as buggy as the last. And that doesn't even consider the fact that you'll need more steps to expose it to the Internet for remote viewing or the fact that there's literally a list of unaddressed security holes https://github.com/jellyfin/jellyfin/issues/5415

[–] Strit@lemmy.linuxuserspace.show 20 points 4 days ago (9 children)

From one of the Jellyfin devs in the issue you linked, posted in April this year:

Now, let's address this clearly once and for all. What is possible is unauthenticated streaming. Each item in a Jellyfin library has a UUID generated which is based on a checksum of the file path. So, theoretically, if someone knows your exact media paths, they could calculate the item IDs, and then use that ItemID to initiate an unauthenticated stream of the media. As far as we know this has never actually been seen in the wild. This does not affect anything else - all other configuration/management endpoints are behind user authentication. Is this suboptimal? Yes. Is this a massive red-flag security risk that actively exposes your data to the Internet? No.

At this point, this over-4-year-old issue has gotten posted to HackerNews more than enough times and gotten quite enough unhelpful peanut-gallery comments like those above.. We are limiting this issue to Jellyfin collaborators only at this point. Most of the big items are already tracked elsewhere (specifically, unauth playback) or have already been fixed. And many other options are now open to us in a post-10.11 landscape now that we have a proper library database ready.

[–] TrickDacy@lemmy.world -2 points 4 days ago (8 children)

That only addresses one of several items.

[–] Strit@lemmy.linuxuserspace.show 10 points 4 days ago (1 children)

Yes, but it's always the one people come back too.

They mention the other issues are either being tracked elsewhere or already solved.

At the end of the day, it's a community project, done by primarily volunteers, who is not making any money doing this. No VC funding to hire developers to take care of these issues.

[–] TrickDacy@lemmy.world 3 points 4 days ago

I understand there's an explanation for it. Doesn't make these things not things to consider when choosing one's solution

load more comments (6 replies)

load more comments (19 replies)