From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1WmfDp-0004Ts-1c for bitcoin-development@lists.sourceforge.net; Tue, 20 May 2014 08:16:29 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmx.com designates 212.227.17.21 as permitted sender) client-ip=212.227.17.21; envelope-from=bitcoingrant@gmx.com; helo=mout.gmx.net; Received: from mout.gmx.net ([212.227.17.21]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WmfDn-0006az-MN for bitcoin-development@lists.sourceforge.net; Tue, 20 May 2014 08:16:29 +0000 Received: from [216.155.145.67] by 3capp-mailcom-bs08 with HTTP; Tue, 20 May 2014 10:15:44 +0200 MIME-Version: 1.0 Message-ID: From: bitcoingrant@gmx.com To: Drak Content-Type: text/html; charset=UTF-8 Date: Tue, 20 May 2014 10:15:44 +0200 Importance: normal Sensitivity: Normal In-Reply-To: References: , X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K0:mCu9yc7VDvHXmKcrlbKkAGsEhWof90He4NKYRRgFBBn gwJLV2n0Eg0wf0rcr49TOfRuVTB8CAPgXMMIOqZBLkUZSY4r1S +ZrfJM3ekgBmv8JoKHeU7bYe7Qd/tMqij1ngbjui0FrUsRE93e CobuPpJwCrEGZJ1Df6Kn0NqGS3PpoMlfsK8S7kdBrKDVOGIKja JFihRf2f86yH0jjbhkpmR7v0VUFc5A7KRkuIcuetRUJuqDD5Td dJDMdLruoSaOiIL4Htba2PdTQ1QqSDL9c5CWBHZoF9Kz/6R947 a6sDLfSzeoVM2JbLT88yj15Gfl3 X-Spam-Score: 1.8 (+) 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 (bitcoingrant[at]gmx.com) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [212.227.17.21 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 2.3 MIME_HTML_ONLY BODY: Message only has text/html MIME parts X-Headers-End: 1WmfDn-0006az-MN Cc: Bitcoin Dev 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: Tue, 20 May 2014 08:16:29 -0000
Recently China has updated its firewall blocking bitcoin sites and pools. Whether this is simple blacklist or more sophisticated packet targeting is uncertain, however this update did spefically target VPN handshakes.
 
Sent: Monday, April 07, 2014 at 1:07 PM
From: Drak <drak@zikula.org>
To: "Mike Hearn" <mike@plan99.net>
Cc: "Bitcoin Dev" <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
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:
 
 
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
 
------------------------------------------------------------------------------ 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_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development