path: root/86/8dfaea32db49b2d28235083a6f44d93a72a5d4

Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <g.rowe.froot@gmail.com>) id 1SPfVr-0002Ql-Q7
	for bitcoin-development@lists.sourceforge.net;
	Wed, 02 May 2012 19:46:59 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.47 as permitted sender)
	client-ip=209.85.213.47; envelope-from=g.rowe.froot@gmail.com;
	helo=mail-yw0-f47.google.com; 
Received: from mail-yw0-f47.google.com ([209.85.213.47])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1SPfVq-00048U-KS
	for bitcoin-development@lists.sourceforge.net;
	Wed, 02 May 2012 19:46:59 +0000
Received: by yhjj56 with SMTP id j56so1296757yhj.34
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 02 May 2012 12:46:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.185.68 with SMTP id t44mr32150774yhm.126.1335988013216;
	Wed, 02 May 2012 12:46:53 -0700 (PDT)
Sender: g.rowe.froot@gmail.com
Received: by 10.236.25.98 with HTTP; Wed, 2 May 2012 12:46:52 -0700 (PDT)
In-Reply-To: <1335987832.23789.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>
	<CAKm8k+0pxiKvRp8BokQ+dt-3Ttu7KsdichSqav8qZiv_p6coFQ@mail.gmail.com>
	<1335987832.23789.YahooMailNeo@web121007.mail.ne1.yahoo.com>
Date: Wed, 2 May 2012 20:46:52 +0100
X-Google-Sender-Auth: ybjV-pVDIiXR2nG3u0PMU5LwLSg
Message-ID: <CAKm8k+12tXVHMcS5-nF4G5F2wUWcBjTFbJ66aL8gaAO4PXVBOQ@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=20cf303f69aef3b21604bf12f210
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: 1SPfVq-00048U-KS
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:46:59 -0000

--20cf303f69aef3b21604bf12f210
Content-Type: text/plain; charset=UTF-8

Alan, apologies about the installer - I was just using your website info to
infer how it all fitted together.

On 2 May 2012 20:43, Amir Taaki <zgenjix@yahoo.com> wrote:

> This discussion about ordering is absolutely retarded. Once the list fills
> up, then it won't matter. For now I'm deciding the ordering with Bitcoin-Qt
> first and the others ordered however. That was nobody can try to game the
> system (it remains unexploitable).
>
> If there are no objections, then I am going to merge this branch. The
> forum thread is divulging into a mess all over the place, and this
> conversation can go on forever discussing the silly fine details:
>
> http://hackerspaces.org/wiki/The_Bikeshed_Anti-PatternProblem:
> You suggest creating something new for your hackerspace, like a
> bikeshed.  But now all anyone will discuss is its colour. No bikeshed
> will be built.
>
> Armory & MultiBit, are you OK with that description? I will check with
> ThomasV about Electrum.
>
>
> ________________________________
> From: Gary Rowe <g.rowe@froot.co.uk>
> To: "bitcoin-development@lists.sourceforge.net" <
> bitcoin-development@lists.sourceforge.net>
> Sent: Wednesday, May 2, 2012 8:34 PM
> Subject: Re: [Bitcoin-development] new bitcoin.org clients page
>
>
> 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
> >
>
>
> ------------------------------------------------------------------------------
> 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
>

--20cf303f69aef3b21604bf12f210
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Alan, apologies about the installer - I was just using your website info to=
 infer how it all fitted together.<div><br><div class=3D"gmail_quote">On 2 =
May 2012 20:43, Amir Taaki <span dir=3D"ltr">&lt;<a href=3D"mailto:zgenjix@=
yahoo.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">This discussion about ordering is absolutely=
 retarded. Once the list fills up, then it won&#39;t matter. For now I&#39;=
m deciding the ordering with Bitcoin-Qt first and the others ordered howeve=
r. That was nobody can try to game the system (it remains unexploitable).<b=
r>

<br>
If there are no objections, then I am going to merge this branch. The forum=
 thread is divulging into a mess all over the place, and this conversation =
