It's by far the most common on public torrent trackers, but I occasionally see it on usenet too. Never bothered to check which indexers they tend to come from.
Sonarr has an advanced setting in "Settings > Indexers > [Your indexer] > Fail Downloads" which you should add "Executables" to. Then these kinds of downloads get automatically marked as failed/blacklisted and a new search and new download is attempted without you needing to manually intervene. You may also have to tweak some conflicting settings on qbit.
Alternatively, if there's a way to have qbit itself mark the download as "Failed" when it detects and refuses to download an executable, that would work too. I don't use qbit personally so I don't know if that's a thing it can be configured to do.
That'll be good for new installs down the line, but I don't think it's something to "wait on" right now. I have around 30 indexers configured in Prowlarr, but going into Sonarr/Radarr and just changing the no-executables setting for each indexer that's actually active only takes a minute or so and never gets reverted.
Seeing great results from bcachefs just makes me more sad that Kent and the other kernel devs couldn't come to an understanding to keep bcachefs in-tree. I want to use it for my storage arrays so badly, but I'm still stuck with btrfs as the only available in-tree filesystem with modern features.
> Seeing great results from bcachefs just makes me more sad that Kent and the other kernel devs couldn't come to an understanding to keep bcachefs in-tree.
I think you are sugarcoating the shit show that was bcachefs's history of involvement in the linux kernel. I mean, do I need to mention that the person was subjected to a code of conduct enforcement action due to his long history of abuse and unprofessional behavior?
Personally I've had 0 issues with the bcachefs dkms packages from distro repos. Unlike zfs it keeps up with upstream kernel releases so it's far less hassle than running zfs dkms.
There's no way my memory of this is reliable anymore, but I also remember my administrator account being chess pieces (and my user account being an orange fish).
It's vibe-slop that popped up just a couple months ago. Aside from inappropriate advertising, why would anyone mention it under a Jellyfin release announcement?
I have a ~40TB library and was still on 10.10.7 because of all the performance issues with 10.11. Upgraded straight to 12.0 and was impressed with how quick and painless it was! As the upgrade instructions warn about, some of my titles disappeared until a rescan added them back, but that was the only weirdness. The whole initial migration only took a few minutes.
Went from 10.11 to 12.0 and had zero issues. Scaleway/Ubuntu/Docker env with 8GB RAM.
Well one small niggle, I had a custom script setup on Caddy that overrides how certain buckets are sorted because my users are too lazy to follow my instructions. They changed the BucketID string in some way but this more to do with me having a custom script dependant on something they don't guarantee.
Hopefully they allow admins to change a users preferences in the future but currently it has to be done at the user level. I'm sure that will be in a future update.
Scaleway Object Storage + rclone. Airbus is switching from AWS to Scaleway and has begun their migration. So they are enterprise grade but seem to have the ease of use of Digital Ocean which I migrated from last year. I get a bit overwhelmed by AWS sometimes in work so it's nice to use a simpler product for my personal setup.
I wrongly assumed I was below version 10.10.7 and tried to "upgrade" to it first as the migration guide said, but this completely blew up and the db migrations failed. I then tried to skip straight to 12 and that also crashed on startup during db migrations, so I just nuked the whole Jellyfin config and started from scratch.
Bit unfortunate how this can even happen, but it's on me for not checking or taking a backup first. The config/db really contain anything important anyways, other than "watched" markers that are already out of sync for me across Emby/Jellyfin/Plex.
Probably 20TB here, 10.11.11, upgrade was smooth and quick. Maybe a few minutes of migration time?
I was actually just getting frustrated with Jellyfin performance and had just told my wife last night that I was switching back to Plex. I didn't realize it was a .11 thing. I just realized that it had gotten worse lately.
12 is working good in the browser so far, but I haven't really put it through the paces fully on Android.
Same here, though my migration took about 10 minutes, and the rescan took about 30 minutes. It also had a few minutes of generating trickplay images, though it must have just been filling in gaps, because generating trickplay images for a large library takes days.
yeah when I started my homelab journey I wanted my windows desktop to also be a server. Over time i moved to pis and other smaller footprint stuff but my media server still is my desktop pc and works via a remote wake up and sleep method over day/night cycle to manage less power consumption. only I use my jellyfin mostly so how can i watch stuff if i am asleep
yep, "just worked". Seems to be much better at properly categorizing some of the more stubborn corners of my library as well. Congrats to Jellyfin maintainers!
Given the number of upvotes my comment got and the other comments where people missed the sarcasm, I wouldn’t be too sure that many people have no trouble distinguishing
The writer can simply say "it was a joke!", cuz we all know someone who uses this pattern regularly when they are trying to squeeze in a non-popular but highly lucrative (to the messenger) position to test the waters.
Either it lands (in which case, it was always meant to be taken literally), or it doesn't land (and can always be walked back as "it was meant sarcastically" or "can't you take a joke?"
The cost proposition to sending this message payload is low, since the messenger can always wiggle their way out (therefore, a "cop-out").
Therefore the need to be more explicit (i.e., /s) in a medium with little nuance affordances for tone and the significantly-increasing risk of such non-popular messages being taken literally (particularly by the also significantly-increasing audience of robots, who themselves may not have the capacity for nuance or irony detection).
