{"type":"rich","version":"1.0","author_name":"npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","author_url":"https://nostr.ae/npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-05-07\n📝 Original message:On Wed, May 7, 2014 at 9:57 PM, Jameson Lopp \u003cjameson.lopp at gmail.com\u003e wrote:\n\u003e -----BEGIN PGP SIGNED MESSAGE-----\n\u003e Hash: SHA1\n\u003e\n\u003e I agree that it would be awesome to offer these types of stats with the installer; unfortunately the route I've taken has dependencies on several other other pieces of software to do all the heavy lifting of stats aggregation and chart rendering. I'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?\n\nDepends on just how much stuff it is. The idea is primarily to have an\ninstaller for running a (wallet-less) node as an OS background\nservice.\n\nHaving some statistics available would be worth some extra download\nsize, otherwise it would be pretty much invisible.\n\nWe'd already decided that we would need something like Python for the\nstats service. Implementing things like web services in C++ is just\nnot realistic given the time constraints and the great already-written\ncode that is out there. As an optional tool it should be external, not\npart of bitcoind itself.\n\nI suppose the chart rendering happens client-side? In that case the\nweb service just has to collect and provide the data, and serve static\nhtml/js files.\n\nWladimir"}