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 1WXC0f-0005gj-Cq for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 16:02:57 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.41 as permitted sender) client-ip=209.85.216.41; envelope-from=jameson.lopp@gmail.com; helo=mail-qa0-f41.google.com; Received: from mail-qa0-f41.google.com ([209.85.216.41]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXC0e-0000qf-Ki for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 16:02:57 +0000 Received: by mail-qa0-f41.google.com with SMTP id j5so6187480qaq.28 for ; Mon, 07 Apr 2014 09:02:51 -0700 (PDT) X-Received: by 10.140.40.47 with SMTP id w44mr3301560qgw.112.1396886571055; Mon, 07 Apr 2014 09:02:51 -0700 (PDT) Received: from [192.168.119.214] (BRONTO-SOFT.car1.Raleigh1.Level3.net. [4.59.160.2]) by mx.google.com with ESMTPSA id u7sm35027648qap.5.2014.04.07.09.02.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Apr 2014 09:02:50 -0700 (PDT) Message-ID: <5342CC29.8050401@gmail.com> Date: Mon, 07 Apr 2014 12:02:49 -0400 From: Jameson Lopp User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <5342C833.5030906@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.6 (-) 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 (jameson.lopp[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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: 1WXC0e-0000qf-Ki 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: Mon, 07 Apr 2014 16:02:57 -0000 I would point to bandwidth as the most important issue to the casual user who runs a node at home. Few casual users have the know-how to set up QoS rules and thus become quite annoyed when their Internet connection is discernibly slowed. - Jameson On 04/07/2014 11:53 AM, Gregory Maxwell wrote: > On Mon, Apr 7, 2014 at 8:45 AM, Justus Ranvier wrote: >> 1. The resource requirements of a full node are moving beyond the >> capabilities of casual users. This isn't inherently a problem - after >> all most people don't grow their own food, tailor their own clothes, or >> keep blacksmith tools handy in to forge their own horseshoes either. > > Right now running a full node consumes about $1 in disk space > non-reoccurring and costs a couple cents in power per month. > > This isn't to say things are all ducky. But if you're going to say the > resource requirements are beyond the capabilities of casual users I'm > afraid I'm going to have to say: citation needed. > > ------------------------------------------------------------------------------ > 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 >