For the lazy.
75 karma · joined September 5, 2026
For the lazy.
What communities do this? Can I do this on my laptop too to trial it?
Does 80% mean "tastes like a dull chocolate bar, but still basically a chocolate bar", or more like "like a nice chocolate bar but somehow 20% less enjoyable in some looser way"?
Perhaps this is why I can't identify the beat in the music.
I'm just not interested in closed ecosystems like Oculus.
That said, I have barely looked at VR so much that I'm not sure whether to bother with the Steam Frame.
Is it just for gaming/movies?
If people have an "inner taste" or "inner hearing", why bother eating a sweet or playing music?
> Asked what sits beside the television, they answer without hesitation, but “we experience these as an awareness of a set of spatial facts.”
This helps me understand what little I do seem to have.
Maybe the most vivid thing that I can imagine is the world map, but... I wouldn't call it visual. But I can recall that Europe is east of US, and Italy looks like a boot.
Perhaps it is just spatial facts.
I expect as LLMs penetrate further, we'll see much more of it, continually running, and doing more 3D work.
Call SOS on your telegraph?
How is "offline e-reader" handled? Does CUPS retry?
Do you do this outside of your LAN?
+1.
And it's worth celebrating the underlying technologies that enable this: ESP32, and RISC-V.
Anyone know what's needed for eink to become cheaper?
Sorry to have missed that!
That said, TPM quotes are attesting the value of TPM PCRs which are just registers of hashes (representing the state of the machine).
When making a CSR, you can use https://tpm2-tools.readthedocs.io/en/latest/man/tpm2_certify... to attest a key is TPM-resident.
I think your central thesis is that at the time of TLS establishment, why not use PKCS11 (with a cert signed by a CA that has validated a TPM certification), and I agree: services should probably integrate via PKCS11.
> even if you don't have the keys you may still control the implementation
The sorts of places that care about remote attestation also care about insider risk.
PKCS11 doesn't allow you to attest that the key is resident in the PKCS11 provider, which as you say, the author alludes to, but doesn't cover.
> with real TPM, the key could be locked to a specific configuration register value, which makes less sense for VMs.
A vTPM is as real as a physical TPM chip.
The question is which TPM endorsement certificate CAs you are willing to trust.
For some that might the manufacturer of TPM chips, for others it might be their VM provider. (For some, none: for some both!)
Trusting their VM provider isn't so crazy if the VM provider is able to influence the guest code anyway.
Not suitable for servers, since it's such an easy DoS vector.
ARM TrustZone, for example, can run this OSS TPM: https://github.com/OP-TEE/optee_ftpm
I expect there are equivalents for Intel/AMD.
What is the author's model of a company?
To be clear, I'm not saying it doesn't. I'm saying I don't understand.
This might oversell the agency that practicioners have.
Sandboxed zero-install delivery will outcompete anything with more frictionful installs.
It's probably not the right model for a pacemaker though.
Web/JS has been a double-edged sword for FOSS: sure, I can run a free OS, but if most of my "apps" happen to be JS that I can't practically control, then I have won a battle and lost a war.