public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jameson Lopp <jameson.lopp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
Date: Mon, 07 Apr 2014 09:58:37 -0400	[thread overview]
Message-ID: <5342AF0D.1060209@gmail.com> (raw)
In-Reply-To: <CAAS2fgQxgRjCYEynXmZxMsYkohudBZN7jyJ1hOTft82ppKCQ1A@mail.gmail.com>

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 <gmaxwell@gmail.com> 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
> 



  reply	other threads:[~2014-04-07 13:58 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 11:34 [Bitcoin-development] Why are we bleeding nodes? Mike Hearn
2014-04-07 12:17 ` Ricardo Filipe
2014-04-07 13:43   ` Andreas Schildbach
2014-04-07 14:05     ` Mike Hearn
2014-04-07 14:15       ` Eric Martindale
2014-04-07 14:23         ` Mike Hearn
2014-04-07 19:46         ` Troy Benjegerdes
2014-04-08  3:13         ` kjj
2014-04-08  7:50           ` Mike Hearn
2014-04-09 10:38         ` Wendell
2014-04-09 11:15           ` Wladimir
2014-04-07 14:45       ` Tom Harding
2014-04-07 12:19 ` Jameson Lopp
2014-04-07 12:26   ` Pieter Wuille
2014-04-07 12:34     ` Mike Hearn
2014-04-07 12:34     ` Jameson Lopp
2014-05-20 18:38     ` Isidor Zeuner
2014-04-07 13:50 ` Gregory Maxwell
2014-04-07 13:53   ` Gregory Maxwell
2014-04-07 13:58     ` Jameson Lopp [this message]
2014-04-07 14:04       ` Gregory Maxwell
2014-04-08 11:28   ` Jesus Cea
2014-04-07 15:45 ` Justus Ranvier
2014-04-07 15:53   ` Gregory Maxwell
2014-04-07 16:02     ` Jameson Lopp
2014-04-07 16:27     ` Mark Friedenbach
2014-04-07 16:57       ` Gregory Maxwell
2014-04-07 17:01         ` Mark Friedenbach
2014-04-07 17:16           ` Gregory Maxwell
2014-04-07 17:35             ` Brent Shambaugh
2014-04-07 17:40               ` Mike Hearn
2014-04-07 17:44                 ` Gregory Maxwell
2014-04-07 17:45                 ` Tamas Blummer
2014-04-07 17:50                 ` Justus Ranvier
2014-04-07 18:30                   ` Arne Brutschy
2014-04-07 17:56                 ` Brent Shambaugh
2014-04-07 17:46             ` Justus Ranvier
2014-04-07 17:39     ` Chris Williams
2014-04-07 18:23       ` Mike Hearn
2014-04-07 18:35         ` Tamas Blummer
2014-04-07 18:49           ` Gregory Maxwell
2014-04-07 19:00             ` Tamas Blummer
2014-04-07 18:48               ` Mark Friedenbach
2014-04-07 19:02               ` Gregory Maxwell
2014-04-07 19:05                 ` Tamas Blummer
2014-04-07 19:03               ` Gregory Maxwell
2014-04-07 19:13                 ` Tier Nolan
2014-04-07 19:20                 ` Tamas Blummer
2014-04-07 19:13                   ` Mark Friedenbach
2014-04-07 19:36                     ` Tamas Blummer
2014-04-07 21:46                     ` Ricardo Filipe
2014-04-07 19:30                   ` Paul Lyon
2014-04-07 19:50                     ` Tamas Blummer
2014-04-07 21:48                       ` Tier Nolan
2014-04-07 21:56                         ` Gregory Maxwell
2014-04-08  3:44             ` Jeff Garzik
2014-04-08  7:24               ` Jean-Paul Kogelman
2014-04-08  7:59               ` Tamas Blummer
2014-04-08 17:18       ` Andrew LeCody
2014-04-07 17:07 ` Drak
2014-05-20  8:15   ` bitcoingrant
2014-05-20  8:42     ` Mike Hearn
2014-05-20 14:37     ` Eugen Leitl
2014-05-20 14:52       ` Gmail
2014-05-20 18:46         ` Andy Alness
2014-05-20 19:17           ` Jeff Garzik
2014-05-20 20:09             ` Andy Alness
2014-05-20 20:22               ` Jeff Garzik
2014-04-07 21:55 Paul Lyon
2014-04-07 22:14 ` Tier Nolan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5342AF0D.1060209@gmail.com \
    --to=jameson.lopp@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox