My thirteen year old PC is holding up fine. I've replaced the disk (condition of me getting it; it was a disused Windows machine), installed Ubuntu, Debian, then Kubuntu, and upgraded the video card, but beyond that...basically as it shipped from Dell. The last BIOS update was 2013.
I have a similar machine. The only issue is that I haven't bought a video card and the integrated Intel is starting to show its age by not supporting Vulcan.
You'd have to use this version (not sure if they back-licensed old versions) but MIT would mean you wouldn't have to agree to that draconian licensing.
AIUI (I don't have any of this hardware) SteamOS is really meant for the Steam Deck; while there's "basic support" for the ROG Ally, it's not their focus. Bazzite seems to be quite happy to support everything, and AIUI it's frighteningly close to SteamOS (the same customizations, etc.)
It's not "we have SteamOS at home" - it's more like RedHat vs CentOS
This is changing. Valve is actively working with hardware manufacturers to get SteamOS on a number of systems other than the Steam Deck. You can buy a Lenovo Legion Go S with SteamOS today[1], and Valve will be supporting SteamOS on the Asus ROG Ally in the future[2], whether Asus partners with them or not.
As we know or a quick STFW will educate - the "airplane with red dots" refers to the idea that the planes that came back had damage indicated on them with red dots and so the initial idea was that the designers of the planes needed to armor those spots...
When it was really the case that the spots that weren't damaged were the ones that actually needed to be armored, because the planes that took damage there didn't come back.
In this case, the data that survived a selection process ("I just recommended this book that dovetails nicely") is the only data considered, when really all of the data needs to be considered.
I'm seeing this as "you're reading the data wrong" or more accurately "you're barking up the wrong tree"
That dovetails with "Dolphins must be friendly, because we always hear about them pushing drowning sailors to shore, and we never hear anything about dolphins pushing drowning sailors out to sea." Wait a minute...
(Not OP) it's a shorthand to use a company's stock symbol instead of the name, especially if you're worked in the financial industry, where everyone knows what you're talking about or can look it up very quickly.
With public/private key pairs, encrypting anything with the private key means that you use the public key to decrypt that same thing. This means anyone (as the key is public!) can decrypt the thing. So if you get the public key, and if the thing decrypts successfully, then you know that the corresponding private key was used to encrypt the thing. This is considered proof that the private key holder encrypted the thing / sent the message, and that's why everyone calls it "signing" instead of "encryption" - you send the cleartext thing along with the encrypted thing.
For private messages, you encrypt with someone's public key and have them decrypt with their private key. You'd sign it with your key, and that person would verify the signature with your key. That's 4 keys you need to worry about.
This doesn't even begin to consider key rotation, perfect forward secrecy, multiple recipients, etc.
I would say that it's not "new" that presidential power has expanded. That's very new, and every president over my lifetime has expanded it bit by bit.
4547 is just doing so at a much more rapid pace and using obscure laws that no one wanted to take the time to clean up.
I expect that if we get out of this the American populace will insist Congress tighten up its books and repeal and clarify some of its more obscure laws.
> I expect that if we get out of this the American populace will insist Congress tighten up its books and repeal and clarify some of its more obscure laws.
