summaryrefslogtreecommitdiff
path: root/0a/b08718b027375578bc78971774c40eecb106d2
blob: 256a98622f630b8f7a6730467d970fa733ce10a7 (plain)
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
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <etotheipi@gmail.com>) id 1SOwdY-0004mk-Jt
	for bitcoin-development@lists.sourceforge.net;
	Mon, 30 Apr 2012 19:51:56 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.175 as permitted sender)
	client-ip=74.125.82.175; envelope-from=etotheipi@gmail.com;
	helo=mail-we0-f175.google.com; 
Received: from mail-we0-f175.google.com ([74.125.82.175])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1SOwdX-0003IS-7C
	for bitcoin-development@lists.sourceforge.net;
	Mon, 30 Apr 2012 19:51:56 +0000
Received: by wera1 with SMTP id a1so2712283wer.34
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 30 Apr 2012 12:51:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.139.229 with SMTP id c79mr15706090wej.16.1335815509022;
	Mon, 30 Apr 2012 12:51:49 -0700 (PDT)
Received: by 10.180.83.103 with HTTP; Mon, 30 Apr 2012 12:51:48 -0700 (PDT)
In-Reply-To: <1335810663.39838.YahooMailNeo@web121007.mail.ne1.yahoo.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>
Date: Mon, 30 Apr 2012 15:51:49 -0400
Message-ID: <CALf2ePx_+SaANDfvyuTpv=M8rquvjAqSGV5+Uo=wkYKb-oOrLQ@mail.gmail.com>
From: Alan Reiner <etotheipi@gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Content-Type: multipart/alternative; boundary=0016e6dd8d50e699e804beeac8cd
X-Spam-Score: -0.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
	(etotheipi[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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: 1SOwdX-0003IS-7C
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
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: Mon, 30 Apr 2012 19:51:56 -0000

--0016e6dd8d50e699e804beeac8cd
Content-Type: text/plain; charset=ISO-8859-1

Actually I was looking at a screenshot someone sent me because I couldn't
seem to access it even after changing the hosts file (I assumed it was
recent, but I guess not).  It just looked like the regular Bitcoin page
(despite doing a ping on the command line and seeing the expected IP).  Was
there a specific link to click on?    Am I blind?

Is there a process we should use to submit how we think our program should
be represented on the clients page?

-Alan


On Mon, Apr 30, 2012 at 2:31 PM, Amir Taaki <zgenjix@yahoo.com> wrote:

> Are we looking at the same list? Because here is the order I added:
> Bitcoin-Qt, Armory, Electrum and MultiBit. Maybe try CTRL-F5 to force a
> refresh of your browser.
>
> Also about the descriptions: yeah I know. I think it's better to put this
> up first and then have everyone submit their own descriptions and
> screenshots. Otherwise it'll be a nightmare to coordinate until everything
> is perfect. I did message you on IRC today but maybe you were offline.
>
> I didn't copy paste the Armory description from the website because it
> really sounds too spammy like a sales pitch. Here I was trying to give an
> even handed balanced overview of all the clients. For each client I was
> trying to empaphise a 'theme'. Bitcoin-Qt is stability. Armory is advanced.
> Electrum is convenient. MultiBit is ease of use.
>
> ________________________________
> From: Alan Reiner <etotheipi@gmail.com>
> To: Amir Taaki <zgenjix@yahoo.com>
> Cc: "bitcoin-development@lists.sourceforge.net" <
> bitcoin-development@lists.sourceforge.net>
> Sent: Monday, April 30, 2012 7:23 PM
> Subject: Re: [Bitcoin-development] new bitcoin.org clients page
>
>
> Hey, looks good!  I'm glad to see them sorted alphabetically :)
>
> A couple comments:  I don't think the entries for "wallet security" and
> "backups" accurately describe Armory.  Wallet Security should say
> "Encrypt/Offline" or something to to that effect -- after all, offline
> wallets are the holy grail feature of the Armory.  And backups should say
> something like "One-time Printable" if it fits within the box.
>
> Otherwise, I really like the layout and design.  Although despite the fact
> I enjoy being first on the list, I think Bitcoin-Qt should still go first.
>  It is the "reference" client, and I think it's relevant that it is the
> "de-facto" client for the majority of users, and the one with the most
> quality control and stability.
>
> -Alan
>
>
>
> On Mon, Apr 30, 2012 at 1:50 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
>
> Check it :) https://github.com/bitcoin/bitcoin.org/pull/34
> >
>
> >------------------------------------------------------------------------------
> >Live Security Virtual Conference
> >Exclusive live event will cover all the ways today's security and
> >threat landscape has changed and how IT managers can respond. Discussions
> >will include endpoint security, mobile security and the latest in malware
> >threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >_______________________________________________
> >Bitcoin-development mailing list
> >Bitcoin-development@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--0016e6dd8d50e699e804beeac8cd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Actually I was looking at a screenshot someone sent me because I couldn&#39=
;t seem to access it even after changing the hosts file (I assumed it was r=
ecent, but I guess not). =A0It just looked like the regular Bitcoin page (d=
espite doing a ping on the command line and seeing the expected IP). =A0Was=
 there a specific link to click on? =A0 =A0Am I blind?<div>
<br></div><div>Is there a process we should use to submit how we think our =
program should be represented on the clients page? =A0</div><div><br></div>=
<div>-Alan<br><div><br><br><div class=3D"gmail_quote">On Mon, Apr 30, 2012 =
at 2:31 PM, Amir Taaki <span dir=3D"ltr">&lt;<a href=3D"mailto:zgenjix@yaho=
o.com" target=3D"_blank">zgenjix@yahoo.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Are we looking at the same list? Because her=
e is the order I added: Bitcoin-Qt, Armory, Electrum and MultiBit. Maybe tr=
y CTRL-F5 to force a refresh of your browser.<br>

<br>
Also about the descriptions: yeah I know. I think it&#39;s better to put th=
is up first and then have everyone submit their own descriptions and screen=
shots. Otherwise it&#39;ll be a nightmare to coordinate until everything is=
 perfect. I did message you on IRC today but maybe you were offline.<br>

<br>
I didn&#39;t copy paste the Armory description from the website because it =
really sounds too spammy like a sales pitch. Here I was trying to give an e=
ven handed balanced overview of all the clients. For each client I was tryi=
ng to empaphise a &#39;theme&#39;. Bitcoin-Qt is stability. Armory is advan=
ced. Electrum is convenient. MultiBit is ease of use.<br>

<div class=3D"hm HOEnZb"><br>
________________________________<br>
From: Alan Reiner &lt;<a href=3D"mailto:etotheipi@gmail.com">etotheipi@gmai=
l.com</a>&gt;<br>
To: Amir Taaki &lt;<a href=3D"mailto:zgenjix@yahoo.com">zgenjix@yahoo.com</=
a>&gt;<br>
Cc: &quot;<a href=3D"mailto:bitcoin-development@lists.sourceforge.net">bitc=
oin-development@lists.sourceforge.net</a>&quot; &lt;<a href=3D"mailto:bitco=
in-development@lists.sourceforge.net">bitcoin-development@lists.sourceforge=
.net</a>&gt;<br>

Sent: Monday, April 30, 2012 7:23 PM<br>
Subject: Re: [Bitcoin-development] new <a href=3D"http://bitcoin.org" targe=
t=3D"_blank">bitcoin.org</a> clients page<br>
</div><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
Hey, looks good! =A0I&#39;m glad to see them sorted alphabetically :)<br>
<br>
A couple comments: =A0I don&#39;t think the entries for &quot;wallet securi=
ty&quot; and &quot;backups&quot; accurately describe Armory. =A0Wallet Secu=
rity should say &quot;Encrypt/Offline&quot; or something to to that effect =
-- after all, offline wallets are the holy grail feature of the Armory. =A0=
And backups should say something like &quot;One-time Printable&quot; if it =
fits within the box. =A0<br>

<br>
Otherwise, I really like the layout and design. =A0Although despite the fac=
t I enjoy being first on the list, I think Bitcoin-Qt should still go first=
. =A0It is the &quot;reference&quot; client, and I think it&#39;s relevant =
that it is the &quot;de-facto&quot; client for the majority of users, and t=
he one with the most quality control and stability.<br>

<br>
-Alan<br>
<br>
<br>
<br>
On Mon, Apr 30, 2012 at 1:50 PM, Amir Taaki &lt;<a href=3D"mailto:zgenjix@y=
ahoo.com">zgenjix@yahoo.com</a>&gt; wrote:<br>
<br>
Check it :) <a href=3D"https://github.com/bitcoin/bitcoin.org/pull/34" targ=
et=3D"_blank">https://github.com/bitcoin/bitcoin.org/pull/34</a><br>
&gt;<br>
&gt;-----------------------------------------------------------------------=
-------<br>
&gt;Live Security Virtual Conference<br>
&gt;Exclusive live event will cover all the ways today&#39;s security and<b=
r>
&gt;threat landscape has changed and how IT managers can respond. Discussio=
ns<br>
&gt;will include endpoint security, mobile security and the latest in malwa=
re<br>
&gt;threats. <a href=3D"http://www.accelacomm.com/jaw/sfrnl04242012/114/501=
22263/" target=3D"_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/5=
0122263/</a><br>
&gt;_______________________________________________<br>
&gt;Bitcoin-development mailing list<br>
&gt;<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-de=
velopment@lists.sourceforge.net</a><br>
&gt;<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develop=
ment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoi=
n-development</a><br>
&gt;<br>
<br>
---------------------------------------------------------------------------=
---<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today&#39;s security and<br>
threat landscape has changed and how IT managers can respond. Discussions<b=
r>
will include endpoint security, mobile security and the latest in malware<b=
r>
threats. <a href=3D"http://www.accelacomm.com/jaw/sfrnl04242012/114/5012226=
3/" target=3D"_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122=
263/</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div></div>

--0016e6dd8d50e699e804beeac8cd--