blob: 1a1b78026eed282d96ac448c80a65156e01c01ee (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1VHZ0Q-0003ft-U8
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Sep 2013 12:49:50 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.172 as permitted sender)
client-ip=209.85.214.172; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f172.google.com;
Received: from mail-ob0-f172.google.com ([209.85.214.172])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VHZ0P-00025v-8H
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Sep 2013 12:49:50 +0000
Received: by mail-ob0-f172.google.com with SMTP id er7so1889653obc.31
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Sep 2013 05:49:43 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.32.70 with SMTP id g6mr6103481obi.81.1378385383536; Thu,
05 Sep 2013 05:49:43 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.80.165 with HTTP; Thu, 5 Sep 2013 05:49:43 -0700 (PDT)
In-Reply-To: <40424BD6-6EF1-454E-AA9F-6AF4C723A4BE@grabhive.com>
References: <879EBFD7-3047-4ECD-B03B-941857F7970C@grabhive.com>
<CANEZrP1zAJ0bQHsqKgH=L4BpgE_kHGKNh=+mv=Tk++7OWA4C2g@mail.gmail.com>
<36036B83-CD26-497F-BC5A-FD69DAFF578C@grabhive.com>
<CANEZrP3hrYZ5SYng=fknCqn_vg9gK4HTS7T-tdQNfc0MwZ5DtA@mail.gmail.com>
<40424BD6-6EF1-454E-AA9F-6AF4C723A4BE@grabhive.com>
Date: Thu, 5 Sep 2013 14:49:43 +0200
X-Google-Sender-Auth: eZeSclZ26H50QGQdocauNQsgBoc
Message-ID: <CANEZrP0k5igJuWXV_oJCoFtEy_POXrLHt00g8EM4CtTgLLbkug@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Wendell <w@grabhive.com>
Content-Type: multipart/alternative; boundary=089e013a09f42641b004e5a25bc7
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VHZ0P-00025v-8H
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] An "app store" and non-network
transaction fees
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 05 Sep 2013 12:49:51 -0000
--089e013a09f42641b004e5a25bc7
Content-Type: text/plain; charset=UTF-8
It needs people to use either a dedicated app or a wallet with the right
features. I've gone back and forth on whether it's better to have wallets
become featureful things or to have lots of separate apps. There are pro's
and con's to each.
Fortunately bitcoinj makes bringing up a new GUI wallet app quite easy
(well ... if you're writing it in java ;). So having a dedicated app just
for managing your pledges is quite straightforward.
At that point it's about contracts programming:
https://code.google.com/p/bitcoinj/wiki/WorkingWithContracts
--089e013a09f42641b004e5a25bc7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">It needs people to use either a dedicated app or a wallet =
with the right features. I've gone back and forth on whether it's b=
etter to have wallets become featureful things or to have lots of separate =
apps. There are pro's and con's to each.<div>
<br></div><div>Fortunately bitcoinj makes bringing up a new GUI wallet app =
quite easy (well ... if you're writing it in java ;). So having a dedic=
ated app just for managing your pledges is quite straightforward.</div>
<div><br></div><div>At that point it's about contracts programming:</di=
v><div><br></div><div><a href=3D"https://code.google.com/p/bitcoinj/wiki/Wo=
rkingWithContracts">https://code.google.com/p/bitcoinj/wiki/WorkingWithCont=
racts</a><br>
</div><div class=3D"gmail_extra"><br></div></div>
--089e013a09f42641b004e5a25bc7--
|
