Yes, both the Ally and the Go are sold in Australia. However it’s also quite easy to order a “grey import” Steam Deck from Amazon, which is what I did. I’m guessing the sheer number of Steam Decks that have been sold into Australia that way are factoring into Valve’s decision, because anecdotally among my peers the Steam Decks owned outnumber the Allys 4:1. Pretty impressive for a device not officially sold here.
Yeah there’s not nearly enough damage to the back of the car for it to have hit so hard as to launch it into the air. Plus you can see yellow paint on the ground where the bollard was clearly laid over. OP is right.
By hand you can feel that you’ve engaged the thread properly. If you just send it with a power tool then dealing with cross threaded fasteners is in your future.
You may know this already from the Steam Deck, but I highly recommend installing protonup-qt which will enable you to install the glorious eggroll versions of Proton. A lot of game cutscenes don’t work with vanilla proton but will with ProtonGE.
Really not good enough from AMD. I wonder if Intel wasn’t a complete dumpster fire right now if they would still cut off the fix at Zen 3 (I doubt it). There’s really no reason not to issue a fix for these other than they don’t want to pay the engineers for the time to do it, and they think it won’t cost them any reputational damage.
I hate that every product and company sucks so hard these days.
This isn’t the first time such a vulnerability has been found, have you forgotten spectre/meltdown? Though this is arguably not nearly as impactful as those because it requires physical access to the machine.
Your fervour in trying to paint this as an equivalent problem to Intel’s 13th and 14th gen defects, and implication that everyone else are being fanboys, is just telling on yourself mate. Normal people don’t go to bat like that for massive corpos, only Kool aid drinkers.
It’s how I’ve always interpreted it. The oft-cited saying is “you can’t outrun a bad diet”
Crowdstrike bypassed WHQL because the update was not to the driver, it was to a configuration file that then gets ingested by the driver. It’s deliberate so they can push out updates for developing threats without being slowed down by the WHQL process.
And that means when they decide to just send it on a Friday with a buggy config file, nobody is responsible but Crowdstrike.
I’ve had two different arch based distros have issues when trying to update after long periods. I also had an Ubuntu server fail completely when doing a major version upgrade and had to restore it from backup. But then again I’ve also had no trouble updating an Ubuntu machine that was a couple years behind.
I’m on Fedora now for my desktop and it’s been great so far, but I also do updates at least weekly. My advice would be if you expect to go months between updates your best choice is probably Debian.