{"type":"rich","version":"1.0","author_name":"Jameson Lopp [ARCHIVE] (npub1gh…akqmn)","author_url":"https://nostr.ae/npub1ghgfr3aumwuxwnwghywxpaejxpf6k9pjcnyg9lfdnztlu5pwa0ksyakqmn","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-07\n📝 Original message:I'm glad to see that I'm not the only one concerned about the consistent dropping of nodes. Though I think that the fundamental question should be: how many nodes do we really need? Obviously more is better, but it's difficult to say how concerned we should be without more information. I posted my thoughts last month: http://coinchomp.com/2014/03/19/bitcoin-nodes-many-enough/\n\nI have begun working on my node monitoring project and will post updates if it results in me gaining any new insights about the network.\n\n- Jameson\n\nOn 04/07/2014 07:34 AM, Mike Hearn wrote:\n\u003e At the start of February we had 10,000 bitcoin nodes. Now we have 8,500 and\n\u003e still falling:\n\u003e \n\u003e    http://getaddr.bitnodes.io/dashboard/chart/?days=60\n\u003e \n\u003e I know all the reasons why people *might* stop running a node (uses too\n\u003e much disk space, bandwidth, lost interest etc). But does anyone have any\n\u003e idea how we might get more insight into what's really going on? It'd be\n\u003e convenient if the subVer contained the operating system, as then we could\n\u003e tell if the bleed was mostly from desktops/laptops (Windows/Mac), which\n\u003e would be expected, or from virtual servers (Linux), which would be more\n\u003e concerning.\n\u003e \n\u003e When you set up a Tor node, you can add your email address to the config\n\u003e file and the Tor project sends you emails from time to time about things\n\u003e you should know about. If we did the same, we could have a little exit\n\u003e survey: if your node disappears for long enough, we could email the\n\u003e operator and ask why they stopped.\n\u003e \n\u003e \n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e Put Bad Developers to Shame\n\u003e Dominate Development with Jenkins Continuous Integration\n\u003e Continuously Automate Build, Test \u0026 Deployment \n\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e http://p.sf.net/sfu/13600_Cloudbees_APR\n\u003e \n\u003e \n\u003e \n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e"}