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 ) 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 ; 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> <201205021230.46349.luke@dashjr.org> <1335986730.68336.YahooMailNeo@web121007.mail.ne1.yahoo.com> Date: Wed, 2 May 2012 20:34:35 +0100 X-Google-Sender-Auth: 0qj416ImA2Y9btIvWA2SB5KHHRk Message-ID: From: Gary Rowe To: "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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 > --20cf303f6d3800dede04bf12c7b2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
How about keeping it simple?

Bitcoin-Qt
=
* Requires the entire blockchain
* Standalone client
* Designed for continuous operation
* Available for Windows, M= ac, Linux with installer
* Developed in C

MultiBit
* Requi= res a reduced blockchain=C2=A0
* Standalone client
* De= signed for occasional use
* Available for Windows, Mac, Linux with installer
* Develop= ed in Java =C2=A0

Armory
* Requires th= e entire blockchain
* Dependent client of Bitcoin-Qt=C2=A0
* Designed for occasi= onal use
* Available for Windows (64-bit only), Mac, Linux (self-= build)
* Developed in Python

Electrum
* Requires no blockchain
*= Dependent client of Bitcoin-Qt (on server)
* Designed for occasi= onal use
* Available for Windows, Linux (self-build)
* Developed in Python

Bitcoin Wall= et (Android client)
* Requires a reduced blockchain
* S= tandalone client
* Designed for occasional use on mobile
* Available for Andr= oid only
* Developed in Java


On 2 May 2012 20:25, Amir Taa= ki <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 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 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.

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.



----- Original Message -----
From: Jeff Garzik <jgarzik@exmult= i.com>
To: grarpamp <grarpamp@gmail.com>
Cc: bitcoin-de= velopment@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/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

--20cf303f6d3800dede04bf12c7b2--