From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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> <201205021230.46349.luke@dashjr.org> <1335986730.68336.YahooMailNeo@web121007.mail.ne1.yahoo.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: From: Gary Rowe To: "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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 > 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 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 > >To: grarpamp > >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 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.

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 howeve= r. 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-PatternProb= lem:
You suggest creating something new for your hackerspace, like a
bikeshed. =C2=A0But now all anyone will discuss is its colour. No bikeshed<= br> 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.u= k>
To: "bitc= oin-development@lists.sourceforge.net" <bitcoin-development@lists.sourceforge= .net>
Sent: Wednesday, May 2, 2012 8:34 PM
Subject: Re: [Bitcoin-development] = new bitcoin.org client= s 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://bitcoi= n.org

MultiBit
* Requires a reduced blockchain=C2=A0
* Standalone client
* Designed for occasional use
* Available for Windows, Mac, Linux with installer
* Developed in Java =C2=A0
* Website: http://multibi= t.org

Armory
* Requires the entire blockchain
* Dependent client of Bitcoin-Qt=C2=A0
* Designed for occasional use
* Available for Windows (64-bit only), Mac, Linux (self-build)
* Developed in Python
* Website: http://b= itcoinarmory.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/stor= e/apps/details?id=3Dde.schildbach.wallet&hl=3Den


On 2 May 2012 20:25, Amir Taaki <zg= enjix@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 real= ise the persons are missing and add them back in.
>
>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.
>
>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= 9;t get the same email again.
>
>
>
>
>----- Original Message -----
>From: Jeff Garzik <jgarzik@ex= multi.com>
>To: grarpamp <grarpamp@gmail.c= om>
>Cc: bitcoi= n-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. Discussio= ns
>will include endpoint security, mobile security and the latest in malwa= re
>threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/5= 0122263/
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-de= velopment@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoi= n-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. Discussio= ns
>will include endpoint security, mobile security and the latest in malwa= re
>threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/5= 0122263/
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-de= velopment@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoi= n-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/50122= 263/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

---------------------------------------------------------------------------= ---
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/50122= 263/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--20cf303f69aef3b21604bf12f210--