Their reasoning is literally the second sentence on that page.
Note however that the
10.Y.Zrelease chain represents the “cleanup” of the codebase, so it should be accepted that10.Y.Zbreaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous10.Yreleases if required for later cleanup work
Any 10.Y.Z release is cleanup and can include breaking changes. That’s been the case for 10.9 and 10.10 already btw.
Yeah, I also use that, but it’s not quite as easy as the others. Either you’re open to the whole network or you need some form of external key management to add/remove peers from your network.
You always have to learn the processes in a new company, this is just part of that. And if they don’t give you the explanations, training and time to learn, that’s a good sign you wouldn’t want to be at this company.
Maybe also speak to some of your new colleagues, whether they had similar trouble and see if you can improve the process for the next person.
A bunch really, Headscale with Tailscale client, Nebula VPN, Netmaker, Zerotier.
This is the database rework that’s been in progress for a while to remove all the bad inherited database code from when the forked Emby. No more SQL statements in code or plugins, any DB access now goes through the core library. There are a few blog posts in their website with more details.
Oh, that’s disappointing. I was thinking of eventually using Storj as a second s3 endpoint for backups in addition to Backblaze.
You can have a dynamic language that is strongly typed to disallow stuff like this. Like Python for example
They’ve been putting ads on your home screen for years
I had the opportunity to check out a bunch of S3 servers for work. For a quick summary, Garage was much faster than Minio in my tests but lacks advanced S3 features like object locking, versions or retention. Be sure to check what you need before switching.
Also, it’s CLI only as far as I know, so the same as Minio will be.
God really should get on that and fix the design issues with humans
Use one artist for album artist. For the artist field, look up how to properly split entries. This is different for IDv3 vs Vorbis. Split the artists and Jellyfin will handle it fine.
It’s really a wild growth over the years. My current approach is twofold. Netbox to manage devices/VMs and associated info with service deployments using Ansible. You can use the info from Netbox as an Ansible inventory directly.
Previously I tried network diagrams (too low detail) and spreadsheets (terrible to modify) to document machines. And for serviced I’d have an install page on my wiki (apologies, the codeblocks are somewhat broken atm)
Linters won’t necessarily help. You also need a code formatter that screams at you if you intent badly.
/* doesn’t require --no-preserve-root, you’re not trying to delete root after all.
Per the RSS specification the guid field is optional.
And if you do want to provide it, any string works. So just count up from 1, use the title, current date or whatever for that field.
I run basically all my games in gamescope, plus I get HDR for those games that support it.
Why is this here?
Edit: apparently that dude’s been doing multiple of those
Downloaded through HTTPS so end-to-end encrypted