From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org
Date: Thu, 27 Jun 2013 23:03:18 +0100 [thread overview]
Message-ID: <CAKm8k+0pCGY53QyQpsdmmjPL5_1Kx7xXD3Lz0n0RSHgcx4Bz-g@mail.gmail.com> (raw)
In-Reply-To: <CALMbsi+5JYYDvy5D=22RMQ5SGtaZ2dY=FLDTRhUAv7=dAvuTeQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4964 bytes --]
Many people that I have introduced Bitcoin to have balked at the massive
blockchain download. When I showed them MultiBit (and Bitcoin Wallet) they
breathed a sigh of relief and got on with it.
A currency lives or dies by network effects. If we can provide the average
low-tech user with a great client experience right from the word go then we
can win them over quickly. Once that is accomplished then more techie users
will likely go on to use a full node which will continue to strengthen the
network overall.
On 27 June 2013 22:12, Alex Kravets <kravets@gmail.com> wrote:
> Hi Jim,
>
> On Thu, Jun 27, 2013 at 12:18 PM, Jim <jim618@fastmail.co.uk> wrote:
>
>>
>> Alex: Yes I think most users migrate to blockchain.info or,
>> more recently coinbase.com. They are both good wallets
>> but I'd like to keep Bitcoin as P2P as possible.
>>
>
> Guys, being a late comer/outsider (I got into bitcoin in early 2012), I
> can tell you that this particular asylum is definitely run by its inmates.
>
> 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.
>
> Simply channelling them to a decent client that
>
> 1. Just works (no blockchain downloads and no re-sync)
> 2. Allows to retain control of the private keys
>
> Would be HUGE for mass adoption.
>
> Old tired argument about "Bitcoin needs your nodes", so we'll channel you
> to get bitcoin-qt client is both manipulative and unnecessary (there's
> plenty of nodes and NAT'ed home nodes which don't mine are mostly useless
> anyways)
>
> P.S. coinbase.com is just another trust-me setup takes your coins in
> exchange for IOUs, whereas blockchain.info does let you to retain control
> of your private keys.
>
> P.P.S. The reason why coinbase has gotten so big is precisely because they
> don't trouble regular lawyers and doctors with all the nonsense but simply
> give them a
> "buy" and a "sell" button.
>
>
>
>
>
>> Luke-Jr
>> I think you are right here on the number of full nodes versus
>> SPV nodes.
>> I don't think we even know yet what are the working ratios of
>> full nodes to SPV nodes. I haven't seen anybody do any
>> analysis on this.
>>
>> I doubt multibit will ever participate in the Bitcoin network
>> other than as an SPV client. All the optimisation is to reduce
>> data traffic - it is effectively a mobile wallet that happens to
>> live on a desktop. It is not really intended to be more than
>> "a wallet for regular people to store and spend their bitcoin".
>>
>> In English the nomenclature for direction of the transactions
>> is: "Sent to" and "Received with". To be honest I
>> haven't transliterated the localisation files to check other
>> language packs but the localisers are pretty good in my
>> experience.
>>
>>
>>
>>
>>
>> On Thu, Jun 27, 2013, at 07:41 PM, Gregory Maxwell wrote:
>> > On Thu, Jun 27, 2013 at 11:04 AM, Luke-Jr <luke@dashjr.org> wrote:
>> > > On Thursday, June 27, 2013 5:30:21 PM Jeff Garzik wrote:
>> > >> * Very real possibility of an overall net reduction of full nodes on
>> P2P
>> > >> network
>> > > Even a reduction of *nodes at all*, as I've never seen a listening
>> bitcoinj or
>> > > MultiBit node. :/
>> > > Jim, will MultiBit be adding p2p listening support?
>> >
>> > Without validation listening isn't currently very useful. :( Maybe it
>> > could be somewhat more with some protocol additions.
>> >
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by Windows:
>> >
>> > Build for Windows Store.
>> >
>> > http://p.sf.net/sfu/windows-dev2dev
>> > _______________________________________________
>> > Bitcoin-development mailing list
>> > Bitcoin-development@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>> --
>> https://multibit.org Money, reinvented
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
>
>
> --
> 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 ]]
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 7597 bytes --]
next prev parent reply other threads:[~2013-06-27 22:03 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
2013-06-27 22:03 ` Gary Rowe [this message]
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=CAKm8k+0pCGY53QyQpsdmmjPL5_1Kx7xXD3Lz0n0RSHgcx4Bz-g@mail.gmail.com \
--to=g.rowe@froot.co.uk \
--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