이메일 #231 - #235
원본 출처: Satoshi - Sirius emails 2009-2011
이메일 #231
Date: Sun, 15 Aug 2010 21:37:28 +0100
From: Satoshi Nakamoto <[email protected]>
Subject: [bitcoin-list] ALERT - we are investigating a problem
To: [email protected]
영어 원문
*** WARNING *** We are investigating a problem. DO NOT TRUST ANY
TRANSACTIONS THAT HAPPENED AFTER 15.08.2010 17:05 UTC (block 74638)
until the issue is resolved.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
bitcoin-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bitcoin-list
이메일 #232
Date: Fri, 27 Aug 2010 03:36:43 +0100
From: Satoshi Nakamoto <[email protected]>
Subject: [Fwd: SweepMines now accept bitcoins]
To: Martti Malmi <[email protected]>
영어 원문
-------- Original Message --------
Subject: SweepMines now accept bitcoins
Date: Tue, 24 Aug 2010 19:50:47 +0600
From: Kirill Kisel <[email protected]>
To: [email protected]
Dear BitCoin.
http://apps.facebook.com/sweepmines/ now accepts BitCoins.
This is single-player computer game based on Windows Minesweeper version.
Would you be so kind to add us to the http://www.bitcoin.org/trade page?
Thank you.
이메일 #233
Date: Sun, 26 Sep 2010 16:27:10 +0300
From: [email protected]
To: Satoshi Nakamoto <[email protected]>
Subject: Bookkeeping
영어 원문
+1829€
-23,32€ August hosting bill
-24,40 September hosting bill
이메일 #234
Date: Sun, 26 Sep 2010 17:17:17 +0300
From: [email protected]
To: Satoshi Nakamoto <[email protected]>
Subject: Re: Bookkeeping
영어 원문
> +1829€
> -23,32€ August hosting bill
> -24,40 September hosting bill
--------
+1781,28
이메일 #235
Date: Sun, 03 Oct 2010 21:27:29 +0100
From: Satoshi Nakamoto <[email protected]>
Subject: SMF php code
To: Martti Malmi <[email protected]>
영어 원문
I noticed my custom captcha stuff is gone. I guess it got lost in an
upgrade? What are we doing for captcha now? If we only have default
captcha, we'd be getting flooded with spam accounts. Do I need to
re-integrate the custom captcha stuff or do we have another solution now?