From: Mike Hearn <mike@plan99•net>
To: Wendell <w@grabhive•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] An "app store" and non-network transaction fees
Date: Thu, 5 Sep 2013 12:14:42 +0200 [thread overview]
Message-ID: <CANEZrP3hrYZ5SYng=fknCqn_vg9gK4HTS7T-tdQNfc0MwZ5DtA@mail.gmail.com> (raw)
In-Reply-To: <36036B83-CD26-497F-BC5A-FD69DAFF578C@grabhive.com>
[-- Attachment #1: Type: text/plain, Size: 2451 bytes --]
On Thu, Sep 5, 2013 at 12:04 PM, Wendell <w@grabhive•com> wrote:
> Funny you should mention it! I just mocked this idea up last week, though
> I assumed a cruder system of "voting" to an address that corresponds to a
> feature -- literally, voting with your wallet (for your wallet, ad
> infinitum). I watched your talk about assurance contracts and other
> "hidden" features, but am not entirely sure that I understood it enough to
> know how it would work in this context. Sorry for the persistent
> hand-holding requests, but some advice would be very welcome.
>
Well, it's a bit complicated and needs some software development to do
well. The best way to fund a complex project would be to raise the money
using an assurance contr.... oh wait ;)
> If it is a real burden for the users, that's the best argument I've yet
> heard. However, my impression from Peter's post was that it would be fairly
> painless for them.
>
It could be automatic in the sense that users don't need to know it's
happening, but look at it this way. Gavin believes the future of computing
is mobile and tablets. I don't know about that, but let's assume for the
sake of argument he turns out to be right. These devices are expected to
have much longer battery life than laptops. Apps that spin up in the
background and use battery+radio can easily be seen as "abusive" by end
users. In fact, if you look in the Bitcoin Wallet section of the forum,
you'll see a giant argument by users of the Android app who are upset
because the app sometimes runs in the background *just to keep up with the
chain*! That's not even donating resources, it's just trying to ensure it
doesn't fall behind, and this enrages some users because it can have a
small but non-zero battery/bandwidth usage impact.
Given the number of complaints generated by just having the app sync
automatically, imagine what would happen if we started relaying blocks!
Generally the ethos and modus operandi of desktops is different to laptops
which is in turn different to mobiles/tablets. Things you can get away with
on more powerful machines that expect to be plugged in all the time are
verboten on more modern devices.
Now that said, I can easily see Bitcoin enthusiasts buying some kind of
cheap embedded device, maybe Raspberry Pi based, and plugging it into a
wall in order to donate to the network. That way it doesn't affect their
primary devices responsiveness or storage or battery life.
[-- Attachment #2: Type: text/html, Size: 3181 bytes --]
next prev parent reply other threads:[~2013-09-05 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 19:47 Wendell
2013-09-05 8:26 ` Mike Hearn
2013-09-05 10:04 ` Wendell
2013-09-05 10:14 ` Mike Hearn [this message]
2013-09-05 12:09 ` Wendell
2013-09-05 12:49 ` Mike Hearn
2013-10-18 11:56 ` Wendell
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='CANEZrP3hrYZ5SYng=fknCqn_vg9gK4HTS7T-tdQNfc0MwZ5DtA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=w@grabhive$(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