From: Alex Kravets <kravets@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org
Date: Thu, 27 Jun 2013 15:53:05 -0700 [thread overview]
Message-ID: <CALMbsiL_NQ9P6yRKA3rK-qa_bs2U6WNTtxUBT1i=Dh-N7LwwuQ@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0O2vRUS+eMcSa-ggVPUNX4d8Ffb7Bs_Gp0X1SB1qz_U2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
Perhaps there should be two different sections on the web page.
Nerds / Non-Nerds
With different recommendations for which clients to use.
On Thu, Jun 27, 2013 at 2:56 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> On Thu, Jun 27, 2013 at 5:12 PM, Alex Kravets <kravets@gmail.com> wrote:
> > What all the nerdy devs (and I am one so I know) seem unable to
> comprehend,
> > is that regular people out there don't wanna learn all this new stuff and
> > new terminology they simply have no attention span for it.
>
> Bitcoin Wallet for Android is a decentralized client w/ network sync,
> and it works just fine. Fast, easy to use.
>
> --
> Jeff Garzik
> Senior Software Engineer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
--
Alex Kravets <http://www.linkedin.com/in/akravets> def redPill = '
Scala <http://www.scala-lang.org/>
[[ brutal honesty <http://goo.gl/vwydt> is the best policy ]]
[-- Attachment #2: Type: text/html, Size: 1698 bytes --]
next prev parent reply other threads:[~2013-06-27 22:53 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 17:10 [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org Jim
2013-06-27 17:30 ` Jeff Garzik
2013-06-27 18:04 ` Luke-Jr
2013-06-27 18:41 ` Gregory Maxwell
2013-06-27 19:18 ` Jim
2013-06-27 19:40 ` Jim
2013-06-27 19:50 ` Jim
2013-06-27 21:12 ` Alex Kravets
2013-06-27 21:56 ` Jeff Garzik
2013-06-27 22:53 ` Alex Kravets [this message]
2013-06-27 22:03 ` Gary Rowe
2013-06-28 10:59 ` John Dillon
2013-06-28 9:10 ` Mike Hearn
2013-06-28 14:24 ` Gavin Andresen
[not found] ` <CAFtwHRewE0wgvWsf-785hpCb8ns7wiGaKHAQ-1QmDD-W+diBJA@mail.gmail.com>
2013-06-28 20:37 ` Bill Hees
2013-06-28 20:42 ` Jim
2013-06-30 11:42 ` Mike Hearn
2013-06-30 15:19 ` Jim
2013-06-30 16:39 ` Gary Rowe
2013-07-09 0:22 ` Robert Backhaus
2013-07-09 1:20 ` Caleb James DeLisle
2013-07-09 10:36 ` Mike Hearn
2013-07-09 10:56 ` Jim
2013-07-09 11:04 ` Mike Hearn
2013-07-09 11:13 ` Will
2013-07-09 11:15 ` Jim
2013-07-09 11:18 ` Mike Hearn
2013-07-09 14:00 ` Daniel F
2013-07-09 14:06 ` Jeff Garzik
2013-07-09 14:28 ` Mike Hearn
2013-07-09 14:46 ` Jim
2013-07-09 14:57 ` Daniel F
2013-07-09 15:27 ` Mike Hearn
2013-07-09 15:32 ` Nick Simpson
2013-07-09 15:51 ` Johnathan Corgan
2013-07-09 16:44 ` Mike Hearn
2013-07-09 15:59 ` Jeff Garzik
2013-07-09 16:03 ` Nick Simpson
2013-07-09 22:15 ` Andreas Petersson
2013-06-27 17:56 ` Gregory Maxwell
2013-06-27 18:05 ` Alex Kravets
2013-06-27 23:45 ` Caleb James DeLisle
2013-06-28 9:05 ` Mike Hearn
2013-06-28 10:09 ` John Dillon
2013-06-28 10:20 ` Mike Hearn
2013-06-28 10:32 ` John Dillon
2013-06-30 10:12 ` Peter Todd
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='CALMbsiL_NQ9P6yRKA3rK-qa_bs2U6WNTtxUBT1i=Dh-N7LwwuQ@mail.gmail.com' \
--to=kravets@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@bitpay.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