📅 Original date posted:2013-03-12
📝 Original message:I'm sure it won't be long before Slashdot and a variety of sources start
reporting on this event. Bitcoin has been in the media a lot lately, so
this story is likely to get some attention. The blowback of this event
is mostly psychological, so I think it would be exceptionally wise to
start preparing PR comments that can be posted on articles immediately
after they go public. This event is likely draw much more negative
attention than it deserves, and getting some positive&informed comments
posted up front will potentially make a difference in the way the story
is received.
Undoubtedly, many articles (and especially commenters) will shape this
into "the end of Bitcoin". I would describe it as "there was a short
and mostly-harmless lapse in the ability of the network to reach a
consensus, causing transactions to get delayed by a few hours." It
*really* needs to be emphasized that coins are safe, and nothing anyone
has/could do will change that. And that it would've been extremely
difficult to exploit for gain. Transactions got delayed while a bug was
fixed. End of story.
Hell, someone here should submit their own slashdot article about it!
100% chance this hits slashdot -- it might as well be written by someone
who understands it. Similarly, we could be sending sources information
to pre-empt misinformation being spread about it. Unfortunately, I have
to go to bed, so I can't really do much. I just wanted folks to be on
the lookout and be ready to respond to the crazy stuff that's going to
hit the media in the next 12 hours.
-Alan
Alan Reiner [ARCHIVE] /
npub1sm…mnq7h
2023-06-07 11:37:33
in reply to nevent1q…u2x3
Author Public Key
npub1sm6zhjmk5scuz294jmpkw99wwwjzetjgwp4fu4gn6utqgdz87hkqamnq7hPublished at
2023-06-07 11:37:33Event JSON
{
"id": "cdd384937c9e9d389b924554b28dfccf229e8217f689b282f71f84732edcbc6b",
"pubkey": "86f42bcb76a431c128b596c36714ae73a42cae48706a9e5513d716043447f5ec",
"created_at": 1686137853,
"kind": 1,
"tags": [
[
"e",
"f33f518d3b5ede4c8e85312ebea36f59a0dce8fd1c908dfe9352a4a28b6ea01d",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2013-03-12\n📝 Original message:I'm sure it won't be long before Slashdot and a variety of sources start\nreporting on this event. Bitcoin has been in the media a lot lately, so\nthis story is likely to get some attention. The blowback of this event\nis mostly psychological, so I think it would be exceptionally wise to\nstart preparing PR comments that can be posted on articles immediately\nafter they go public. This event is likely draw much more negative\nattention than it deserves, and getting some positive\u0026informed comments\nposted up front will potentially make a difference in the way the story\nis received. \n\nUndoubtedly, many articles (and especially commenters) will shape this\ninto \"the end of Bitcoin\". I would describe it as \"there was a short\nand mostly-harmless lapse in the ability of the network to reach a\nconsensus, causing transactions to get delayed by a few hours.\" It\n*really* needs to be emphasized that coins are safe, and nothing anyone\nhas/could do will change that. And that it would've been extremely\ndifficult to exploit for gain. Transactions got delayed while a bug was\nfixed. End of story.\n\nHell, someone here should submit their own slashdot article about it! \n100% chance this hits slashdot -- it might as well be written by someone\nwho understands it. Similarly, we could be sending sources information\nto pre-empt misinformation being spread about it. Unfortunately, I have\nto go to bed, so I can't really do much. I just wanted folks to be on\nthe lookout and be ready to respond to the crazy stuff that's going to\nhit the media in the next 12 hours.\n\n-Alan",
"sig": "3593c5a6010b02ec1551c1124f5f8304eeb77007c565ce43894cc994055fd54014fb91de7dbe579f2b4a7ada4a334e3a991e43fd7be20b7adde5c2d8be132626"
}