Discontinue exomedia #148
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
security
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#183 Jellyfin security issues
exozyme/exozyme
Reference: exozyme/exozyme#148
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We currently host a Jellyfin server at https://media.exozy.me. However I doubt anyone actually uses it, so should we discontinue it? The maintainence cost isn't high but there are occasional C# issues especially when
dotnet
gets updated in the official repos, since Jellyfin is in the AUR. Of course if we switch to NixOS, we don't have to worry about that. What do you all think?Also, we're using a Jellyfin beta build because the latest release (from several months ago) doesn't support the latest .NET version in the Arch repos.
Since Jellyfin works perfectly currently, we won't discontinue it unless it breaks in the future and becomes a maintainence issue. Plus, Jellyfin upstream hasn't released anything in like a year, so it's not like Jellyfin has required much time so far to maintain.
JellyFin just made a new release, so let's hope it works perfectly so we don't have to discontinue it.
Phew, no problems with the update except a packaging detail that I reported upstream: https://aur.archlinux.org/pkgbase/jellyfin#comment-869224
Reopening because of the security issues in #183.
Done in
0b4d89ad50
and6eb0fb2edf
.