The bigger problem is that this model is inherently flawed. Even if end-to-end encryption with browser crypto were implemented, there is never any security since the code in the browser can simply be swapped with compromised code that diverts the plaintext somewhere.
I've been forced to use this service, by way of healthcare professionals just disclosing correspondence to this service without asking for my consent.
> there is never any security since the code in the browser can simply be swapped with compromised code that diverts the plaintext somewhere.
This is not the case in the land of DICE-like key derivation; see TKey protocol for example. You can download and run an actual rv32 program on actual FPGA over WebUSB without having to worry about its provenance. If the program is modified, firmware will derive a completely different key.
I'm simply pointing out that web standards allow for secure end-to-end communication, and more, in fact they happen to allow arbitrary cryptographic constructions—as long as the program itself never changes.
Not necessarily. You can run TKey in qemu :-) etc. The hardware aspect is what makes it easy to use, with WebUSB and all. The derivation algorithm is key. And it takes program binary as parameter to Blake2 hash function.
CPAP makes breathing harder than normal. It's antiquated technology, superseded by something called bilevel-CPAP (BiPAP) which has the quality that it makes breathing actually _easier_. It's slightly more expensive than plain CPAP so insurance and doctors withhold it from the patients and try to keep it a secret.
CPAP is NOT "antiquated technology." It has different indications from BPAP. Some people tolerate one better than the other. We are not "keeping one a secret."
He did say that having successive revisions is doing it wrong. Literal quote (from the translation)
"So then you get these version numbers, even with decimals, version 2.6 or 2.7. That's nonsense. While version 1 should have been the finished product."
So I think the nuance you are trying to make is unsupported. He did mean: think it through once, write it out once, version 1. Done.
Of course there is no hardware emulation, so all Windows binary code is running natively with no performance drop. That's why it was called WINE. But still there are two meanings of the word. Hardware emulation or OS emulation at API level.
That's Jason Sazama a.k.a. TheLankyLefty27. He's good, he knows about UARS and flow limitation. His experience with bilevel/ASV modalities is very limited though.
I've been forced to use this service, by way of healthcare professionals just disclosing correspondence to this service without asking for my consent.
Smeerlappen.