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 1Wmfd5-0003g1-Mm for bitcoin-development@lists.sourceforge.net; Tue, 20 May 2014 08:42:35 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.47 as permitted sender) client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f47.google.com; Received: from mail-oa0-f47.google.com ([209.85.219.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wmfd4-0006Xo-Ah for bitcoin-development@lists.sourceforge.net; Tue, 20 May 2014 08:42:35 +0000 Received: by mail-oa0-f47.google.com with SMTP id i7so142064oag.34 for ; Tue, 20 May 2014 01:42:28 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.144.161 with SMTP id sn1mr1444564obb.82.1400575348742; Tue, 20 May 2014 01:42:28 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.162 with HTTP; Tue, 20 May 2014 01:42:28 -0700 (PDT) Received: by 10.76.71.162 with HTTP; Tue, 20 May 2014 01:42:28 -0700 (PDT) In-Reply-To: References: Date: Tue, 20 May 2014 10:42:28 +0200 X-Google-Sender-Auth: NERlcpX4a1JMPcCuLbk5gZ4oDgw Message-ID: From: Mike Hearn To: bitcoingrant@gmx.com Content-Type: multipart/alternative; boundary=089e0158ac7824a1a504f9d0dc16 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1Wmfd4-0006Xo-Ah 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:42:35 -0000 --089e0158ac7824a1a504f9d0dc16 Content-Type: text/plain; charset=UTF-8 Yeah I'm expecting port 8333 to go away in China at some point. Actually I was expecting that years ago and was kind of surprised that the suppression was being done via banks. Guess the GFW operators were just slow to catch up. On 20 May 2014 10:16, wrote: > 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 > *To:* "Mike Hearn" > *Cc:* "Bitcoin Dev" > *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 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 >> > > ------------------------------------------------------------------------------ > 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 > > > --089e0158ac7824a1a504f9d0dc16 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yeah I'm expecting port 8333 to go away in China at some= point. Actually I was expecting that years ago and was kind of surprised t= hat the suppression was being done via banks. Guess the GFW operators were = just slow to catch up.

On 20 May 2014 10:16, <bitcoingrant@gmx.com> wrote:
Recently China has updated its firew= all blocking bitcoin sites and pools. Whether this is simple blacklist or m= ore=C2=A0sophisticated=C2=A0packet targeting is uncertain, however t= his update did spefically target VPN handshakes.
=C2=A0
Sent:=C2=A0Monday, April 07, 2014 a= t 1:07 PM
From:=C2=A0Drak <drak@zikula.org>
To:=C2=A0"Mike Hearn" <mike@plan99.net>
Cc:=C2=A0"Bitcoin Dev" <bitcoin-development@lists.s= ourceforge.net>
Subject:=C2=A0Re: [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 bitco= in trading in China.
=C2=A0
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,50= 0 and still falling:
=C2=A0
=C2=A0
I know all the reasons why people might=C2=A0stop running a nod= e (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 o= n? 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/M= ac), which would be expected, or from virtual servers (Linux), which would = be more concerning.
=C2=A0
When you set up a Tor node, you can add your email address to the conf= ig 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 sur= vey: if your node disappears for long enough, we could email the operator a= nd 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-de= velopment
=C2=A0
---------------------------------------------------------------------------= --- Put Bad Developers to Shame Dominate Development with Jenkins Continuou= s Integration Continuously Automate Build, Test & Deployment Start a ne= w project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees____________________________________= ___________ Bitcoin-development mailing list Bitcoin-development@li= sts.sourceforge.net https://lists.sourceforge.net/l= ists/listinfo/bitcoin-development
=C2=A0
=C2=A0
--089e0158ac7824a1a504f9d0dc16--