public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Some PR preparation
Date: Tue, 12 Mar 2013 12:10:32 +0000	[thread overview]
Message-ID: <201303121210.34515.luke@dashjr.org> (raw)
In-Reply-To: <513ED35A.8080203@gmail.com>

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



  reply	other threads:[~2013-03-12 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  7:03 [Bitcoin-development] Some PR preparation Alan Reiner
2013-03-12 12:10 ` Luke-Jr [this message]
2013-03-12 16:55   ` Alan Reiner
2013-03-12 17:35     ` Peter Vessenes
2013-03-12 18:09     ` Gregory Maxwell
2013-03-12 18:39       ` Gregory Maxwell
2013-03-12 19:53         ` Christian Decker
2013-03-12 20:09           ` Peter Vessenes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201303121210.34515.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox