From: Gregory Maxwell <gmaxwell@gmail•com>
To: Alan Reiner <etotheipi@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Roadmap to getting users onto SPV clients
Date: Tue, 4 Dec 2012 19:27:50 -0500 [thread overview]
Message-ID: <CAAS2fgQewysOG7eOHQxmLup4oLJK=jY=q-_4qTL6yKQ855g3ew@mail.gmail.com> (raw)
In-Reply-To: <CALf2ePw82wt08_G2RtUYEBxorjY1ryZ4r+W7atSzDLYMU+rGGQ@mail.gmail.com>
On Tue, Dec 4, 2012 at 5:44 PM, Alan Reiner <etotheipi@gmail•com> wrote:
> Greg's point looks like it's veering towards "we don't want to grow
> the network unless we're going to get more full nodes out of it."
No…
There is no fundamental completion between taking what actions we can
to maximize the decentralization of the network and making the
software maximally friendly and painless to get started with and use.
It's possible— not even deep rocket science— to create software that
accommodates both.
And because of this, I don't think it's acceptable to promote
solutions which may endanger the decentralization that makes the
system worthwhile in the first place. If the current experience is so
poor that you'd even consider talking about promoting directions which
reduce its robustness then thats evidence that it would be worth
finding more resources to make the experience better without doing
anything the that reduces the model, even if you've got an argument
that maybe we can get away with it. If there isn't interest in
putting in more resources to make these improvements then maybe the
issue isn't as bad as we think it is?
> I think it is very much in everyone's interest here to encourage new users to start "using" Bitcoin, even if they don't "support" it.
Absolutely— and yet that has nothing to do with promoting software to
users which only consumes without directly contributing and which
doesn't even have the capability to do so even if the user wants to
(or much less, is indifferent).
next prev parent reply other threads:[~2012-12-05 0:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 17:46 Mike Hearn
2012-12-04 18:03 ` Alan Reiner
2012-12-04 18:08 ` Will
2012-12-04 18:17 ` Gregory Maxwell
2012-12-04 20:58 ` Mike Hearn
2012-12-04 21:41 ` Gregory Maxwell
2012-12-04 22:44 ` Alan Reiner
2012-12-05 0:27 ` Gregory Maxwell [this message]
2012-12-05 2:08 ` Alan Reiner
2012-12-05 2:54 ` Gregory Maxwell
2012-12-05 5:38 ` Jim Nguyen
2012-12-05 7:50 ` Wladimir
2012-12-05 9:43 ` Gary Rowe
2012-12-05 10:19 ` Robert Backhaus
2012-12-05 10:43 ` Mike Hearn
2012-12-04 18:57 ` Mark Friedenbach
2012-12-04 19:36 ` Gregory Maxwell
[not found] <mailman.70419.1354648162.2176.bitcoin-development@lists.sourceforge.net>
2012-12-04 19:56 ` Jim
2012-12-04 22:23 ` slush
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='CAAS2fgQewysOG7eOHQxmLup4oLJK=jY=q-_4qTL6yKQ855g3ew@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=etotheipi@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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