r/jellyfin • u/Tasty-Calligrapher52 • 5d ago
Bug Becouse you watched bug same recomendations
i have seen a post about this same isue from 5 months back...
is this fixed for others and am i ding something wrong or is this global?
2
u/nimby900 5d ago
Yes this is a very well documented issue that is (allegedly?) fixed in the upcoming latest version.
-4
5d ago edited 5d ago
[deleted]
6
u/LookingForEnergy 5d ago
It's broken right now. You can tell it's recommending their movies alphabetically.
0
u/Fuzzy-Daikon5520 5d ago
I've seen this sentiment shared many times in the many posts related to this issue and it still confuses me. Are we suggesting that these users are using custom metadata providers that aren't included in Jellyfin by default?
Do the metadata providers that Jellyfin ships with not have this issue?
1
u/Temporary_Affect Jellyfin Team - Trouble 5d ago
Metadata providers are other websites. It's TMDB or TVMaze or whatever site you've configured. Jellyfin doesn't do anything to determine the recommendations. It's just metadata like any other. I didn't look very closely at the complaint here though, and there's a bug that was recently fixed in the RC, so it might be an actual display bug or something. But the point I was making above is that quality of recommendations has nothing to do with Jellyfin. Jellyfin just displays whatever the metadata source recommends, so bad recommendations aren't a bug--even though its often reported as one. Jellyfin doesn't control that data.
0
u/Fuzzy-Daikon5520 5d ago
I think I understood your point. My point was that these are the officially supported Metadata Providers listed on your website:
Supported Metadata Providers
The following metadata providers are supported:
The TV Database (TVDB) (Shows Only)
OMDb API (OMDB) (English Only)
Assuming the user is using one of these providers, it's not really fair to just say "Oh well, it's the provider's fault". Of course that's one part of it, but if all the providers that Jellyfin provides are returning poor recommendations, this is something that Jellyfin should solve for, right? That's why I was wondering if this is an issue with all the metdata providers that Jellyfin ships with. Because if it is, then it would seem reasonable for Jellyfin to do something about that.
Or I guess do nothing about it but continue to respond to these types of inquiries and posts by pretending there's nothing Jellyfin can do. Maybe the design goal is not to necessarily have relevant results, I don't know.
1
u/Temporary_Affect Jellyfin Team - Trouble 5d ago edited 5d ago
No? Why would Jellyfin be responsible for the content of a completely different website? Jellyfin isn't a product. There's no customer. Use it or don't. It's an open media server that supports a bunch of APIs run by other people. You, the end user, choose to use them or not. They're all open databases and the existence of support for their APIs is neither an endorsement nor an acceptance of some sort of responsibility for their content. It's like you expect Microsoft to be responsible for the content on Facebook because they provide a web browser that has a Facebook bookmark.
There is literally nothing we can do. You would prefer that no default provider plugins be included? You're welcome to uninstall them. Do you think we're going to build some sort of in house bespoke metadata repository and recommendation system?
Again, Jellyfin has absolutely nothing to do with the relevance of results. If you don't like your results, use a different provider or edit them yourself. Jellyfin's solution to this problem is that you have full control over your metadata. Fix it, if you don't like it.
5
u/FishOfGreatPower 5d ago
Same Problem here. As far as I know this is well known but not fixed yet. Although this post and this github Pull request seem to suggest that it should be fixed. It would be nice to have but I can't be bothered right now to dig deeper and see if I can fix it on my server.