Preach, my brother, preach!

Instead of reading it, just assign one of the agents to read it for you.

I have many questions. The government uses a lot of these kind of things, but they need to go through very specific certification processes that Librem doesn't seem to have gone through.

They are extremely vague here about what the actual connection is. Is it IPsec with a PQ-safe algorithm? How are keys actually exchanged? How are they stored on the hardware?

This could potentially be really cool... but with the information we have, I can't imagine how anyone could actually look at this as a serious product for consideration.

This is a troll, right? The strace for "ls" on my system consists of 1) checking if selinux is enabled (which their re-implementation does not do), 2) openat -> fstat -> getdents64, 3) writing out the information those syscalls gave you.

Jumping from "oh my gosh you can (incorrectly) reimplement ls from a trace of syscalls" to "this means the end of binary blobs" is a level of detachment from reality I've most recently seen from Geoff Lewis. Never mind that the author mixes up eBPF tracing and strace.

Big oof. I hope he has family and friends close enough to pull him out of the spiral.

If you were the CEO of one of his companies, what would you do to limit his ability to access your corporate information and people at this point? Forget whether or not you invite him to a board meeting….

n=1 isn't necessarily data, and I have other questions (the formate concentration of the probiotic variant is 4x over JH1140, but JH1140 is itself a mutant; what's the formate production of an average wildtype strain?). Methanol can cause blindness in as little as 4mL, so the amounts we're talking about are relatively small; 4mL of methanol ≅ 99mmol.

Wouldn't the correct tool here be a multi-armed bandit optimization, like an epsilon-greedy algorithm?

It’s not just the UK who has standardized on these language; the U.S. intelligence community also has a list of required terminology to use for different confidence levels and different likelihoods — and distinguishing between them. It’s all laid out in ICD-203, publicly available at https://www.dni.gov/files/documents/ICD/ICD-203.pdf

I’ve found it very helpful in the same vein as RFC 2119 terminology (MUST, SHOULD, MAY, etc.); when you need your meanings to be understood by a counterparty and can agree on a common language to use.

Very impressive design of the application -- haven't looked into the crypto yet. It reminds me a bit of the design the OpenBSD folks made with letskencrypt/acme-client: https://kristaps.bsd.lv/acme-client/