SaaS & Software·Jul 20, 2026

Jellyfin founder Andrew leaves team

joshuaboniface Offline Posts: 118 Threads: 27 Joined: 2023 Jun Reputation: 24 Country: 10 hours ago (This post was last modified: 10 hours ago by joshuaboniface. Edited 2 times in total.) Hello everyone. Effective yesterday, Anthony and I d

Hacker News2 min readSingle source
Jellyfin founder Andrew leaves team
Image · Hacker News
The gist
5-point summary · 1 min

joshuaboniface Offline Posts: 118 Threads: 27 Joined: 2023 Jun Reputation: 24 Country: 10 hours ago (This post was last modified: 10 hours ago by joshuaboniface. Edited 2 times in total.) Hello everyone. Effective yesterday, Anthony and I d

  • joshuaboniface Offline Posts: 118 Threads: 27 Joined: 2023 Jun Reputation: 24 Country: 10 hours ago (This post was last modified: 10 hours ago by joshuaboniface.
  • Effective yesterday, Anthony and I decided to depart from the project, myself as Project Leader, and he as a core team member.
  • After 7.5 - nearly 8 - years, it's been a long time since I've been able to give much of my free time to Jellyfin.
  • 7 jellykrabbypatty Offline Member Posts: 114 Threads: 32 Joined: 2025 Mar Reputation: 2 Country: 3 hours ago Thank you for everything!
  • 1 Cutter Offline Junior Member Posts: 14 Threads: 4 Joined: 2023 Jun Reputation: 0 2 hours ago Thank you very much Joshua, Anthony and Andrew for the time and effort you've put into this project.

joshuaboniface Offline Posts: 118 Threads: 27 Joined: 2023 Jun Reputation: 24 Country: 10 hours ago (This post was last modified: 10 hours ago by joshuaboniface. Edited 2 times in total.) Hello everyone. Effective yesterday, Anthony and I decided to depart from the project, myself as Project Leader, and he as a core team member. This is in addition to the resignation of Andrew on Friday. We leave the project in the very capable hands of the remaining team who have been driving the project for many years now. Joshua: For me personally, it was just time for a change. I simply could no longer provide the effort (mental or time-wise) that the role demanded, and thus I was not performing my duties to an acceptable degree, facing severe burnout, and risks to my mental health. It was time to step aside. Hand-off is ongoing and is amicable, and there is good communication lines, so there is little to no risk of a hostile fork or anything of that nature. Jellyfin will continue for a long time to come, just not with me at its head. When I started Jellyfin, I thought it would be something used by a few hundred, or maybe if we were lucky, a few thousand, users. We might put a few pet features in, and do a bit of cleanup, but really, I didn't expect much. Now here we are 7-and-a-half years later, and it's the #1 FLOSS media server, a truly viable alternative to Plex for literally millions of server administrators and probably 10x that many individual users, and we've left our parent project completely in our dust. We've proven that FLOSS works, and is in demand. I truly hope Jellyfin outlives me, and I trust those in the team to keep the philosophy and code alive. For the last time, happy watching all! Anthony: My particular reasons are a bit different, so I figured I would post as well. For myself, though I don't touch much code these days, I do a lot to manage things in the backend and with App Stores/etc. After 7.5 - nearly 8 - years, it's been a long time since I've been able to give much of my free time to Jellyfin. My life is changing and I've got other things that must take priority. I am fully committed to a smooth transition, which is something I've wanted for a long time anyway. Even if the transition takes a year, I'm still down to do that. I want Jellyfin to succeed, and it should. 7 jellykrabbypatty Offline Member Posts: 114 Threads: 32 Joined: 2025 Mar Reputation: 2 Country: 3 hours ago Thank you for everything! I complain about Jellyfin a lot and have no idea what I'm doing. 1 Cutter Offline Junior Member Posts: 14 Threads: 4 Joined: 2023 Jun Reputation: 0 2 hours ago Thank you very much Joshua, Anthony and Andrew for the time and effort you've put into this project.

Integrity note  ·  Xela does not rewrite or paraphrase article content. The excerpt above is the source publication's own words, sanitized for display. For the full piece — including any quotes, charts, or images — read it at Hacker News. Xela's rewritten version is off for this story, so there's no editorial angle attached — you're getting the source's reporting unfiltered. When the rewrite is on, we add a What this means block underneath with the operator/trader takeaway.

What people are saying

Discussion

Hot takes

0/280

Loading takes…

Comments

Discussion · 0

Sign in to comment, like, and save articles.

Sign in

Loading comments…

Keep readingSaaS & Software desk
See all in SaaS
Show HN: Ex Situ – open-source spatial index of displaced cultural artifacts
·

Show HN: Ex Situ – open-source spatial index of displaced cultural artifacts

Hi, I designed and developed a spatial index that maps museum artefacts as connecting arcs/hyperlinks from their origin site to institutional location/sources. The Index specifically looks at western/euro-american institutions and maps their collection categorised by them under Islamic art, Asian/African art, ethnological collections, Middle East, South America etc. Started as my MA thesis in 2022, kept building since, mostly solo with a little funding. Fully open source, self-hosted, AGPL-3.0, Next.js + Deck.gl on the frontend, Strapi backend, Python ETL pulling from museum open-access APIs. Currently indexing over 100k artifacts from all over the world, across 8 collections (Met, V&A, SMB Berlin). Recently added an md export so researchers can download provenance data for a filtered set of artifacts. The infrastructure is conceptualized as an indexer, not a hoster. Even images are kept as URLs pointing to the source institutions. It's connective tissue between archives that were never designed to speak to each other, with an origin-first search UI concept. The data model is on purpose flat, to avoid encoding problematic taxonomies, and routes researchers directly to the source giving responsibility to the source institutions rather than duplicating institutional data. It indexes the relationship between origin sites and destination collections. Coming from a design background, taking this project from prototype to production app has been incredibly rewarding, but honestly it’s getting a little bit overwhelming to scale alone. I would love community’s feedback on performance scaling, any code contributions, data pipelines for missing museum apis or general feedback. Repo: Live:

Hacker NewsSingle source
Newsletter

Track saas & software every morning.

Daily digest tuned to this beat. The 5 stories most worth your time. Unsubscribe anytime.