posted in Selfhosted
Self-Host Weekly (24 July 2026)
selfh.st/weekly/2026-07-24/
selfh.stSelf-Host Weekly (24 July 2026)Jellyfin and Codeberg hurt themselves in their confusionposted in Selfhosted
Self-Host Weekly (24 July 2026)
selfh.st/weekly/2026-07-24/
selfh.stSelf-Host Weekly (24 July 2026)Jellyfin and Codeberg hurt themselves in their confusionReplying to @jogai_san@lemmy.world
Regardless, widespread burnout
If I were a dev, that would be the number one reason I would not publish any app I created. The constant demands from users, the constant integrations, et al, nah…pass. I am grateful for who do, but that’s just not my bag.
Replying to @irmadlad@lemmy.world
One could also not feel obligated to address all requests and just let anyone fork the project.
Isn’t it a bit about the ego to keep running the project while it’s too much to handle?
Replying to @myrmidex@belgae.social
Didn’t downvote ya but, yeah I guess I could do that if I were a dev. Also, I would personally feel responsible for someone’s loss or havoc caused my my app.
Replying to @irmadlad@lemmy.world
Also, I would personally feel responsible for someone’s loss or havoc caused my my app.
Which is one of the reasons I’ll never implement the delete function in the Jellyfin for Roku client.
Replying to @irmadlad@lemmy.world
Sure, I’m assuming the project has a stable version and a warning or archived banner clearly advertised 😉
You can keep running the project and invite people wishing for an XYZ integration to open a pull request. The collaborative nature is kind of a big point of open source imo.
Replying to @Opisek@piefed.blahaj.zone
oh absolutely. I only meant in case it’s physically too much for the repo owner.
There’s no need to feel obligated to carry on to one’s own detriment. The community knows how to move on with it, e.g. ownership transfer or a fork.
Replying to @irmadlad@lemmy.world
He specifically goes on to say it’s primarily from dealing with anti-AI backlash in response to his use of Claude to help (solely) maintain the client: github.com/andrewrabert/jellium-desktop/…/609
GitHubRename the app · Issue #609 · andrewrabert/jellium-desktopThis is no longer an official Jellyfin organization project. It needs a new name & branding. To sum up why it was moved: burnout working within the Jellyfin organization. I was the developer who st...Replying to @irmadlad@lemmy.world
I think I’m going to put a declarations.md that says something like “I made this for me, but I’m sharing it with the world. If you find it useful, use it and let me know! If you find issues, submit request and I’ll look but no promises. And if you want feature X … fork it and build it. The code’s yours, with my blessings. PS: I don’t accept PRs, sorry”.
I code for fun; I’m not looking for a third unpaid job. That’s what parenting is for.
Replying to @SuspiciousCarrot78@aussie.zone
That would be a way to do it. Here it is, works on my machine, it you feel you can use it, knock yourselves out. 30 minute, 30 mile guarantee.
That’s what parenting is for.
Well, that’s a full time job right there. I wish you the very best of luck in those endeavors. You’ll need it.
Replying to @jogai_san@lemmy.world
Jellyfin is the o ly OSS project I’ve walked away from a change. It was a simple exception thrown that could be ignored in very specific circumstances that I remember. I wrote up the change, left several lines of comments, looked up code style, files the bug and PR in the proper way and… Rejected.
My 2 or 3 line PR was nitpicked to hell, I think the fourth round of reviews I just walked away. It wasn’t worth it for me at that point.
So I’m not entirely surprised that they’re feeling burnout. It seemed exhausting getting anything done.
Replying to @scrubbles@poptalk.scrubbles.tech
I never had the feeling the Jellyfin devs were were interested in outside contributions or ideas. A lot of the discussion in issues quickly gets passive aggressive from their side.
Replying to @MaggiWuerze@feddit.org
Yeah, I’m hopeful that changes. I know big projects require stronger leadership, but watching the comments on things made me feel like smaller OSS devs were like me and felt discouraged from helping out.
Replying to @scrubbles@poptalk.scrubbles.tech
I won’t speak for others, but as the maintainer of Jellyfin for Roku, I love contributions from everyone!
Replying to @jogai_san@lemmy.world
Any JellyGlance users here? Is it worth it? This seems like it should be a jellyfin add-on, not a separate service. Still trying to see the real upside, so feel free to enlighten me.
Replying to @jogai_san@lemmy.world
The web is a frightening place these days.
A few seconds after I stood up a public web server, there were bots scanning for
.gitand.env.Mauricio Teixeira (Mastodon)
I got my 20th crowdsec alert (for a banned IP) for today while reading that… I don’t know what’s happening but this week is not a good one
And you just motivated me to perform a software update maintenance on my server
Replying to @jogai_san@lemmy.world
Wow, they’re not holding back!
And Bandcamp officially supporting OpenSubsonic clients wasn’t on my bingo card for sure!
Replying to @jogai_san@lemmy.world
trying setup Opencloud on NAT VPS, no luck, perhaps its need direct ipv4. . . or im just stupid
(navidrome are smooth on this nat VPS)