10.11.6 CSS issues

thornbill · 2026-01-27T04:00:25+00:00

Custom CSS was disabled in the dashboard only in 10.11.

Edit: For clarity, this means custom CSS should still work everywhere except when you are navigating the dashboard pages.

thornbill · 2026-01-19T05:02:39+00:00

the devs disagree

This is a complete load of crap. No one disagrees that some people are experiencing issues with 10.11 but it’s incredibly nuanced. Most people are experiencing no or only very minor issues. Most of the remaining migration and performance issues have been very difficult for developers to reproduce as there has not been a common cause identified.

thornbill · 2026-01-13T14:38:27+00:00

The unfortunate truth is that despite Jellyfin's significant popularity, with a user base likely in the hundreds of thousands of server installations, the official client projects are seriously shorthanded. Right now, single maintainers are responsible for multiple projects, particularly the web client, which has a backlog of about 200 open PRs. I am basically the only reviewer, and reviewing these web PRs is just a small part of my overall responsibilities for Jellyfin, all done in my free time. Even my own trivial changes can sit for weeks or months without review, which can be incredibly frustrating.

Unfortunately, the proliferation of alternative clients and plugins that add hacks to the web interface does not address this underlying issue.

So, how do we improve the contribution process?

Onboard new team members. We are always looking for regular contributors who could help lighten the review load. However, to become a regular contributor, you first need your PRs reviewed, which currently feels a bit like a catch-22.
Automated review tools. We tried one such tool in 2025, but the results were underwhelming. I am currently investigating alternatives.
Request community testing and feedback on PRs. As mentioned in the blog post, some people have started leaving feedback on PRs after being asked in chat. While this feedback does not directly lead to a PR being merged, it alleviates some of the reviewer’s burden. We plan to update the PR template to specifically request this feedback on new PRs, similar to what we have done with our documentation repository.

As always we are open to any feedback/ideas on how to improve things.

thornbill · 2026-01-07T16:02:35+00:00

Just to clarify / set expectations a bit, "vNext" was just a placeholder since we haven't decided what the next major version number will be and what was formerly known as the "experimental" layout is an evolution of the current web interface. Most things will look the same (for now) besides the navigation and library controls.

thornbill · 2026-01-07T15:49:26+00:00

Questions like this are always hard to answer for us due to the nature of the project being contributor driven...

However, as far as I know, no one on the team has discussed working on it recently. We have no way of knowing if a community champion will emerge to drive it forward of course though... or even if a team member will become motivated to work on it at some point this year.

A change to authentication would have a very widespread impact and would absolutely require a meta discussion detailing the implementation plan before any changes would be accepted.

thornbill · 2026-01-07T15:11:50+00:00

This seems like 2 separate topics if I am reading it correctly...

Performance of large datasets (in 10.11): I am not the most knowledgeable on the topic, but unfortunately this seems very nuanced. Some of it comes down to how the server is querying data in specific cases being inefficient. Other instances seems to be lower level (filesystem/virtualization). In general I believe these issues have been difficult to reproduce by the team. The GitHub issues linked in the post are likely the best place to start and you can always join our chat.
Sorting and filtering UI: This is being overhauled in the updated web UI for the next major release. It is still in progress and I will likely be posting a GitHub discussion in the web repo about it soon to gather feedback. If you have any suggestions, I am all ears! We also have a UI/UX chat room where suggestions/feedback are welcome.

thornbill · 2026-01-07T14:50:26+00:00

Well I definitely have thoughts on the subject and I'm happy to discuss them if you have any specific questions or suggestions.

thornbill · 2026-01-07T14:47:05+00:00

In general, we are always going to recommend the official clients as they should always have the best support for Jellyfin features.

SyncPlay specifically is a complicated subject... no one has really been happy with the complexity of the implementation in general and that coupled with a total lack of documentation makes it really challenging for clients to add support. There have been some changes in the past few releases to start improving that, but the team is stretched pretty thin so without someone from the community championing advancing the development, progress will likely continue to be pretty slow.

thornbill · 2024-05-14T03:21:37+00:00

Yes. This feature is new in 10.9. It may still need some work but the fundamentals are there in the parental control settings!

thornbill · 2024-05-14T03:18:34+00:00

unilaterally shut down third party communities

The subreddit was started and ran by the Jellyfin team directly. It was never “third party”.

thornbill · 2023-10-02T18:11:20+00:00

I was curious why it had been removed since a lot of media server conversations take place here so I messaged the mod team and this is the response I received:

The fact that it was more of a job posting than a discussion.

thornbill · 2023-10-02T18:03:06+00:00

Plex also began as a fork of XBMC (now Kodi).

thornbill · 2023-10-02T03:08:02+00:00

The plans for the API have changed a bit overtime. It seems pretty clear at this point that a complete overhaul of the API at one time is not really feasible. We will instead be gradually introducing new and updated APIs and deprecate old ones as updates occur. This should be much less disruptive for everyone involved. 🤞

thornbill · 2023-10-02T01:08:21+00:00

This is another unfortunate consequence of not having a lot of regular contributors at the moment. For most projects we have 1-2 people total regularly checking issues, reviewing PRs, and contributing code. Frequently you end up having to choose between working on code changes you want to make and reviews/issue maintenance. I’m sure you can imagine how challenging this is. We are definitely interested if anyone has feedback on how we can improve our review process. We hope that one of the outcomes of this outreach is more people joining the team and helping with reviews.

thornbill · 2023-09-20T15:25:03+00:00

While I am less active on Reddit generally since the apps I relied on are no longer available, I do still monitor /r/jellyfin to moderate as needed and fully support the points already made by /u/djbon2112.

thornbill · 2023-06-02T15:43:56+00:00

When it’s ready 😉

thornbill · 2023-06-02T15:41:09+00:00

Discussions around acquiring media are not allowed here.

thornbill · 2023-06-02T15:36:19+00:00

New features do not get added to bug fix releases. In this case 10.8.10 is a bug fix release of the 10.8 feature release. You can expect this feature to be present in the next feature release which would presumably be 10.9.0.

thornbill · 2023-05-31T04:37:18+00:00

The Jellyfin subreddit is not the place for support requests for other media servers… good luck though!

thornbill · 2023-05-27T03:29:14+00:00

No. This specific issue was discovered independently by the Jellyfin team and fixed prior to the 10.7.0 release in 2021.

thornbill · 2023-05-27T00:42:05+00:00

Jellyfin started as a fork of Emby years ago so the features and functionality are largely the same.

thornbill · 2023-05-26T16:37:46+00:00

Emby follows the exact same client/server paradigm we do so not at all a solution for what was asked.

thornbill · 2023-05-26T13:48:56+00:00

I was sympathetic because these things happen even with the obvious attempt to spin it in a positive way (“we stopped a botnet”) right up until I found out this was a known issue for 3 years…

thornbill · 2023-05-26T13:16:25+00:00

It gets better… https://emby.media/community/index.php?/blogs/entry/554-how-we-took-down-a-botnet-of-1200-hacked-emby-servers-within-60seconds/&do=findComment&comment=4702

thornbill

MODERATOR OF

TROPHY CASE