You must log in or register to comment.
- 4 hours
Wow, they’re not holding back!
And Bandcamp officially supporting OpenSubsonic clients wasn’t on my bingo card for sure!
- Courant d'air 🍃@jlai.luEnglish6 hours
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
- Opisek@piefed.blahaj.zoneEnglish4 hours
And you just motivated me to perform a software update maintenance on my server
8 hoursRegardless, 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.
- 3 hours
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: https://github.com/andrewrabert/jellium-desktop/issues/609
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?
- Opisek@piefed.blahaj.zoneEnglish4 hours
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.
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.
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.
Sure, I’m assuming the project has a stable version and a warning or archived banner clearly advertised 😉
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.
- 7 hours
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.
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.
- 2 hours
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.
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.
