diff options
| author | Drak <drak@zikula.org> | 2014-04-07 18:07:09 +0100 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-04-07 17:07:37 +0000 |
| commit | aa975ab345cf9832fc4f5a9e6a11b98b8dd61f8e (patch) | |
| tree | 7df0bee691550f6a1d9f9d623094ccef82d9cf94 | |
| parent | cd6b63f65a65f9ca51d30843ee6db9d49fb814a8 (diff) | |
| download | pi-bitcoindev-aa975ab345cf9832fc4f5a9e6a11b98b8dd61f8e.tar.gz pi-bitcoindev-aa975ab345cf9832fc4f5a9e6a11b98b8dd61f8e.zip | |
Re: [Bitcoin-development] Why are we bleeding nodes?
| -rw-r--r-- | f0/643971321ff1c5ab0225e05d6ef2a5b1ef1a8c | 166 |
1 files changed, 166 insertions, 0 deletions
diff --git a/f0/643971321ff1c5ab0225e05d6ef2a5b1ef1a8c b/f0/643971321ff1c5ab0225e05d6ef2a5b1ef1a8c new file mode 100644 index 000000000..7dbb26500 --- /dev/null +++ b/f0/643971321ff1c5ab0225e05d6ef2a5b1ef1a8c @@ -0,0 +1,166 @@ +Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] + helo=mx.sourceforge.net) + by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <drak@zikula.org>) id 1WXD1F-0002Sw-6x + for bitcoin-development@lists.sourceforge.net; + Mon, 07 Apr 2014 17:07:37 +0000 +Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of zikula.org + designates 209.85.212.182 as permitted sender) + client-ip=209.85.212.182; envelope-from=drak@zikula.org; + helo=mail-wi0-f182.google.com; +Received: from mail-wi0-f182.google.com ([209.85.212.182]) + by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1WXD1E-0003Fq-47 + for bitcoin-development@lists.sourceforge.net; + Mon, 07 Apr 2014 17:07:37 +0000 +Received: by mail-wi0-f182.google.com with SMTP id d1so5439922wiv.15 + for <bitcoin-development@lists.sourceforge.net>; + Mon, 07 Apr 2014 10:07:29 -0700 (PDT) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:mime-version:in-reply-to:references:from:date + :message-id:subject:to:cc:content-type; + bh=7kl+BzG9m/WolKp1JcPiuvZAq4woa9/N9CcsafT2tfs=; + b=aGzd7IvyLmtJNckcG/OOsxXxET05gs1I6oGgTYBSEiOT531RtW+BQ5VKJ0BzsX8J2J + MMY30xxf4AHgTXHtGIn19+Xcvk69JSPC14brrFKB5jPdBMlzm6E/J5kc01h3FscWVhYD + QTv+/MPyvefLCg9fphJOG3wmXiOFqON/vFvzPkX9mppCu8VB5djr/reCCWnLQqSNOHtb + Kz988nxCj+9G8yqLExDDCOSVwwZjZ6Vuiss4UNwSXAJL86z2RJzTh8a/oHQ3NfW2FWRZ + sf/XrGGkZe3iZgVVU6VkCiLEVjTsBdFkhXDdj/Xwb9IcM88WOIO6ZiWCekMC0lSaZJ8p + +ZtQ== +X-Gm-Message-State: ALoCoQlplp7TihNscCOKkiHMj9+2THy6rjLPD9G9RqLMzt1d44xNgG4AqoOZRMolTkvvE8YhbRGf +X-Received: by 10.180.87.233 with SMTP id bb9mr26672196wib.10.1396890449543; + Mon, 07 Apr 2014 10:07:29 -0700 (PDT) +MIME-Version: 1.0 +Received: by 10.194.205.69 with HTTP; Mon, 7 Apr 2014 10:07:09 -0700 (PDT) +In-Reply-To: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com> +References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com> +From: Drak <drak@zikula.org> +Date: Mon, 7 Apr 2014 18:07:09 +0100 +Message-ID: <CANAnSg0ABVyRcSaO2aEcqO8qaj+JdxRN4z-hLE-EbESv2TMf2g@mail.gmail.com> +To: Mike Hearn <mike@plan99.net> +Content-Type: multipart/alternative; boundary=f46d044480af0a955704f676e776 +X-Spam-Score: -0.5 (/) +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 SPF_PASS SPF: sender matches SPF record + 1.0 HTML_MESSAGE BODY: HTML included in message +X-Headers-End: 1WXD1E-0003Fq-47 +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +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: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Mon, 07 Apr 2014 17:07:37 -0000 + +--f46d044480af0a955704f676e776 +Content-Type: text/plain; charset=UTF-8 + +For what it's worth, the number of nodes rose dramatically during the China +bullrun (I recall 45k in China alone) and dropped as dramatically as the +price after the first PBOC announcement designed to cool down bitcoin +trading in China. + + +On 7 April 2014 12:34, Mike Hearn <mike@plan99.net> wrote: + +> At the start of February we had 10,000 bitcoin nodes. Now we have 8,500 +> and still falling: +> +> http://getaddr.bitnodes.io/dashboard/chart/?days=60 +> +> I know all the reasons why people *might* stop running a node (uses too +> much disk space, bandwidth, lost interest etc). But does anyone have any +> idea how we might get more insight into what's really going on? It'd be +> convenient if the subVer contained the operating system, as then we could +> tell if the bleed was mostly from desktops/laptops (Windows/Mac), which +> would be expected, or from virtual servers (Linux), which would be more +> concerning. +> +> When you set up a Tor node, you can add your email address to the config +> file and the Tor project sends you emails from time to time about things +> you should know about. If we did the same, we could have a little exit +> survey: if your node disappears for long enough, we could email the +> operator and ask why they stopped. +> +> +> ------------------------------------------------------------------------------ +> 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 +> +> + +--f46d044480af0a955704f676e776 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr">For what it's worth, the number of nodes rose dramatic= +ally during the China bullrun (I recall 45k in China alone) and dropped as = +dramatically as the price after the first PBOC announcement designed to coo= +l down bitcoin trading in China.</div> + +<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 7 April 20= +14 12:34, Mike Hearn <span dir=3D"ltr"><<a href=3D"mailto:mike@plan99.ne= +t" target=3D"_blank">mike@plan99.net</a>></span> wrote:<br><blockquote c= +lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;= +padding-left:1ex"> + +<div dir=3D"ltr">At the start of February we had 10,000 bitcoin nodes. Now = +we have 8,500 and still falling:<div><br></div><div>=C2=A0 =C2=A0<a href=3D= +"http://getaddr.bitnodes.io/dashboard/chart/?days=3D60" target=3D"_blank">h= +ttp://getaddr.bitnodes.io/dashboard/chart/?days=3D60</a><br> + + +</div><div><br></div><div>I know all the reasons why people <i>might</i>=C2= +=A0stop running a node (uses too much disk space, bandwidth, lost interest = +etc). But does anyone have any idea how we might get more insight into what= +'s really going on? It'd be convenient if the subVer contained the = +operating system, as then we could tell if the bleed was mostly from deskto= +ps/laptops (Windows/Mac), which would be expected, or from virtual servers = +(Linux), which would be more concerning.</div> + + +<div><br></div><div>When you set up a Tor node, you can add your email addr= +ess to the config file and the Tor project sends you emails from time to ti= +me about things you should know about. If we did the same, we could have a = +little exit survey: if your node disappears for long enough, we could email= + the operator and ask why they stopped.</div> + + +</div> +<br>-----------------------------------------------------------------------= +-------<br> +Put Bad Developers to Shame<br> +Dominate Development with Jenkins Continuous Integration<br> +Continuously Automate Build, Test & Deployment<br> +Start a new project now. Try Jenkins in the cloud.<br> +<a href=3D"http://p.sf.net/sfu/13600_Cloudbees_APR" target=3D"_blank">http:= +//p.sf.net/sfu/13600_Cloudbees_APR</a><br>_________________________________= +______________<br> +Bitcoin-development mailing list<br> +<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo= +pment@lists.sourceforge.net</a><br> +<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development= +" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de= +velopment</a><br> +<br></blockquote></div><br></div> + +--f46d044480af0a955704f676e776-- + + |