Surround yourself with beautiful things that inspires you to reach for more. Then sweat the little details with the same zest. Not just because it makes for better products, but because it makes for a better you. Be someone who cares. About aesthetics, competence, all of it.
@mattnida Thanks for migrating! The crazy thing is we actually have special code that tries to clean up some of their HTML during import, but it’s not enough.
There's been some games that have provided a bit of relief for the lack of XCOM 3, but MENACE is the first that is actually good.
Chaos Gate was like OK game mechanics is good but I absolutely don't feel anything towards the franchise. When I was kid I enjoyed Franz Kafka; and hated Lord of the Rings. It is such a boring book...
And in Chaos Gat everything rots and is disgusting. There's nothing I enjoy in this story. Almost as bad as Star Wars (BTW, I'm a trekkie).
Phoenix Point look like a game that was never properly finished; i.e., money run out. I've played it hundreds of hours but never to the end because at some point there's too much going on. If the game had been a finished I think it could have been great so I'm waiting for the rumored sequel :-)
@chergert It's less about the CPU struggling to keep up and more about offloading the work to let the CPU idle and use less power. There's a reason all the phones have this hardware. And anyway, there is a measurable performance impact to FDE under some workloads that does go away if you use blk-crypto.
The best feature of hardware offloading like this, is that you can seal up the encryption keys such that the OS / RAM can never see them. That's a huuuuge benefit
@chergert Yeah unfortunately ZFS isn't in a state anyone can really ship meaningfully. We're never going to support it upstream
The good news is that btrfs is very close. We can do what zfs is doing but with native kernel block devices + a filesystem aware of thin provisioning (that's all ZFS is doing internally anyways)
Once we do what we need to in the kernel, ZFS is going to be behind. For instance, it's not using the kernel's blk-crypto support for hardware accelerated disk encryption
"Open weights let every organization match the right model to the right job at the right cost, reserving frontier-scale capability for genuine frontier problems and running efficient, specialized models everywhere else."
Jensen Huang had avoided social media until today, when he posted to X for the first time to share this. Hmm.
@chergert Yes, it would leak metadata just as bad. fscrypt is fundamentally leaky since it encrypts only file names and contents.
The only solution here is to fix thin volumes and then use those w/ the loopback file and proper dm-crypt (or dm-inlinecrypt actually). Good news is that it's being worked on. Bad news is that it requires relatively substantial work in the kernel.