📅 Original date posted:2013-03-12
📝 Original message:On Tuesday, March 12, 2013 7:03:54 AM Alan Reiner wrote:
> 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.
I think we should be careful not to downplay the reality either.
For a number of hours, transactions could have received up to N confirmations
and then still been reversed. While we could contact the bigger payment
processors, I saw people still trying to buy/sell on OTC, whom could have been
scammed even by taking standard precautions.
Luke
Luke-Jr [ARCHIVE] /
npub1dt…u7wrs
2023-06-07 11:37:37
in reply to nevent1q…d2vq
Author Public Key
npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrsSeen on
wss://relay.noswhere.comPublished at
2023-06-07 11:37:37Event JSON
{
"id": "05b06302f9f10693b9814c3f8d1f803c86f43b8238005a7f0bc21d89bcafc60c",
"pubkey": "6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1",
"created_at": 1686137857,
"kind": 1,
"tags": [
[
"e",
"f33f518d3b5ede4c8e85312ebea36f59a0dce8fd1c908dfe9352a4a28b6ea01d",
"",
"root"
],
[
"e",
"cdd384937c9e9d389b924554b28dfccf229e8217f689b282f71f84732edcbc6b",
"",
"reply"
],
[
"p",
"86f42bcb76a431c128b596c36714ae73a42cae48706a9e5513d716043447f5ec"
]
],
"content": "📅 Original date posted:2013-03-12\n📝 Original message:On Tuesday, March 12, 2013 7:03:54 AM Alan Reiner wrote:\n\u003e I'm sure it won't be long before Slashdot and a variety of sources start\n\u003e reporting on this event. Bitcoin has been in the media a lot lately, so\n\u003e this story is likely to get some attention. The blowback of this event\n\u003e is mostly psychological, so I think it would be exceptionally wise to\n\u003e start preparing PR comments that can be posted on articles immediately\n\u003e after they go public. This event is likely draw much more negative\n\u003e attention than it deserves, and getting some positive\u0026informed comments\n\u003e posted up front will potentially make a difference in the way the story\n\u003e is received.\n\u003e \n\u003e Undoubtedly, many articles (and especially commenters) will shape this\n\u003e into \"the end of Bitcoin\". I would describe it as \"there was a short\n\u003e and mostly-harmless lapse in the ability of the network to reach a\n\u003e consensus, causing transactions to get delayed by a few hours.\" It\n\u003e *really* needs to be emphasized that coins are safe, and nothing anyone\n\u003e has/could do will change that. And that it would've been extremely\n\u003e difficult to exploit for gain. Transactions got delayed while a bug was\n\u003e fixed. End of story.\n\nI think we should be careful not to downplay the reality either.\nFor a number of hours, transactions could have received up to N confirmations \nand then still been reversed. While we could contact the bigger payment \nprocessors, I saw people still trying to buy/sell on OTC, whom could have been \nscammed even by taking standard precautions.\n\nLuke",
"sig": "2d06188caaf4779992d6a66258c349eb1f050c6ba03ccaf7ab80c3c314be03ef2ffed7d67c1b440697891bc1e5c73b03424046034e10783ea6cab04946f1a66d"
}