From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UFO2a-0007rM-O0 for bitcoin-development@lists.sourceforge.net; Tue, 12 Mar 2013 12:10:48 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1UFO2Y-00014C-Vn for bitcoin-development@lists.sourceforge.net; Tue, 12 Mar 2013 12:10:48 +0000 Received: from ishibashi.localnet (unknown [173.170.142.26]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 4D0F827A2968 for ; Tue, 12 Mar 2013 12:10:41 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Tue, 12 Mar 2013 12:10:32 +0000 User-Agent: KMail/1.13.7 (Linux/3.7.3-gentoo; KDE/4.9.5; x86_64; ; ) References: <513ED35A.8080203@gmail.com> In-Reply-To: <513ED35A.8080203@gmail.com> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201303121210.34515.luke@dashjr.org> X-Spam-Score: -2.6 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1UFO2Y-00014C-Vn Subject: Re: [Bitcoin-development] Some PR preparation X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 12:10:48 -0000 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