can go on forever discussing the silly fine details:<br>
<br>
<a href=3D"http://hackerspaces.org/wiki/The_Bikeshed_Anti-PatternProblem" t=
arget=3D"_blank">http://hackerspaces.org/wiki/The_Bikeshed_Anti-PatternProb=
lem</a>:<br>
You suggest creating something new for your hackerspace, like a<br>
bikeshed. =C2=A0But now all anyone will discuss is its colour. No bikeshed<=
br>
will be built.<br>
<br>
Armory &amp; MultiBit, are you OK with that description? I will check with =
ThomasV about Electrum.<br>
<br>
<br>
________________________________<br>
From: Gary Rowe &lt;<a href=3D"mailto:g.rowe@froot.co.uk">g.rowe@froot.co.u=
k</a>&gt;<br>
To: &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: Wednesday, May 2, 2012 8:34 PM<br>
<div class=3D"HOEnZb"><div class=3D"h5">Subject: Re: [Bitcoin-development] =
new <a href=3D"http://bitcoin.org" target=3D"_blank">bitcoin.org</a> client=
s page<br>
<br>
<br>
How about keeping it simple?<br>
<br>
Bitcoin-Qt<br>
* Requires the entire blockchain<br>
* Standalone client<br>
* Designed for continuous operation<br>
* Available for Windows, Mac, Linux with installer<br>
* Developed in C<br>
* Website: <a href=3D"https://bitcoin.org" target=3D"_blank">https://bitcoi=
n.org</a><br>
<br>
MultiBit<br>
* Requires a reduced blockchain=C2=A0<br>
* Standalone client<br>
* Designed for occasional use<br>
* Available for Windows, Mac, Linux with installer<br>
* Developed in Java =C2=A0<br>
* Website: <a href=3D"http://multibit.org" target=3D"_blank">http://multibi=
t.org</a><br>
<br>
Armory<br>
* Requires the entire blockchain<br>
* Dependent client of Bitcoin-Qt=C2=A0<br>
* Designed for occasional use<br>
* Available for Windows (64-bit only), Mac, Linux (self-build)<br>
* Developed in Python<br>
* Website: <a href=3D"http://bitcoinarmory.com/" target=3D"_blank">http://b=
itcoinarmory.com/</a><br>
<br>
Electrum<br>
* Requires no blockchain<br>
* Dependent client of Bitcoin-Qt (on server)<br>
* Designed for occasional use<br>
* Available for Windows, Linux (self-build)<br>
* Developed in Python<br>
* Website: <a href=3D"http://ecdsa.org/electrum/" target=3D"_blank">http://=
ecdsa.org/electrum/</a><br>
<br>
Bitcoin Wallet (Android client)<br>
* Requires a reduced blockchain<br>
* Standalone client<br>
* Designed for occasional use on mobile<br>
* Available for Android only<br>
* Developed in Java<br>
* Website: <a href=3D"https://play.google.com/store/apps/details?id=3Dde.sc=
hildbach.wallet&amp;hl=3Den" target=3D"_blank">https://play.google.com/stor=
e/apps/details?id=3Dde.schildbach.wallet&amp;hl=3Den</a><br>
<br>
<br>
On 2 May 2012 20:25, Amir Taaki &lt;<a href=3D"mailto:zgenjix@yahoo.com">zg=
enjix@yahoo.com</a>&gt; wrote:<br>
<br>
This is like the most annoying thing about email. Often with group emails, =
we&#39;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&#39;ll real=
ise the persons are missing and add them back in.<br>

&gt;<br>
&gt;On Yahoo mail (which I use for spam/mailing lists), to do reply all inv=
olves clicking a tab, scrolling down and clicking Reply All. Normally I ins=
tead go through the steps of reply, delete To, re-enter bitco... select dro=
p down, click send.<br>

&gt;<br>
&gt;Anyone know how to make reply all the default in mutt? And how can I ex=
clude it from re-including my own email when I do a group reply so I don&#3=
9;t get the same email again.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;----- Original Message -----<br>
&gt;From: Jeff Garzik &lt;<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@ex=
multi.com</a>&gt;<br>
&gt;To: grarpamp &lt;<a href=3D"mailto:grarpamp@gmail.com">grarpamp@gmail.c=
om</a>&gt;<br>
&gt;Cc: <a href=3D"mailto:bitcoin-development@lists.sourceforge.net">bitcoi=
n-development@lists.sourceforge.net</a><br>
&gt;Sent: Wednesday, May 2, 2012 7:29 PM<br>
&gt;Subject: Re: [Bitcoin-development] new <a href=3D"http://bitcoin.org" t=
arget=3D"_blank">bitcoin.org</a> clients page<br>
&gt;<br>
&gt;<br>
&gt;On Wed, May 2, 2012 at 12:58 PM, grarpamp &lt;<a href=3D"mailto:grarpam=
p@gmail.com">grarpamp@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt; Try &quot;Reply to All&quot;<br>
&gt;&gt;<br>
&gt;&gt; That puts the sender in &#39;to&#39; and list in &#39;cc&#39;,<br>
&gt;&gt; which dupes to the sender and eventually<br>
&gt;&gt; blows out the to and cc lines as everyone<br>
&gt;&gt; chimes in and doesn&#39;t trim. &#39;reply to&#39; solves<br>
&gt;&gt; most of that. assuming the list sw can do it.<br>
&gt;<br>
&gt;&quot;Reply-To&quot; Munging Considered Harmful<br>
&gt;<a href=3D"http://www.unicom.com/pw/reply-to-harmful.html" target=3D"_b=
lank">http://www.unicom.com/pw/reply-to-harmful.html</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;--<br>
&gt;Jeff Garzik<br>
&gt;exMULTI, Inc.<br>
&gt;<a href=3D"mailto:jgarzik@exmulti.com">jgarzik@exmulti.com</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>
&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>
<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>

--20cf303f69aef3b21604bf12f210--