Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXA9s-0002W5-Vd for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 14:04:21 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.179 as permitted sender) client-ip=209.85.217.179; envelope-from=gmaxwell@gmail.com; helo=mail-lb0-f179.google.com; Received: from mail-lb0-f179.google.com ([209.85.217.179]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXA9s-0004bm-5Q for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 14:04:20 +0000 Received: by mail-lb0-f179.google.com with SMTP id p9so4707588lbv.24 for ; Mon, 07 Apr 2014 07:04:13 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.3.72 with SMTP id a8mr2131452laa.33.1396879453445; Mon, 07 Apr 2014 07:04:13 -0700 (PDT) Received: by 10.112.89.68 with HTTP; Mon, 7 Apr 2014 07:04:13 -0700 (PDT) In-Reply-To: <5342AF0D.1060209@gmail.com> References: <5342AF0D.1060209@gmail.com> Date: Mon, 7 Apr 2014 07:04:13 -0700 Message-ID: From: Gregory Maxwell To: Jameson Lopp Content-Type: text/plain; charset=UTF-8 X-Spam-Score: 1.1 (+) 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 (gmaxwell[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 1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see ] 1.5 SF_NO_SPF_SPAM SF_NO_SPF_SPAM X-Headers-End: 1WXA9s-0004bm-5Q Cc: Bitcoin Development 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2014 14:04:21 -0000 On Mon, Apr 7, 2014 at 6:58 AM, Jameson Lopp wrote: > The Bitnodes project updated their counting algorithm a month or so ago. It used to be slower and less accurate - prior to their update, it was reporting in excess of 100,000 nodes. Nah. It reported multiple metrics. The "100,000" number was an mostly useless metric that just counted the number of distinct addr messages floating around the network, which contains a lot of junk. They also reported an actual connectable node count previously and while they may have tweaked things here and there as far as I can tell it has been consistent with the numbers they are using in the headlines now.