Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <bo.bjornsen@gmail.com>) id 1WmJqQ-0007nH-FU
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 09:26:54 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.170 as permitted sender)
	client-ip=209.85.217.170; envelope-from=bo.bjornsen@gmail.com;
	helo=mail-lb0-f170.google.com; 
Received: from mail-lb0-f170.google.com ([209.85.217.170])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WmJqP-0004QC-EV
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 09:26:54 +0000
Received: by mail-lb0-f170.google.com with SMTP id w7so3815028lbi.15
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 19 May 2014 02:26:46 -0700 (PDT)
X-Received: by 10.152.20.194 with SMTP id p2mr25858107lae.13.1400491606601;
	Mon, 19 May 2014 02:26:46 -0700 (PDT)
Received: from [172.17.3.20] ([109.247.232.34])
	by mx.google.com with ESMTPSA id n3sm19218093lan.3.2014.05.19.02.26.44
	for <bitcoin-development@lists.sourceforge.net>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 19 May 2014 02:26:45 -0700 (PDT)
Message-ID: <5379CE4D.5040100@gmail.com>
Date: Mon, 19 May 2014 11:26:37 +0200
From: =?ISO-8859-1?Q?Bj=F8rn_=D8ivind_Bj=F8rnsen?=
 <bo.bjornsen@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CA+8=xu+GPykmKdAjxLdRA3QoCPR8azervT9uO-GVraNowAb49g@mail.gmail.com>
In-Reply-To: <CA+8=xu+GPykmKdAjxLdRA3QoCPR8azervT9uO-GVraNowAb49g@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="sur35UQFgRUo17kJXKgIUVwhdK3NEbkwG"
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
	(bo.bjornsen[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: 1WmJqP-0004QC-EV
Subject: Re: [Bitcoin-development] About the small number of bitcoin nodes
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: Mon, 19 May 2014 09:26:54 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--sur35UQFgRUo17kJXKgIUVwhdK3NEbkwG
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 18/05/14 19:43, Ra=FAl Mart=EDnez wrote:
> About the small number of bitcoin nodes:
> Hi, I read the message that Mike Hearn sent to this mailing list some
> days ago (2014-04-07 11:34:43) related to the number of bitcoin full no=
des.
>=20
> As an owner of two Bitcoin Nodes, one in my home computer and one in a
> dedicated server, I believe I can contribute with some of my thoughts
> and ideas:
>=20
> <snip some good ideas>

As an interested party not intimately familiar with the bitcoin codebase
who also spent some time setting up a node a while ago, I would like to
add one thing to the above list - network rate limiting.
When I first set up my node, I did not consider this until it started
eating all of my upstream bandwith (on an ADSL line that isn't so fun),
and I must admit I was a bit disappointed when I found that I would have
to set this up separately. An option to limit the upstream and
downstream network usage (like what tor or most torrent clients does)
would be useful.

On the note of the distro packages, I've so far been pretty happy with
the packages provided by Arch Linux - I have no idea if they build it
correctly (with the correct static libs and all), but it seems to work
fine for the edge router case.

Bj=F8rn =D8ivind



--sur35UQFgRUo17kJXKgIUVwhdK3NEbkwG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJTec5UAAoJEL7WgfZSg+BMayoP/iP5OPL5/PEEPM7jlgCcqUm/
j3xAVvJaQYL6zy8enb7iwgiIQAVAMPh4TB6+6klJ1OXc/CosBsjgawVpL/JTyS5u
5n+JMZghqxU/0o7U4Ro+dOujaG6BH4GkWNVhEkWnZr2gLZhxhAs64IedMccF0m57
IXp0XpM9udeXFjwEm2KL+tIaV2j7yzbaOBW879MjNDXuQw/t9BRwTZPTo+H5V12R
t0EQQK3lY3HDDK0lFa0WBNydwVko2i9BijIAdrilk413gvGZb3m9LaZMlv55TPSq
UeRKelxMIl3rRreklUUR4dOX+P5LFLVJwbbWrVZ78Cap3E/KCFH8l6nkK4roq451
5fRcWt9WldYaL57R94o8HrxpdM0cQWRMXHuYNZDXFOnXyh9gg3i4uYfO2wjsA7Tw
f1ix7cK5euqXj59gr8/7SsRamsSI88wm1OqSd/ACN+7uwmpJTqu0o2EicqH2xDWt
8MJ5wPr77dWhg3/FFARMOElPhVidbrw2YISizsP2g8ew39bpyLdw8LNgMhL+wzPO
Kb7ER9HLR0W8T6Q5s+x2IKoCUIXIbC5C0fDjtRWS82MYmnDfsgTdKOYBgKNl4AG8
4woGvMb/WtMNOTTl3yw0fpe9Py7CJD2f+HcTpCbcQWP/LVCNcZP0SBv4u5XVeQ2D
2MF52sFCjaisIkfamvi6
=fGzQ
-----END PGP SIGNATURE-----

--sur35UQFgRUo17kJXKgIUVwhdK3NEbkwG--