From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
Date: Wed, 2 May 2012 16:25:26 -0400 [thread overview]
Message-ID: <201205021625.27867.luke@dashjr.org> (raw)
In-Reply-To: <CAKm8k+0pxiKvRp8BokQ+dt-3Ttu7KsdichSqav8qZiv_p6coFQ@mail.gmail.com>
On Wednesday, May 02, 2012 3:34:35 PM Gary Rowe wrote:
> Bitcoin-Qt
> * Developed in C
This is far less relevant than license...
> Armory
> * Requires the entire blockchain
> * Dependent client of Bitcoin-Qt
Or bitcoind?
> Electrum
> * Dependent client of Bitcoin-Qt (on server)
Dependent on centralized server, not any particular client
> Bitcoin Wallet (Android client)
There are multiple Android clients. There is (or was) an OS selection to the
left of the client choices...
On Wednesday, May 02, 2012 3:43:23 PM Alan Reiner wrote:
> I'm not sure what "designed for occasional use" means. Many users of
> other clients use them exclusively without touching other clients. Armory
> is designed to be your only wallet (if bitcoind[d/-qt] is running in bkgd).
> I'm sure the other clients are the same.
Pretty sure it means "not running continuously".
> Btw, Armory now has full installers for both Windows and Linux
> (Ubuntu/Debian), with uninstallers and automatic URI registration
Would be awesome if it took after Spesmilo and managed bitcoind itself in the
background...
next prev parent reply other threads:[~2012-05-02 20:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 17:50 [Bitcoin-development] new bitcoin.org clients page Amir Taaki
2012-04-30 18:23 ` Alan Reiner
2012-04-30 18:31 ` Amir Taaki
2012-04-30 19:51 ` Alan Reiner
2012-05-02 13:22 ` Mike Hearn
2012-05-02 13:30 ` Gregory Maxwell
2012-05-02 13:32 ` Mike Hearn
2012-05-02 13:31 ` Luke-Jr
2012-05-02 16:21 ` grarpamp
2012-05-02 16:30 ` Luke-Jr
2012-05-02 16:58 ` grarpamp
2012-05-02 18:29 ` Jeff Garzik
2012-05-02 19:25 ` Amir Taaki
2012-05-02 19:34 ` Gary Rowe
2012-05-02 19:40 ` Raphael NICOLLE
2012-05-02 19:42 ` Gary Rowe
2012-05-02 19:43 ` Alan Reiner
2012-05-02 19:43 ` Amir Taaki
2012-05-02 19:46 ` Gary Rowe
2012-05-02 19:56 ` Alan Reiner
2012-05-02 20:25 ` Luke-Jr [this message]
2012-05-02 20:39 ` Gary Rowe
2012-05-02 19:35 ` Alan Reiner
2012-05-03 9:06 ` grarpamp
2012-05-02 13:38 ` Gregory Maxwell
2012-05-02 13:42 ` Mike Hearn
2012-05-02 15:01 ` Alan Reiner
2012-05-02 16:53 ` grarpamp
2012-05-03 7:28 ` Andreas Schildbach
2012-05-03 9:24 ` Jorge Timón
2012-05-03 9:53 ` Andreas Schildbach
2012-05-03 10:25 ` Jorge Timón
2012-05-02 23:04 ` Jeff Garzik
2012-05-02 20:41 Jim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201205021625.27867.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox