2,787 karma · joined November 23, 2017
Which the cop will promptly ignore and take the money anyway.
If you do, consider whatever money you put in to be lost and plan accordingly.
But iirc it started off with a whole history of physics grad students offing themselves when their experiments didn’t work out or confirmed negative results, not just the one you are referring to.
Actual physicist here. We LIVE for that moment when the experiment does something unexpected. That’s when new discoveries are made, and our understanding of the world turned upside down. We got into the field hoping for a moment like that to happen within our lifetime. Suicide? Hell no, we’d be giddy for excitement wanting to see what happens next.
Liu Cixin doesn’t have the faintest clue about scientists and what motivates them. I put down the book as soon as that part happened.
Do you have a cite for the galactic spin thing?
Regardless, my question was about the part of the quote which said: "which we now know as wrong."
What aspect of the cosmological principle, strong equivalence principle, or the universal application of physical law do we now know to be be wrong?
What is this in reference to?
Longevity escape velocity is achievable within our lifetimes.
First of all there is nothing new or unique about the above. Cypherpunks we’re discussing digital gold for a decade and a half prior to Bitcoin.
Second, during this time and until years after the release of Bitcoin, he has been on record for exploring, pushing, and supporting the cost-value theory of money. This is the erroneous idea that a unit of digital gold should represent directly somehow the cost of production. E.g. a Bitcoin that is twice as hard to mine should be worth twice as much. Nick’s whole theory of digital money (the bitgold in the article) is built upon this. In the years after bitcoin’s release he was fiercely critical of it for this reason. However we now know that rejecting this idea was Satoshi’s key innovation and the reason it works at all.
Python3 unnecessarily broke compatibility in many places. Yes I agree that using bytes.fromhex() and .hex() are better design choices. But requiring manual inspection and updating of all strong manipulation code for the transition was an outrageous requirement, particularly for a dynamic language that doesn’t (or at least didn’t at that time) have compile-time type checking to catch such errors.
(With the technical caveat that doing at least two serial hashes does improve the properties of the hash function by defending against length extension attacks. That's why things like HMAC do multiple chained hashes. But it does zilch for collision or preimage resistance.
But yes I agree, and that’s why my two slow burn start ups have been related to astroid mining and molecular nanotechnology.