It's not a quick or easy fix. The patch is a 10000 line nightmare. No really it's actually 10k. A lot of that is test code, but there are also significant changes to deep engine internals.
PHP did really really bad memory limit handling. Now it's only really bad.
That looks correct to me if uid 1101 == userC. Sorry, don't really know what it might be then.
Complete shot in the dark, but I would start by comparing podman system info between the two user accounts, with the most importance on the idMappings. Podman is usually configured to use rootless by default, and this can result in wildly different behavior based on whether /etc/subuid and /etc/subgid are configured to give your user IDs or not. See tutorial if your user 1001 is missing.
Modern distro installers tend to give the user created during setup 65536 IDs, but useradd usually doesn't do that by default. This is really distro-specific stuff though and I don't know how modern Fedora handles it, so I might be grasping at nothing here.
It's kind of a spoiler for a spoiler-averse game but Void Stranger has some.
Void Stranger
The game autosaves only between rooms. Quitting the game lets you reset the room without losing a life, and it's a turn-based puzzle game, so you got time for it. But if you repeatedly cheat that way, you find out the developers were keeping track of ways you can abuse this, and you will get punished appropriately.
For a second, I was wondering if it's Dominant Species. But I don't think it had anything resembling human houses or cool UI.
14 layers is insane, but 3 to 5 is on the real low side for a $300B corp with lots of massive studios too. The vision presented is gonna be real awkward for companies working on more than 1 game at a time, or with huge 200+ employee teams. Activision-Blizzard-King in particular, World of Warcraft has a handful of sub-teams that have to coordinate stuff and Call of Duty runs on coordinated yearly releases.
I can easily imagine 7 layers for WoW or 8 layers for CoD. That's not bloat, just the inevitable end-result of Satya Nadella being ultimately responsible for approving the salary of whoever's writing the latest Call of Duty, the main project of a wholly owned subsidiary (the four studios making CoD on rotation) of an acquired company (Activision) of Microsoft's side project gaming division (XBOX).
Another choice quote from the original IGN interview that this is from:
Sweeney: [...] The only way that we can hope for new games coming into the market to be able to succeed when there's so much Metcalfe's Law at play and so many captive audiences in the really big games – you know, Fortnite, Roblox, PUBG Mobile, and a few other really huge ones – it's got to be that those games get momentum by connecting to the economies in other games. I think that can really reinvigorate the market if people are constantly looking to new games and sources of new items that they can earn everywhere and be able to really easily move together with their friends.
Guy got talked into the whole blockchain NFT crap so hard that he's still trying to make it happen, as if it was ever a desirable thing that the best way to get some kind of gear or cool cosmetics in game A involves playing game B instead.
My favorite demo this time around has been Sting & Swing. Bee golf is a cursed concept somehow turned into an Animal Well esque game.
To add to that, even the original paper written with 1999-2007 era SDRAM/DDR/DDR2 is not optimistic about the scenario of a machine that was already powered down at regular operating temperatures:
with the fastest exhibiting complete data loss in approximately 2.5 seconds and the slowest taking an average of 35 seconds
And that only got worse with more advanced RAM, not to mention that they lost almost all of the data far quicker than that with only a couple % of bits surviving that long. For all practical intents and purposes, cold boot against an already-powered-down machine is a myth, the cooling has to be applied while it's on.
One example: https://aur.archlinux.org/cgit/aur.git/commit/?h=oracle-bin&id=eceeb808ef933a66285ea68cefd72c1b5f4374c9 . It seems the AUR team forcepushed the malicious commits out of the repo branches, likely to prevent being accidentally reused by git-bisect in the future, but the URLs still seem to work until they run garbage collection. The author/committer information on each affected commit impersonated a previous maintainer of that particular repository and isn't real.
The whole thing essentially just boils down to adding a cd /tmp; npm install [random crap] post-install hook to every abandoned repository they easily got access to, which itself had a post-install hook to set up malware things. npm has nulled the affected packages, though it took them somewhere around 24 hours to do so. atomic-lockfile was one of them.
Dev post on the forum:
Just be aware that choosing works only in places where there is ambiguity due to belt being perpendicular. Those cases were the cause of problems for blueprint flip reliability.
So there's limits to it.
A different FAQ item mentions Winward NL Limited is in the Cayman Islands, which is a really nice place if you would want to hide such links. But yeah, could also be a bunch of individuals just looking for some extra yachts (bonus irony if they buy them from Gaben's yacht company).