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
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <g.rowe.froot@gmail.com>) id 1SPfJz-00064B-PP
for bitcoin-development@lists.sourceforge.net;
Wed, 02 May 2012 19:34:43 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.175 as permitted sender)
client-ip=209.85.160.175; envelope-from=g.rowe.froot@gmail.com;
helo=mail-gy0-f175.google.com;
Received: from mail-gy0-f175.google.com ([209.85.160.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SPfJx-0000jp-EE
for bitcoin-development@lists.sourceforge.net;
Wed, 02 May 2012 19:34:43 +0000
Received: by ghbz2 with SMTP id z2so1261460ghb.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 02 May 2012 12:34:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.152.41 with SMTP id c29mr18935818yhk.64.1335987275882;
Wed, 02 May 2012 12:34:35 -0700 (PDT)
Sender: g.rowe.froot@gmail.com
Received: by 10.236.25.98 with HTTP; Wed, 2 May 2012 12:34:35 -0700 (PDT)
In-Reply-To: <1335986730.68336.YahooMailNeo@web121007.mail.ne1.yahoo.com>
References: <1335808239.18613.YahooMailNeo@web121006.mail.ne1.yahoo.com>
<201205020931.01718.luke@dashjr.org>
<CAD2Ti2_AUG7zmhwrg1GK9iDOgAh5RNrSEGvJefWCc0Uo=-GQbw@mail.gmail.com>
<201205021230.46349.luke@dashjr.org>
<CAD2Ti29NGc7F1_w5VgKm565CXwhrFPZvMx4BgE_5PVbh0SYU5w@mail.gmail.com>
<CA+8xBpczLTCzikGr62K-4paxecOTtcxFPygQsp7JRg_0DwvMEQ@mail.gmail.com>
<1335986730.68336.YahooMailNeo@web121007.mail.ne1.yahoo.com>
Date: Wed, 2 May 2012 20:34:35 +0100
X-Google-Sender-Auth: 0qj416ImA2Y9btIvWA2SB5KHHRk
Message-ID: <CAKm8k+0pxiKvRp8BokQ+dt-3Ttu7KsdichSqav8qZiv_p6coFQ@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=20cf303f6d3800dede04bf12c7b2
X-Spam-Score: -0.5 (/)
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
(g.rowe.froot[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1SPfJx-0000jp-EE
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 19:34:43 -0000
--20cf303f6d3800dede04bf12c7b2
Content-Type: text/plain; charset=UTF-8
How about keeping it simple?
Bitcoin-Qt
* Requires the entire blockchain
* Standalone client
* Designed for continuous operation
* Available for Windows, Mac, Linux with installer
* Developed in C
* Website: https://bitcoin.org
MultiBit
* Requires a reduced blockchain
* Standalone client
* Designed for occasional use
* Available for Windows, Mac, Linux with installer
* Developed in Java
* Website: http://multibit.org
Armory
* Requires the entire blockchain
* Dependent client of Bitcoin-Qt
* Designed for occasional use
* Available for Windows (64-bit only), Mac, Linux (self-build)
* Developed in Python
* Website: http://bitcoinarmory.com/
Electrum
* Requires no blockchain
* Dependent client of Bitcoin-Qt (on server)
* Designed for occasional use
* Available for Windows, Linux (self-build)
* Developed in Python
* Website: http://ecdsa.org/electrum/
Bitcoin Wallet (Android client)
* Requires a reduced blockchain
* Standalone client
* Designed for occasional use on mobile
* Available for Android only
* Developed in Java
* Website:
https://play.google.com/store/apps/details?id=de.schildbach.wallet&hl=en
On 2 May 2012 20:25, Amir Taaki <zgenjix@yahoo.com> wrote:
> This is like the most annoying thing about email. Often with group emails,
> we'll be having a conversation then someone will click reply instead of
> group reply and the convo will go on for a while. Eventually I'll realise
> the persons are missing and add them back in.
>
> On Yahoo mail (which I use for spam/mailing lists), to do reply all
> involves clicking a tab, scrolling down and clicking Reply All. Normally I
> instead go through the steps of reply, delete To, re-enter bitco... select
> drop down, click send.
>
> Anyone know how to make reply all the default in mutt? And how can I
> exclude it from re-including my own email when I do a group reply so I
> don't get the same email again.
>
>
>
> ----- Original Message -----
> From: Jeff Garzik <jgarzik@exmulti.com>
> To: grarpamp <grarpamp@gmail.com>
> Cc: bitcoin-development@lists.sourceforge.net
> Sent: Wednesday, May 2, 2012 7:29 PM
> Subject: Re: [Bitcoin-development] new bitcoin.org clients page
>
> On Wed, May 2, 2012 at 12:58 PM, grarpamp <grarpamp@gmail.com> wrote:
> >> Try "Reply to All"
> >
> > That puts the sender in 'to' and list in 'cc',
> > which dupes to the sender and eventually
> > blows out the to and cc lines as everyone
> > chimes in and doesn't trim. 'reply to' solves
> > most of that. assuming the list sw can do it.
>
> "Reply-To" Munging Considered Harmful
> http://www.unicom.com/pw/reply-to-harmful.html
>
>
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
>
>
> ------------------------------------------------------------------------------
> 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
>
--20cf303f6d3800dede04bf12c7b2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div>How about keeping it simple?</div><div><br></div><div>Bitcoin-Qt</div>=
<div>* Requires the entire blockchain</div><div>* Standalone client</div><d=
iv>* Designed for continuous operation</div><div>* Available for Windows, M=
ac, Linux with installer</div>
<div>* Developed in C</div><div>* Website: <a href=3D"https://bitcoin.org">=
https://bitcoin.org</a></div><div><br></div><div>MultiBit</div><div>* Requi=
res a reduced blockchain=C2=A0</div><div>* Standalone client</div><div>* De=
signed for occasional use</div>
<div>* Available for Windows, Mac, Linux with installer</div><div>* Develop=
ed in Java =C2=A0</div><div>* Website: <a href=3D"http://multibit.org">http=
://multibit.org</a></div><div><br></div><div>Armory</div><div>* Requires th=
e entire blockchain</div>
<div>* Dependent client of Bitcoin-Qt=C2=A0</div><div>* Designed for occasi=
onal use</div><div>* Available for Windows (64-bit only), Mac, Linux (self-=
build)</div><div>* Developed in Python</div><div>* Website: <a href=3D"http=
://bitcoinarmory.com/">http://bitcoinarmory.com/</a></div>
<div><br></div><div>Electrum</div><div>* Requires no blockchain</div><div>*=
Dependent client of Bitcoin-Qt (on server)</div><div>* Designed for occasi=
onal use</div><div>* Available for Windows, Linux (self-build)</div><div>
* Developed in Python</div><div>* Website: <a href=3D"http://ecdsa.org/elec=
trum/">http://ecdsa.org/electrum/</a></div><div><br></div><div>Bitcoin Wall=
et (Android client)</div><div>* Requires a reduced blockchain</div><div>* S=
tandalone client</div>
<div>* Designed for occasional use on mobile</div><div>* Available for Andr=
oid only</div><div>* Developed in Java</div><div>* Website: <a href=3D"http=
s://play.google.com/store/apps/details?id=3Dde.schildbach.wallet&hl=3De=
n">https://play.google.com/store/apps/details?id=3Dde.schildbach.wallet&=
;hl=3Den</a></div>
<div><br></div><br><div class=3D"gmail_quote">On 2 May 2012 20:25, Amir Taa=
ki <span dir=3D"ltr"><<a href=3D"mailto:zgenjix@yahoo.com" target=3D"_bl=
ank">zgenjix@yahoo.com</a>></span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">
This is like the most annoying thing about email. Often with group emails, =
we'll be having a conversation then someone will click reply instead of=
group reply and the convo will go on for a while. Eventually I'll real=
ise the persons are missing and add them back in.<br>
<br>
On Yahoo mail (which I use for spam/mailing lists), to do reply all involve=
s clicking a tab, scrolling down and clicking Reply All. Normally I instead=
go through the steps of reply, delete To, re-enter bitco... select drop do=
wn, click send.<br>
<br>
Anyone know how to make reply all the default in mutt? And how can I exclud=
e it from re-including my own email when I do a group reply so I don't =
get the same email again.<br>
<div class=3D"im HOEnZb"><br>
<br>
<br>
----- Original Message -----<br>
From: Jeff Garzik <<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@exmult=
i.com</a>><br>
To: grarpamp <<a href=3D"mailto:grarpamp@gmail.com">grarpamp@gmail.com</=
a>><br>
Cc: <a href=3D"mailto:bitcoin-development@lists.sourceforge.net">bitcoin-de=
velopment@lists.sourceforge.net</a><br>
Sent: Wednesday, May 2, 2012 7:29 PM<br>
Subject: Re: [Bitcoin-development] new <a href=3D"http://bitcoin.org" targe=
t=3D"_blank">bitcoin.org</a> clients page<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">On Wed, May 2, 2012 at 12:58 =
PM, grarpamp <<a href=3D"mailto:grarpamp@gmail.com">grarpamp@gmail.com</=
a>> wrote:<br>
>> Try "Reply to All"<br>
><br>
> That puts the sender in 'to' and list in 'cc',<br>
> which dupes to the sender and eventually<br>
> blows out the to and cc lines as everyone<br>
> chimes in and doesn't trim. 'reply to' solves<br>
> most of that. assuming the list sw can do it.<br>
<br>
"Reply-To" Munging Considered Harmful<br>
<a href=3D"http://www.unicom.com/pw/reply-to-harmful.html" target=3D"_blank=
">http://www.unicom.com/pw/reply-to-harmful.html</a><br>
<br>
<br>
<br>
--<br>
Jeff Garzik<br>
exMULTI, Inc.<br>
<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@exmulti.com</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today'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>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today'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>
--20cf303f6d3800dede04bf12c7b2--
|
