@tgpo@social.linux.pizza2026-07-22 01:09:18
#Jellyfin Server 12.0 RC3 has been released!
We're inching closer to the next server release!!!!
https://github.com/jellyfin/jellyfin/releases/tag/v12.0-rc3
@tgpo@social.linux.pizza2026-07-22 01:09:18
@tgpo@social.linux.pizza2026-06-18 23:27:21
#Jellyfin for #Roku 3.2.1 is scheduled for release on Friday, Jun 19, 2026 5:00 PM PT
https://github.com/jelly…
@tgpo@social.linux.pizza2026-05-23 17:43:14
@teledyn@mstdn.ca2026-07-23 14:27:29
On My Resignation as #Jellyfin Project Leader | Joshua Boniface, sysadmin
https://www.boniface.me/posts/on-my-jellyfin-resignation/
@tgpo@social.linux.pizza2026-07-20 19:14:27
Important information regarding #jellyfin project leadership changes.
https://forum.jellyfin.org/t-project-leadership-changes
How does this impact the
@teledyn@mstdn.ca2026-07-23 20:47:10
Another run in with cruft in #jellyfin and a strong recommendation to others to read their manual page on filenames very carefully, at least until this notion of uncaught exceptions on missing files is updated to be a mere shrug and flush of associated metadata,and a priority to fix.
What happened was really stupid on my part: I noticed file shares often include an IMDB tag in the filename. I had THOUGHT I had seen {imdb-tt…} in the wild, but it had no effect (so I thought) so I hunted up the guide, and so I corrected them to be [imdbid-tt…]
I can no longer watch those shows: Jellyfin offers the old {imdb-*} and will not register the 'new' [imdbid-*] files, even in the Folders view.
For a wishlist, I'd hope some enterprising coder can roll a db-cleanup script that recognizes a missing file and purges all references. Would be nice if it recognized a name-change-only case and ported the old metadata, but hey, as it is, the only method left is wipe clean rebuild from scratch, so anything at all is welcome.
@tgpo@social.linux.pizza2026-05-18 23:56:11
After 2 years of me hounding him, jimdogx, my fellow #Jellyfin for #Roku maintainer has finally created a method to donate to him.
https://buymea…
@draxil@social.linux.pizza2026-06-26 15:54:26
Having #selfhosted services, like #jellyfin seems extra magic during a major broadband outage!
@teledyn@mstdn.ca2026-07-14 03:15:13
apparently the phenomenon is new with 10.11 #Jellyfin
https://github.com/jellyfin/jellyfin/issues/15384
I also cannot delete the phantom old Twilight Zone, and so cannot see the updates of same name, as I apparently do not have permission to delete a file that isn't there. It wasn't there again today; I wish I wish it'd go away! 😊
@tgpo@social.linux.pizza2026-06-01 23:27:06
@tgpo@social.linux.pizza2026-07-03 19:28:42
@teledyn@mstdn.ca2026-07-16 19:32:14
Content warning: lamenting yet another tech disappointment
Ok, major major stupid flaw in #jellyfin and looks like the only solution is wipe clean the entire dB and reinstall … every time you make an outside change?!
And starting from scratch means copious mislabeled items. It will take me weeks to fix television shows. Admittedly I chose Jellyfin because it appeared to work well sharing legacy files and folders with Nextcloud, and I loved the big-screen apps. It was fun, until I noticed …
But I can't spend my life re-entering metadata, and the family just laughs at the brokenness.
How, no, why on earth would a competent programmer throw an uncaught exception and abort because a file to be deleted has already been removed, or simply renamed? What is the business case for such? Why make an archive write-only, no deletes, no renames, no moves?
Is there a less fragile alternative?
@tgpo@social.linux.pizza2026-06-05 01:01:03
Point of clarification regarding the new #JellyfinJune episode 2 video regarding clients.
In the video it's said the official clients are "just the website packaged..."
That's only true for some of the clients, and certainly isn't true for #Jellyfin for…
@teledyn@mstdn.ca2026-07-14 02:58:02
a #Jellyfin question, that's actually on the forum but unanswered in months so perhaps it's because the fix is easy?
the scans for directory changes do not appear to remove missing files or folders. as a result, as I learned about 'proper' jellyfin file nameing and fixed things so similar titles were not grouped, I end up with many phantoms. Selecting one to watch gives an error, and the log is full of scans reporting things missing. An example now that blocks me, I'd put my Twilight Zone collection up, but then added the '84 series which JF lists as the '64 series in titles etc. I split these, with {imdb-} flags, but all we see are bad links to files no longer there, which also means Metadata cannot 'delete' them.
Is there a fix?
@tgpo@social.linux.pizza2026-07-01 17:20:24
@tgpo@social.linux.pizza2026-05-25 13:07:33
@teledyn@mstdn.ca2026-06-10 22:40:59
@teledyn@mstdn.ca2026-06-08 21:16:59
RE: #NextCloud files with #Jellyfin