This is optimistic, I see "The cryonics people make a mistake in freezing you (how do we know they don't make lots of mistakes?)"[0] and "The current cryonics process is insufficient to preserve everything"[0] resulting of a product 10% already, seemingly matching the questionnaire as well as possible. They say "under ideal conditions" in the survey, so maybe that rules out cracking of brain tissue or ice growth, but that's not the number practitioners want to know about.
...I'm not sure what this is supposed to mean. Asking about ideal conditions is a reasonable starting point for establishing a baseline, and high-quality preservation is definitely something that can be achieved under laboratory conditions with animal models (e.g. https://www.sciencedirect.com/science/article/pii/S001122401...)
Principles of Vitrification (Fahy PDF linked) p. 48 many practitioners think they have vitrified when they have not p. 45 volume changes of vitrifying agents, possibly in a way that avoids detection (very small scale?).
Covers the second term, "freezing" (quibble quibble) speed and delays in the procedure cover the first.
Your team seems not to be trying to maintain either normally solid/fluid tissue maintaining recoverable gradients or vitrification through an entire cycle below the triple point (with just removable or bio-compatible vitrifying mixtures) so your "goal" might be easier. Is the future AI just going to say you didn't do well enough even if you meet your "goal"?
On the other hand if there's never any point in the cycle where any volume is not either recoverable to health or vitrified, all the AI can say is that cryonics doesn't work period.
All you would get is even more insurance overhead and even higher nominal prices. People who pay cover people who don't, and doctors will get insurance to pay for all their failures.
I think the author's (pugworthy's) intent was to disincentivize doctors who take advantage of fee-for-service.
For example, a few years ago, I started getting Plantar Faucitis. (Basically, foot pain that happens in middle age.) My doctor sent me to a podiatrist, who basically told me to buy new shoes, use inserts, and stop walking around barefoot. That worked, BUT:
The podiatrist also pushed me to do a silicon injection (as in they offered it while they were pulling out the needle and pushing it into my foot), pressured me to come in monthly, and wanted to write a prescription for a painkiller that I didn't need and had side effects. It was clear they were trying to increase their patient load and services as a way to get more revenue.
The coolers get so heavy that they don't make good contact if your motherboard is not horizontal. For mainstream CPUs that's why a cheap closed loop cooler is better.
Makes me wonder why old fashioned flat desktops aren't more popular.. they wouldnt have that issue + the gpu wont have it's fans facing down + it wont be a giant weight hanging off the mobo.
~~~~But your VM TPM won't be signed during manufacturing by a trusted root. No attestation.~~~~
OK I take it back, privacy is one of their specified goals:
> Note that the certificate chain for the TPM is never sent to the server. This would allow very precise device fingerprinting, contrary to our privacy goals. Servers will only be able to confirm that the browser still has access to the corresponding private key.
However I still wonder why they don't have TLS try and always create a client certificate per endpoint to proactively register on the server side? Seems like this would accomplish a similar goal?
> why they don't have TLS try and always create a client certificate per endpoint to proactively register on the server side
That is effectively what Token Binding does. That was unfortunately difficult to deploy because the auth stack can be far removed from TLS termination, providing consistency on the client side to avoid frequent sign outs was very difficult, and (benign) client side TLS proxies are a fairly common thing.
Dude; please stop spamming misinformation, this was already debunked in previous commentary you saw and responded to, showing that the website never sees the raw TPM data at any stage under this proposal.
Session cookies have zero correlation to fingerprinting.
Well, it's a good thing Device Bound Session Credentials (DBSC) as proposed here has no way to actually send said endorsement key anywhere; rending the objection irrelevant. The TPM is only for secure storage as verified by the browser itself, not the website being visited.
> You all don't understand how any of this tech works but you think you do.
We do; and it is specifically called out in the spec that the certificate chain is not submitted, due to the potential for overpowered fingerprinting. As such, this battle, should they make a move to change that, needs to be fought a different day. Fighting against hypotheticals is pointless.
Edit: For the pedantic, fighting against hypothetical things that they could do if they invented something that doesn't exist right now, is pointless.
Edit 2: You can't boil a frog without ecosystem cooperation. The internet isn't going to bow to inconsistent adoption. They already made it clear with WEI they have no interest.
No, fighting against things that have already happened is pointless. We only ever fight against hypotheticals. We fight to avoid something happening that has not happened.
> Edit: For the pedantic, fighting against hypothetical things that they could do if they invented something that doesn't exist right now, is pointless.
But it ALREADY EXISTS on Android[0] and has been proposed by google to be added to chrome before [1]. They are OBVIOUSLY using a boil the frog approach here like forcing android devs to register to sideload [2]. This is obviously designed to slowly roll out these checks small steps at a time. To not see that is to be willingly ignorant.
Actually, I came up with that all on my own after I noted to myself that capture-recapture would work; and it amused me so much that I resolved to try to come up with a proper list filling out the idea. I did get some of the other ideas from LLMs, though.
[0]: https://www.jefftk.com/p/breaking-down-cryonics-probabilitie... “Principles of Cryopreservation by Vitrification” https://gwern.net/doc/biology/2015-fahy.pdf