Four days ago, Andrew Rabert — one of the people who built Jellyfin — quietly left the project. No scandal, no acquisition, no dramatic resignation post. He left because the internal culture made volunteering there unsustainable. The desktop client he had been building for seven months now needs a new name. This story trended on Hacker News today, and it deserves more than a passing glance.
What Rabert Was Building
Rabert started a rewrite of Jellyfin’s desktop client in December 2025. The existing one had real problems: poor HDR support, a Qt maintenance burden that nobody wanted to own. His replacement — jellium-desktop — tackled both. Built on CEF and mpv, it gathered 1,400 stars and 115 forks on GitHub without any official marketing push. Clearly, people wanted it.
However, the Jellyfin organization was not enthusiastic. Only a handful of members backed the direction. The rest made their feelings known. Rabert described the atmosphere as “very negative and increasingly burdensome and restrictive.” He stayed as long as he could. Then, on July 17, he left.
“I lost almost all motivation to dedicate my time to the project,” he wrote in the GitHub issue announcing the change, “which was particularly concerning since it was my passion and default hobby to relax.”
Notably, the project continues under his personal account. It works. It is still being developed. But it will never again be the official Jellyfin desktop client.
Jellyfin Saw This Coming
This is not entirely surprising if you were paying attention. Two months ago, the Jellyfin team published their May 2026 State of the Fin and buried an honest warning inside it. They cited burnout at multiple levels of the development and admin teams, attributed in part to AI-generated pull requests eating review time and to direct user abuse when things break.
“There are real people doing the work,” the post read. Specifically, it asked users to treat maintainers with basic respect. The fact that a project feels compelled to publish that reminder tells you something about what maintainers are actually experiencing.
An anonymous contributor, posting under a throwaway account on Hacker News today, confirmed the pattern: “The constant mocking accusations and hostility toward third-party clients, plugins, themes, and other tools have made Jellyfin’s official spaces unbearable.”
The Open Source Governance Failure
Here is the part that gets skipped in coverage like this: Rabert built Jellyfin. Yet that gave him absolutely no structural protection inside the organization he helped create. Community governance formed independently of him. He had to work within it like any other contributor. When the community’s orthodoxy conflicted with his technical direction, there was no mechanism that said “the founder’s judgment gets extra weight here.”
Moreover, this is not a Jellyfin-specific failure. It is how most open source governance works. The founders code the first version, the community forms around what exists, and governance structures — if they exist at all — reflect the preferences of whoever showed up and cared enough to get involved. That is not always the people with the deepest technical context, or the most constructive instincts.
Furthermore, the numbers are familiar by now but worth repeating. Sixty percent of open source maintainers are unpaid. Sixty percent have quit or considered quitting. Forty-four percent cite burnout specifically. The average unpaid maintainer spends 8.8 hours a week on projects; popular ones push that past 20 or 30. Volunteer hours are finite. Organizational friction eats them faster than contributions can replace them.
The Irony Worth Noting
Jellyfin is having a moment. Plex tripled its Lifetime Pass pricing to $750 in 2026. Searches for “plex alternative” are up 60% year-over-year. Jellyfin holds 51% of the self-hosted media server market. It is winning.
Additionally, that success accelerated its internal pressure. More users means more support requests, more expectations, more entitlement, more friction inside the project. Plex can absorb growth stress with headcount and funding. Jellyfin’s volunteer model has no equivalent buffer. Consequently, the same dynamic that made Jellyfin the clear alternative to a commercializing competitor also made it structurally fragile in a way that commercial software is not.
Rabert built something people depend on. Then he had to leave it because the organization around it made volunteering there untenable. The Hacker News thread is mostly gratitude and well-wishes. Some of it is concern. Almost none of it addresses the governance question — how do you build community structures that protect the people who built the thing in the first place?
That question does not have a clean answer. However, it is the right one to be asking. If you want to support the work Rabert is continuing, you can find jellium-desktop on GitHub. It still needs a name. It still needs people.
