social.dk-libre.fr is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Any #Jellyfin people want to help me with this PR?
A small improvement to add "now playing" data to the web browser title.
@lenzgr You know what weirdly follows this pattern? #JellyFin. I tried to get off #selfhosted #plex and run a self-hosted JellyFin server. Not only can you not organize your media, they are actively hostile to the concept.
I have hundreds of films and thousands of home movie files I have accumulated over 20+ years. All arranged in a directory hierarchy by my own preference. In Plex, I choose “Library” view, make that the default, and never look at their stupid suggestions again. JellyFin literally cannot do this. And if you ask on the forums (I didn’t bother because dozens already have asked and been answered), they just say that’s not how it’s done. There’s no workaround and no backlog item. Please feel free to pound sand.
You dump everything into whatever, and the app surfaces them in whatever predetermined organization you select. Genre (according to some db somewhere), year, recently added, alphabetical. Anything except my way.
I fought it for a few months. I even paid $2.99/mo for an appletv app that was a better client than the native client. Everything ignored my structure and imposed its own on me.
So this mentality of the-system-knows-best has infected even some otherwise good open source tools.
Jellyfin for Android TV version 0.19.9 brings faster loading of the homepage, fixes the app crashing on invalid Live TV images and solves an issue with the screensaver not working after playing videos. This release will be available on F-Droid, the Amazon Appstore and Google Play in the coming days.
As always, full changelogs on GitHub: https://github.com/jellyfin/jellyfin-androidtv/releases/tag/v0.19.9
Oops, a change made to the frontend in #jellyfin version 10.11.7 causes the mobile Android app not not properly report device information, this can in turn cause the app to refuse logins or play media.
Fixes for both the server and app are ready and I'll try to get them pushed out soon. Excuses for the inconvenience! 🤐
Jellyfin Server 10.11.7 released.
"This release contains several extremely important security fixes. These vulnerabilities will be disclosed in 14 days as per our security policy. Users of all versions prior to 10.11.7 are advised to upgrade immediately."
Working on setting up my own #ErsatzTV IP streams so we can have some auto-generated "channels" of content like Saturday morning cartoons, westerns, etc. that don't require us to manually pick something to watch. Good to have something playing in the background. Settling in on a working systemd service file for it to help lock it down but still keep it functional. Sourcing the media libraries from the #Jellyfin service.
Three of my mini-PC power supplies have died over the last 2–3 months.
That’s half my #K8S cluster unavailable right now. 😓
All three nodes are old Optiplex 3010s, and their #QuickSync support isn’t great anyway. Right now #Plex / #Jellyfin is pinned to a single node with the “newest” CPU for transcoding.
Debating whether to replace the PSUs or just upgrade the dead nodes to newer mini-PCs.
Vereinbarkeit von Windows und Privatleben
Wie viele von uns muss ich im Beruf das Microsoft-Ökosystem mit Windows und O365 nutzen, setze privat aber wo immer möglich auf FOSS und Self-Hosting. Ein kleiner Erfahrungsbericht von meinem Versuch, beides unter einen Hut zu bringen.
#super_productivity #Nextcloud #Jellyfin #Windows #Linux
https://gnulinux.ch/vereinbarkeit-von-windows-und-privatleben
#NAS #vidéo #transcodage
Pour donner un ordre d'idée : Les 20% de CPU affichés là, c'est #Jellyfin en train de transcoder un film AV1 4K (3840x1920) en H264, le tout sur un petit CPU Intel N100 (4 coeurs). Donc ça passe vraiment sans problème.
Il transcode 214 images par seconde.
(Note: c'est de l'encodage matériel QSV dans la config Jellyfin.)