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
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <grarpamp@gmail.com>) id 1SPcni-0008Ds-S2
for bitcoin-development@lists.sourceforge.net;
Wed, 02 May 2012 16:53:15 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.169 as permitted sender)
client-ip=209.85.212.169; envelope-from=grarpamp@gmail.com;
helo=mail-wi0-f169.google.com;
Received: from mail-wi0-f169.google.com ([209.85.212.169])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SPcnh-00041R-Vm
for bitcoin-development@lists.sourceforge.net;
Wed, 02 May 2012 16:53:14 +0000
Received: by wibhm17 with SMTP id hm17so4295065wib.4
for <bitcoin-development@lists.sourceforge.net>;
Wed, 02 May 2012 09:53:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.201.150 with SMTP id b22mr536080weo.103.1335977587799;
Wed, 02 May 2012 09:53:07 -0700 (PDT)
Received: by 10.180.106.229 with HTTP; Wed, 2 May 2012 09:53:07 -0700 (PDT)
In-Reply-To: <CANEZrP17H-E0mWGGjNS2i0079LuRJ9MnVHSPjR_ots2LR7j9bA@mail.gmail.com>
References: <1335808239.18613.YahooMailNeo@web121006.mail.ne1.yahoo.com>
<CALf2ePwm9_aGngzVTKte+3_+yHF=-pcNqTAO0hmkR5rcimEX3g@mail.gmail.com>
<1335810663.39838.YahooMailNeo@web121007.mail.ne1.yahoo.com>
<CALf2ePx_+SaANDfvyuTpv=M8rquvjAqSGV5+Uo=wkYKb-oOrLQ@mail.gmail.com>
<CANEZrP17H-E0mWGGjNS2i0079LuRJ9MnVHSPjR_ots2LR7j9bA@mail.gmail.com>
Date: Wed, 2 May 2012 12:53:07 -0400
Message-ID: <CAD2Ti29mFcGJsojsuSWzC0XxnRWPYAryZU3T3-URiP+1owdO0w@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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
(grarpamp[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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: 1SPcnh-00041R-Vm
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
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: Wed, 02 May 2012 16:53:15 -0000
> it's unclear how best to run this page. It's clear we need one though.
> the right path is probably the middle one - have some descriptions that try to be neutral
Do it in two parts...
- overview, history, architecture model, 'whys'.
- agnostic table of features, platforms, stats, protocols, etc
Last, resolve whether or not bitcoin.org is independant.
It cannot be if it does not accept all lib/client under it's umbrella
or has a lib/client project of it's own. You will hit up against this,
just saying.
> Bitcoin-Qt
> This application is a peer-to-peer client that builds the backbone of the Bitcoin network.
No, they all do this and build it, subject to their feature set.
> It is suited for enthusiasts, merchants, miners, developers
No, all implementations are suited for whoever, subject to their feature set.
> and people who want to help support the project.
Which project, the given client or the bitcoin meme.
> People who run Bitcoin-Qt are first class network citizens and have the highest levels of security, privacy and stability.
Right, anyone who doesn't is unwashed rebel scum, running default
installs of xp, on systems with bad ram, who post their home address,
transaction logs, and pink bits on facebook.
> leave it running in the background so other computers can connect to yours.
Again, a feature set / usage model thing.
> MultiBit
> fast and easy to use, even for people with no technical knowledge.
Hey, we're fast, easy and for noobs, me too.
> It has a...
But at least the backing specifics to that claim are stated.
> Armory
> Armory was partly funded by a community donation drive which raised over $4000.
Yeah, every lib/client will have a donation thing on their own site,
and the developers own real world wallet.
> Electrum
> the privacy level is lower than for other clients.
Not sure of this claim. It's all in the usage. Run your own remote,
use anonymizers, etc. Right?
|
