

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.
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
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.
If you wanted an actual European OS lawmakes should go to SUSE and get something done with them.
No, it’s just something to be aware of
Just FYI, unless you absolutely need anonymity from ICANN/the country owning the TLD I wouldn’t choose Njalla. Legally any domain you purchase is owned by them, that’s how they can keep your name from law enforcement requests. However, that also means in any dispute between you and Njalla they can just refuse to service you and keep your domain without recourse.
Normal domain registrars are regulated and if you purchase a domain through them you are its legal owner, if they don’t want your service they must still allow you to transfer the domain somewhere else. Any good registrar provides domain WHOIS protection and will only give out your name to legal requests by law enforcement, so I wouldn’t worry too much about that.
I think that breaks most clients
Not keeping the foot perfectly still
This is great news and I really hope they can build something that achieves those goals.
But JPEG XL is better
I started using Quadlets recently and it’s great to have declarative configs for containers all managed with systemd. It only gets good with Podman version 5 though, 4.4 doesn’t support .pod files, which I use quite heavily.
Not sure what Plex debrid does, but anything managed by a good service manager (like systemd) is more reliable than starting a shell session and hoping it doesn’t die.
Nested VMs stay performant about three levels deep, so do that as well.
I still write most scripts for bash, but for interactive use fish is just so much better out of the box.
Finally, a shell for the 2000s
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)