1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jim618@fastmail.co.uk>) id 1UsFim-0004gV-OW
for bitcoin-development@lists.sourceforge.net;
Thu, 27 Jun 2013 17:11:00 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of fastmail.co.uk
designates 66.111.4.26 as permitted sender)
client-ip=66.111.4.26; envelope-from=jim618@fastmail.co.uk;
helo=out2-smtp.messagingengine.com;
Received: from out2-smtp.messagingengine.com ([66.111.4.26])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1UsFil-0007cL-0o
for bitcoin-development@lists.sourceforge.net;
Thu, 27 Jun 2013 17:11:00 +0000
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43])
by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 8238F20F22
for <bitcoin-development@lists.sourceforge.net>;
Thu, 27 Jun 2013 13:10:53 -0400 (EDT)
Received: from web6.nyi.mail.srv.osa ([10.202.2.216])
by compute3.internal (MEProxy); Thu, 27 Jun 2013 13:10:53 -0400
Received: by web6.nyi.mail.srv.osa (Postfix, from userid 99)
id 53136298BED; Thu, 27 Jun 2013 13:10:53 -0400 (EDT)
Message-Id: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com>
X-Sasl-Enc: nYs6Qfipt/rbB+t/FpKMaWSQ/omGWjmTDp+l16XSC4UC 1372353053
From: Jim <jim618@fastmail.co.uk>
To: bitcoin-development@lists.sourceforge.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ae8e04c
Date: Thu, 27 Jun 2013 18:10:53 +0100
X-Spam-Score: -1.4 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(jim618[at]fastmail.co.uk)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (jim618[at]fastmail.co.uk)
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UsFil-0007cL-0o
Subject: [Bitcoin-development] Proposal: MultiBit as default desktop client
on bitcoin.org
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 17:11:01 -0000
Hello Everybody,
Over the last few months we have been steadily adding
functionality to MultiBit including:
+ encrypted wallets
+ sign and verify message
+ stability improvements and bug fixes.
As a result of these efforts I think MultiBit is now
suitable for the entry level Bitcoin user. I propose
that we put MultiBit as the default desktop client
on the bitcoin.org "Choose your wallet" page.
I think a typical new user comes to bitcoin.org from a
google search or a Bitcoin news article. We want them to
peruse the bitcoin.org site and try out a wallet. They
should be able to get MultiBit up and running in a tea break.
Then perhaps they get a colleague to send them some bitcoin
from an Android phone by zapping a QR code.
We say: "Welcome to the Bitcoin economy !"
There is plenty MultiBit cannot do of course. However if
in the first ten minutes we get the new user interested
there is a good chance they will go on to explore other
Bitcoin wallets and solutions.
Let me know if you think this is a good idea (or not!)
and if you have any questions.
Jim
https://multibit.org
|
