summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Hearn <mike@plan99.net>2014-05-07 21:50:53 +0200
committerbitcoindev <bitcoindev@gnusha.org>2014-05-07 19:51:00 +0000
commit8ff5f4650e7d465cb5288f3d6f084f339a69f472 (patch)
tree6b8f934d19cc485909b43cad7e53bab56b6ba03f
parent8992af7a6cd2fd35409221c9cb22426963c10af3 (diff)
downloadpi-bitcoindev-8ff5f4650e7d465cb5288f3d6f084f339a69f472.tar.gz
pi-bitcoindev-8ff5f4650e7d465cb5288f3d6f084f339a69f472.zip
Re: [Bitcoin-development] Announcing the Statoshi fork
-rw-r--r--13/1804dd09c37ed621b5f7707dc67262913f01e997
1 files changed, 97 insertions, 0 deletions
diff --git a/13/1804dd09c37ed621b5f7707dc67262913f01e9 b/13/1804dd09c37ed621b5f7707dc67262913f01e9
new file mode 100644
index 000000000..96b384bfc
--- /dev/null
+++ b/13/1804dd09c37ed621b5f7707dc67262913f01e9
@@ -0,0 +1,97 @@
+Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
+ helo=mx.sourceforge.net)
+ by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <mh.in.england@gmail.com>) id 1Wi7ro-00087c-04
+ for bitcoin-development@lists.sourceforge.net;
+ Wed, 07 May 2014 19:51:00 +0000
+Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
+ designates 209.85.214.180 as permitted sender)
+ client-ip=209.85.214.180; envelope-from=mh.in.england@gmail.com;
+ helo=mail-ob0-f180.google.com;
+Received: from mail-ob0-f180.google.com ([209.85.214.180])
+ by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1Wi7rn-0004Ns-1t
+ for bitcoin-development@lists.sourceforge.net;
+ Wed, 07 May 2014 19:50:59 +0000
+Received: by mail-ob0-f180.google.com with SMTP id va2so1850772obc.11
+ for <bitcoin-development@lists.sourceforge.net>;
+ Wed, 07 May 2014 12:50:53 -0700 (PDT)
+MIME-Version: 1.0
+X-Received: by 10.60.146.201 with SMTP id te9mr48512879oeb.38.1399492253601;
+ Wed, 07 May 2014 12:50:53 -0700 (PDT)
+Sender: mh.in.england@gmail.com
+Received: by 10.76.71.162 with HTTP; Wed, 7 May 2014 12:50:53 -0700 (PDT)
+In-Reply-To: <536A8592.8010009@gmail.com>
+References: <536A8592.8010009@gmail.com>
+Date: Wed, 7 May 2014 21:50:53 +0200
+X-Google-Sender-Auth: tKH2yQx9o3PJsJK_pwf-yNF0C4U
+Message-ID: <CANEZrP1A0z0sVBHzW_2Z1RJ6STX9G1RW_KncbY_yN7NuTL8BZw@mail.gmail.com>
+From: Mike Hearn <mike@plan99.net>
+To: Jameson Lopp <jameson.lopp@gmail.com>
+Content-Type: multipart/alternative; boundary=047d7b5d524ea4569d04f8d4ae38
+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: 1Wi7rn-0004Ns-1t
+Cc: "bitcoin-development@lists.sourceforge.net"
+ <bitcoin-development@lists.sourceforge.net>
+Subject: Re: [Bitcoin-development] Announcing the Statoshi fork
+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: Wed, 07 May 2014 19:51:00 -0000
+
+--047d7b5d524ea4569d04f8d4ae38
+Content-Type: text/plain; charset=UTF-8
+
+Really nice! We definitely need to put together a team who really cares
+about the operations side of the network and this is a fantastic start.
+
+It'd be nice if you didn't assume knowledge of what statsd is out of the
+box. Given the name I'd assumed it was a small UNIX daemon but it seems
+it's actually a Javascript thingy?
+
+It looks like putting together a monitored bitcoind setup can be quite a
+lot of work. I wonder if there are ways to simplify it. For example, would
+it make sense for someone to run a community statsd and graphite instance,
+so we can get aggregate statistics across many nodes and the node operators
+don't have to set everything up themselves? Does that make any sense?
+
+--047d7b5d524ea4569d04f8d4ae38
+Content-Type: text/html; charset=UTF-8
+Content-Transfer-Encoding: quoted-printable
+
+<div dir=3D"ltr">Really nice! We definitely need to put together a team who=
+ really cares about the operations side of the network and this is a fantas=
+tic start.<div><br></div><div>It&#39;d be nice if you didn&#39;t assume kno=
+wledge of what statsd is out of the box. Given the name I&#39;d assumed it =
+was a small UNIX daemon but it seems it&#39;s actually a Javascript thingy?=
+</div>
+<div><br></div><div>It looks like putting together a monitored bitcoind set=
+up can be quite a lot of work. I wonder if there are ways to simplify it. F=
+or example, would it make sense for someone to run a community statsd and g=
+raphite instance, so we can get aggregate statistics across many nodes and =
+the node operators don&#39;t have to set everything up themselves? Does tha=
+t make any sense?</div>
+<div><br></div></div>
+
+--047d7b5d524ea4569d04f8d4ae38--
+
+