Selfhosted
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!
view the rest of the comments
My aim is to get my friends and family to stop paying for streaming services and if I have to pay for Plex to achieve this then that’s a win.
Jellyfin is nowhere near as feature complete as Plex and not by a long shot. My users don’t like the UI of Jellyfin and setting up for remote access is no trivial feat. With this in mind and my goals Plex is better suited.
So far have 8 users all saving £10-40 a month not going to streaming services.
Jellyfin is open source. You could be helping out.
Best of luck with Plex, though. I would say this is even more writing on the wall but it does not sound like that matters to you.
You’re right I could be helping out I mom the open source side, but I really struggle to even turn on my Pc when not working (mental health) so don’t feel I am the best person to contribute.
This is why my focus has been on getting friends and family to stop spending money on streaming services as every little helps.
You’re correct in that the only thing that matters to me is that people I care about save money. That’s it. I’m in awe of people doing more than me, but we can only do what we feel we are able. Together it all makes a difference.
You sound like me. I hope you can find a way to flip your focus: your time outside work should be way more about you than it sounds like your work life is letting it be.
Maybe you are one of the very few with a meaningful job. If not, consider trying to treat your job like the bullshit it is and use your best cycles outside work on stuff that will really make you happy.
Thanks dude.
I am incredibly fortunate that my boss is a Saint and we literally put ourselves first and the work second. It’s a small company and we are not expected to think about work outside of work and they’ve shown time and time again with their actions that they are good people.
I just don’t have that kind of drive for coding now outside of work as work satiates that desire, which means out of work I can focus on mental health which for me comes from being outside or doing something.
I will say the past isn’t amazing as I’m quite new but has two raises and a reduction in hours in less than 2 years.
The Jellyfin devs have made it clear, that they will not make changes that invalidate existing clients. Rebuilding the things that make sharing content via Plex so much easier would most definitely break client compatability
Citation needed.
The most compelling feature I always get asked if Jellyfin has ala Plex is the discovery/NAT punch for linking people up.
That does not strike me as something that necessarily breaks backwards compatibility. It would require some centralized discovery, and I think that is probably where we run into an issue because if I were the Jellyfin devs, I wouldn't want to have to support that, either.
They argue against most suggestion with the notion, that existing clients can't handle authentication. The devs prefer working clients over a properly secured backend.
You can now extrapolate this idea and every major change that would change the way the API is accessed by clients will be stopped for the sake of continued client compatibility.
It's this old link, eh?
Well, just because they closed the issue (without resolving it), doesn't mean it does not speak to their views on security and client breaking changes
Yup the old one... here's the new one too... still unaddressed
https://github.com/jellyfin/jellyfin/issues/13983