public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Alan Reiner <etotheipi@gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
Date: Mon, 30 Apr 2012 14:23:08 -0400	[thread overview]
Message-ID: <CALf2ePwm9_aGngzVTKte+3_+yHF=-pcNqTAO0hmkR5rcimEX3g@mail.gmail.com> (raw)
In-Reply-To: <1335808239.18613.YahooMailNeo@web121006.mail.ne1.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]

Hey, looks good!  I'm glad to see them sorted alphabetically :)

A couple comments:  I don't think the entries for "wallet security" and
"backups" accurately describe Armory.  Wallet Security should say
"Encrypt/Offline" or something to to that effect -- after all, offline
wallets are the holy grail feature of the Armory.  And backups should say
something like "One-time Printable" if it fits within the box.

Otherwise, I really like the layout and design.  Although despite the fact
I enjoy being first on the list, I think Bitcoin-Qt should still go first.
 It is the "reference" client, and I think it's relevant that it is the
"de-facto" client for the majority of users, and the one with the most
quality control and stability.

-Alan


On Mon, Apr 30, 2012 at 1:50 PM, Amir Taaki <zgenjix@yahoo.com> wrote:

> Check it :) https://github.com/bitcoin/bitcoin.org/pull/34
>
>
> ------------------------------------------------------------------------------
> 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
>

[-- Attachment #2: Type: text/html, Size: 2253 bytes --]

  reply	other threads:[~2012-04-30 18:23 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 [this message]
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
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='CALf2ePwm9_aGngzVTKte+3_+yHF=-pcNqTAO0hmkR5rcimEX3g@mail.gmail.com' \
    --to=etotheipi@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=zgenjix@yahoo.com \
    /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