midmagico
Joined 15 years ago
Joined 15 years ago
The gaslighting in this case is therefore inverted.
Others who were very early (source: I was there and interacted with them) were extremely wealthy investment bankers with a track history of being able to make money, some kinds of cryptographers (Hal, Adam, etc) and others who were ultra-competent, often inventors of new technique in their own right.
It's a well-studied but unfortunately not particularly well-known result that the people most interested in Bitcoin are at the two ends of the expertise spectrum—highly highly financially competent, and financially incompetent people.
You will never hear from most of the highly-competent people because they also recognize that being noisy about owning Bitcoin draws a giant target on their backs. E.g. try and find ArtForz now.
I would offer that the late and very great James Randi's often-repeated comments on ultra high-skilled people being some of the easiest to trick are probably illustrative, and my personal opinion at the moment is that many of these people have been tricked long ago into thinking that Bitcoin is something bad.
(edit) I'm also not answering gmax; I'm answering you, with concrete specifics and an actual example, to inform you about the utility of DKIM even if Satoshi's email provider didn't use them, which you clearly didn't already know.
They don't have to! (re: txid 5d80a29be1609db91658b401f85921a86ab4755969729b65257651bb9fd2c10d)
As a result of timestamping emails with their DKIM into Bitcoin, now even rotated, broken, or released keys can be used to partially authenticate e.g. Google messages. You can see this for example in this project here:
https://github.com/robertdavidgraham/hunter-dkim
And in particular, here:
https://github.com/robertdavidgraham/hunter-dkim/pull/5
So you see, even historical DKIM signatures can act as strong authentication.
The purpose of OP_RETURN was to end the script. It was not designed for rando garbage overlays that are worthless; Satoshi's views on scaling were ambiguous—rather than say it "should" he was instead correcting people who thought you could break consensus by simply setting the value higher. There was absolutely zero communication between Vitalik and anybody about his "plans" to dump an overlay into Bitcoin, and his current story about 80-to-40 bytes is a pure, often debunked lie. There isn't a single communication that Vitalik himself can point to anywhere which shows he was interested in "cooperating" and then core turned him down.
His typical lie was that he was interested in stuffing data into Bitcoin, but then core devs "stopped that" by reducing the amount he could stuff into Bitcoin by half—from 80 to 40 bytes—but when he says that he also never points at any discussion, and in any event the direct history contradicts this—no versions of Bitcoin from back then ever reduced anything. It was only ever an increase: from 0, to 40, to 80 in released versions.
There no evidence these people ever give which shows some lack of cooperation with Vitalik is the reason why Hearn and Andresen "split off" to make an altcoin, which itself is quite the absurdity, and if true just means they would have been ethereum pumpers anyway.. so..
Most new platforms port to Linux, commit drivers to the Linux kernel, and ignore the other platforms. The other platforms don't really seem to bother anymore, unfortunately. Things have bit-rotted to such an extent that FS will destroy large amounts of data and.. nobody seems to notice. Kernel panic reports are ignored. Debuggers fail to set functional breakpoints on native hardware. CPU quirks that need workaround to prevent panics are never committed.
Meanwhile, developing this kind of expertise is about as far from the minds of younger experimenters and hackers now as baking cakes and permaculture gardening were from the 00s hardware hackers decades ago. Not only is it far from the minds of younger experimenters, but even attempting to develop it hits a hard wall of hardcore, draconian behavioural purists, secops fashionistas who deride essentially any burgeoning attempts at writing drivers, and language revolutionaries who rage extensively at people for writing any new code in any language but their own favourite.
The situation is pretty harsh and it's likely not going to get any better anytime soon.
https://github.com/jlopp/physical-bitcoin-attacks
That is objectively, justifiably classifiable as manipulative and destructive.
To clarify: I assert that taxation and a functioning state, and the safety and security of the users of an online currency are absolutely not incompatible with one another—and I'm not even implicitly asserting that the definition of a "functioning state" is some kind of weird ancap impossible libertarian ideal.