Go read the first few paragraphs of the XLibre repo. For additional context, the gux was roasted by Linus for spreading anti-vax and other shot years ago.
It's so funny how you can crash the whole Windows desktop by mounting a network share, disconnecting from the network and trying to access it.
Found that at a previous job where technicians would frequently connect and disconnect from networks. Also, it's impossible to unmount such a share from explorer or PowerShell. Only the old CMD tool works
Their reasoning is literally the second sentence on that page.
Note however that the 10.Y.Z release chain represents the "cleanup" of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous 10.Y releases 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.
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.
Upgrade notes for 10.11 RCs
https://notes.jellyfin.org/v10.11.0_features