<oembed><type>rich</type><version>1.0</version><author_name>npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p</author_name><author_url>https://nostr.ae/npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-05-07&#xA;📝 Original message:On Wed, May 7, 2014 at 9:57 PM, Jameson Lopp &lt;jameson.lopp at gmail.com&gt; wrote:&#xA;&gt; -----BEGIN PGP SIGNED MESSAGE-----&#xA;&gt; Hash: SHA1&#xA;&gt;&#xA;&gt; I agree that it would be awesome to offer these types of stats with the installer; unfortunately the route I&#39;ve taken has dependencies on several other other pieces of software to do all the heavy lifting of stats aggregation and chart rendering. I&#39;m assuming that you would not want to build any of that processing into Bitcoin Core itself; would you be opposed to packaging other software along with the installer?&#xA;&#xA;Depends on just how much stuff it is. The idea is primarily to have an&#xA;installer for running a (wallet-less) node as an OS background&#xA;service.&#xA;&#xA;Having some statistics available would be worth some extra download&#xA;size, otherwise it would be pretty much invisible.&#xA;&#xA;We&#39;d already decided that we would need something like Python for the&#xA;stats service. Implementing things like web services in C++ is just&#xA;not realistic given the time constraints and the great already-written&#xA;code that is out there. As an optional tool it should be external, not&#xA;part of bitcoind itself.&#xA;&#xA;I suppose the chart rendering happens client-side? In that case the&#xA;web service just has to collect and provide the data, and serve static&#xA;html/js files.&#xA;&#xA;Wladimir</html></oembed>