Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXA4U-0007Oz-Bg for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 13:58:46 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.175 as permitted sender) client-ip=209.85.216.175; envelope-from=jameson.lopp@gmail.com; helo=mail-qc0-f175.google.com; Received: from mail-qc0-f175.google.com ([209.85.216.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXA4S-0004Ei-Ic for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 13:58:46 +0000 Received: by mail-qc0-f175.google.com with SMTP id e16so6352352qcx.20 for ; Mon, 07 Apr 2014 06:58:39 -0700 (PDT) X-Received: by 10.224.25.2 with SMTP id x2mr33719623qab.37.1396879119010; Mon, 07 Apr 2014 06:58:39 -0700 (PDT) Received: from [192.168.119.214] (BRONTO-SOFT.car1.Raleigh1.Level3.net. [4.59.160.2]) by mx.google.com with ESMTPSA id m9sm17510559qae.32.2014.04.07.06.58.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Apr 2014 06:58:38 -0700 (PDT) Message-ID: <5342AF0D.1060209@gmail.com> Date: Mon, 07 Apr 2014 09:58:37 -0400 From: Jameson Lopp User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 (jameson.lopp[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: 1WXA4S-0004Ei-Ic 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 13:58:46 -0000 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. - Jameson On 04/07/2014 09:53 AM, Gregory Maxwell wrote: > On Mon, Apr 7, 2014 at 6:50 AM, Gregory Maxwell wrote: >> FWIW, A few months before that we had even less than 8500 by the bitnodes count. > > Gah, accidentally send.... I wanted to continue here that it was less > than 8500 and had been falling pretty consistently for months, > basically since the bitcoin.org change. Unfortunately it looks like > the old bitnodes.io data isn't available anymore, so I'm going off my > memory here. > > The Bitnodes counts have always been somewhat higher than my or sipa's > node counts too, fwiw. > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees_APR > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >