Upgrade notes for 10.11 RCs
Upgrade notes for 10.11 RCs
Oh, that’s disappointing. I was thinking of eventually using Storj as a second s3 endpoint for backups in addition to Backblaze.
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.
If you want to rip out all existing wiring and add SFP+ with fiber on all your end devices, then yes.
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.
--force-grab-cursor
broke with 3.16.4 and is fixed again with the latest version.
Yay, I’d been having this issue in Baldur’s Gate 3.
And just after I unsubscribed because I got annoyed with the “I also have this issue” comments.
Now to resubscribe and risk a bunch “I’m still having this issue - The fix isn’t released yet, wait until the next release”
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)
For 2d platformers, the virtio GPU with 3d acceleration might be OK.
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.
Why is this here?
Edit: apparently that dude’s been doing multiple of those
3-2-1 rule also applies with external providers
The main unauthenticated action is video streaming, but an attacker would need to guess the correct id by chance.
https://github.com/jellyfin/jellyfin/issues/5415#issuecomment-2825240290
Some of them can be fixed, though you don’t necessarily need to do all of them. Easiest thing is ignoring them as long as everything works.
Get on a few private trackers and make a request
No, it’s just something to be aware of
Looks like they’re generally confused. The license file is GPLv3, the readme claims to be licensed under LGPLv3 and they have those terms. Potentially the terms apply only to official binaries, similar to VSCode.
I think this would require some form of CLA, or they couldn’t redistribute contributed code under their terms.