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
101
102
103
104
105
106
107
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WXqTv-0002rT-5e
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 11:15:51 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.170 as permitted sender)
client-ip=209.85.223.170; envelope-from=laanwj@gmail.com;
helo=mail-ie0-f170.google.com;
Received: from mail-ie0-f170.google.com ([209.85.223.170])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXqTu-0001nG-F8
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 11:15:51 +0000
Received: by mail-ie0-f170.google.com with SMTP id rd18so2279220iec.1
for <bitcoin-development@lists.sourceforge.net>;
Wed, 09 Apr 2014 04:15:45 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.43.155.209 with SMTP id lj17mr31194icc.94.1397042145112;
Wed, 09 Apr 2014 04:15:45 -0700 (PDT)
Received: by 10.64.70.131 with HTTP; Wed, 9 Apr 2014 04:15:44 -0700 (PDT)
In-Reply-To: <B3C2AD26-F806-450E-A19F-31E7871A09A7@hivewallet.com>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
<CALC81CMc7BridL7600b7bij3dJHzeQWgTv=iqVeW--n-we+1Yw@mail.gmail.com>
<lhua2p$lp5$1@ger.gmane.org>
<CANEZrP3F+UQ1amVAK4a9_UCsXia7Yfv0RO4pWK7NTde0GvH-0A@mail.gmail.com>
<CAAf19Wrz0u_e5V9Gb=_CAG=mHtE9nA_VETgYZeCXZqwaGeYKuQ@mail.gmail.com>
<B3C2AD26-F806-450E-A19F-31E7871A09A7@hivewallet.com>
Date: Wed, 9 Apr 2014 13:15:44 +0200
Message-ID: <CA+s+GJDPTrrrUmiXZzAgngefyJBX6YVK5XCpDQ_OtV8Wa+JpYw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Wendell <w@hivewallet.com>
Content-Type: multipart/alternative; boundary=001a11c2fe10cbb5bf04f69a3864
X-Spam-Score: -0.6 (/)
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
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1WXqTu-0001nG-F8
Cc: Andreas Schildbach <andreas@schildbach.de>,
Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
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: Wed, 09 Apr 2014 11:15:51 -0000
--001a11c2fe10cbb5bf04f69a3864
Content-Type: text/plain; charset=UTF-8
On Wed, Apr 9, 2014 at 12:38 PM, Wendell <w@hivewallet.com> wrote:
> On that note, I think we have every possibility to make desktop and mobile
> wallets mind-numbingly simple -- and perhaps even do one better. Is this
> now a community priority? If so, I would really appreciate some additional
> contributors to Hive!
>
>
How does that relate to the nodes issue?
Would packaging an optional bitcoind with your wallet be an option, which
is automatically managed in the background, so that users can run a full
node if they want?
Wladimir
--001a11c2fe10cbb5bf04f69a3864
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Wed, Apr 9, 2014 at 12:38 PM, Wendell <span dir=3D"ltr"><<a href=3D"m=
ailto:w@hivewallet.com" target=3D"_blank">w@hivewallet.com</a>></span> w=
rote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On that note, I think we have every possibil=
ity to make desktop and mobile wallets mind-numbingly simple -- and perhaps=
even do one better. Is this now a community priority? If so, I would reall=
y appreciate some additional contributors to Hive!<br>
<br></blockquote><div><br></div><div>How does that relate to the nodes issu=
e?<br><br></div><div>Would packaging an optional bitcoind with your wallet =
be an option, which is automatically managed in the background, so that use=
rs can run a full node if they want?<br>
<br>Wladimir<br></div></div><br></div></div>
--001a11c2fe10cbb5bf04f69a3864--
|
