rich1.0npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydhttps://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydnjumphttps://nostr.ae📅 Original date posted:2014-05-20 📝 Original message: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, <bitcoingrant at gmx.com> 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 <drak at zikula.org> > *To:* "Mike Hearn" <mike at plan99.net> > *Cc:* "Bitcoin Dev" <bitcoin-development at 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 at 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 at 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 at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140520/994e0862/attachment.html>