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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1Wi8Iq-0003Gz-R5
for bitcoin-development@lists.sourceforge.net;
Wed, 07 May 2014 20:18:56 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.178 as permitted sender)
client-ip=209.85.213.178; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f178.google.com;
Received: from mail-ig0-f178.google.com ([209.85.213.178])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wi8Iq-00086E-0V
for bitcoin-development@lists.sourceforge.net;
Wed, 07 May 2014 20:18:56 +0000
Received: by mail-ig0-f178.google.com with SMTP id hl10so1602260igb.11
for <bitcoin-development@lists.sourceforge.net>;
Wed, 07 May 2014 13:18:50 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.60.72 with SMTP id f8mr47302831igr.20.1399493930155; Wed,
07 May 2014 13:18:50 -0700 (PDT)
Received: by 10.64.22.168 with HTTP; Wed, 7 May 2014 13:18:50 -0700 (PDT)
In-Reply-To: <536A902C.6080602@gmail.com>
References: <536A8592.8010009@gmail.com>
<CA+s+GJASND3OU2e+YxUeLmSOW6pTkMwuzHCHeJnnihg6xK9Caw@mail.gmail.com>
<536A902C.6080602@gmail.com>
Date: Wed, 7 May 2014 22:18:50 +0200
Message-ID: <CA+s+GJCaUX3ErgVean0e91CBorPc6RNKgYs08fOOsqNYtbd6RA@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Jameson Lopp <jameson.lopp@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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
-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: 1Wi8Iq-00086E-0V
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Announcing the Statoshi fork
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, 07 May 2014 20:18:57 -0000
On Wed, May 7, 2014 at 9:57 PM, Jameson Lopp <jameson.lopp@gmail.com> wrote=
:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I agree that it would be awesome to offer these types of stats with the i=
nstaller; unfortunately the route I've taken has dependencies on several ot=
her other pieces of software to do all the heavy lifting of stats aggregati=
on and chart rendering. I'm assuming that you would not want to build any o=
f that processing into Bitcoin Core itself; would you be opposed to packagi=
ng other software along with the installer?
Depends on just how much stuff it is. The idea is primarily to have an
installer for running a (wallet-less) node as an OS background
service.
Having some statistics available would be worth some extra download
size, otherwise it would be pretty much invisible.
We'd already decided that we would need something like Python for the
stats service. Implementing things like web services in C++ is just
not realistic given the time constraints and the great already-written
code that is out there. As an optional tool it should be external, not
part of bitcoind itself.
I suppose the chart rendering happens client-side? In that case the
web service just has to collect and provide the data, and serve static
html/js files.
Wladimir
|
