getaddr.bitnodes.io and the daft announcement posted on march 26th

[zvs]

I couldn't find some specific thread talking about this "service", so..

re:  'Thu Mar 26 2015 02:38:20 GMT-0500 (Central Daylight Time): Crawler restarted: Updated crawler to exclude sybil nodes from 2607:f0d0:1c01:53::0/112 (@af662daf61).'

What is a 'sybil' node?  These nodes you speak of were acting just like any other normal bitcoin nodes, responding to getaddr messages just as any other would.  Normal bitcoin nodes wouldn't connect to all, hmm, 600 or so.

Please don't confuse your monitoring software that spreads like some malignant tumor with a standard bitcoin client, thx

[zvs]

ps, it's a /64 block, not /112, probably should expand that exclusion

[Blazr]

Was it you who was running all those nodes? why are you doing that?

https://www.reddit.com/r/Bitcoin/comments/30ay6u/almost_10_more_full_nodes_since_this_morning/

[Lauda]

What's the deal with this? Are you running those nodes?
This is one of the reason for which the network needs a higher number of nodes. If 500 nodes were like 0.01% of the network, nobody would care about this incident and the decentralization would be much better.

[nubbins]

I'm going to point out that the embarrassment that is getaddr.bitnodes.io doesn't enumerate any clients running older than 0.8.x.

I'll say that again, a different way, for emphasis: Bitnodes isn't counting all the nodes, just the ones reporting a version number of 0.8.x or newer.

"6-7000 nodes? That's not very many!"

No, it isn't.