Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qchrn-0004va-U2 for bitcoin-development@lists.sourceforge.net; Fri, 01 Jul 2011 17:50:59 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me designates 208.79.240.5 as permitted sender) client-ip=208.79.240.5; envelope-from=bitcoin-list@bluematt.me; helo=smtpauth.rollernet.us; Received: from smtpauth.rollernet.us ([208.79.240.5]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Qchrk-00021Z-Ot for bitcoin-development@lists.sourceforge.net; Fri, 01 Jul 2011 17:50:59 +0000 Received: from smtpauth.rollernet.us (localhost [127.0.0.1]) by smtpauth.rollernet.us (Postfix) with ESMTP id A5AF1594012 for ; Fri, 1 Jul 2011 10:50:37 -0700 (PDT) Received: from mail.bluematt.me (unknown [IPv6:2001:470:9ff2:2:20c:29ff:fe16:f239]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: @bluematt.me) by smtpauth.rollernet.us (Postfix) with ESMTPSA for ; Fri, 1 Jul 2011 10:50:32 -0700 (PDT) Received: from [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b] (unknown [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b]) by mail.bluematt.me (Postfix) with ESMTPSA id 5868A3F4 for ; Fri, 1 Jul 2011 19:50:42 +0200 (CEST) From: Matt Corallo To: bitcoin-development@lists.sourceforge.net In-Reply-To: References: <1309478838.3689.25.camel@Desktop666> <20110701080042.GA657@ulyssis.org> <1309524016.2541.0.camel@Desktop666> <20110701163558.GA7311@dax.lan.local> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-ZDUAbbRKC4XibV5+/UiP" Date: Fri, 01 Jul 2011 19:50:40 +0200 Message-ID: <1309542640.2541.20.camel@Desktop666> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Rollernet-Abuse: Processed by Roller Network Mail Services. Contact abuse@rollernet.us to report violations. Abuse policy: http://rollernet.us/abuse.php X-Rollernet-Submit: Submit ID 14be.4e0e08e8.7653a.0 X-Spam-Score: -1.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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1Qchrk-00021Z-Ot Subject: Re: [Bitcoin-development] 0.3.24 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: Fri, 01 Jul 2011 17:51:00 -0000 --=-ZDUAbbRKC4XibV5+/UiP Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Totally agree it really shouldnt be a vote, in the end UPnP is bad for an individual (more bandwidth usage, etc), but good for the network. That means people will vote against it, but in the end someone has to make the tough decision and turn it on. Also, bitcoind is prebuilt in the daemon folder on the download archives (though Im not sure about OSX) Matt On Fri, 2011-07-01 at 12:47 -0500, Douglas Huff wrote: > On Jul 1, 2011, at 11:35 AM, jan@uos.de wrote: >=20 > > On Fri, Jul 01, 2011 at 11:06:56AM -0400, Gavin Andresen wrote: > >>> Not sure about OS differentiation, seems...wrong? Maybe disabled by > >>> default on bitcoind but on by default on bitcoin? > >>=20 > >> OK. I mis-remembered the poll: > >> http://forum.bitcoin.org/index.php?topic=3D4392.0 > >>=20 > >> On by default 8 (20%) > >> Off by default 22 (55%) > >> On by default in the GUI, off by default in bitcoind 10 (25%) > >=20 > > I just voted as well and now - with some extra votes in the meantime - > > it's 9 / 22 / 13. So exactly 50/50 between off (22) and some form of on > > (9 + 13). > >=20 > > I'm in favor of turning it on by default in the GUI and leaving it off > > in bitcoind. > >=20 > > I don't like UPnP much, I find it exemplifies exactly what is wrong wit= h > > computer security today: Convenience trumps security almost every time. >=20 > I don't think this should be a vote at all. Given Greg/Matt's numbers it = is a necessity to ensure network stability over the next 90 days. >=20 > Also: the default will only apply to pre-built binaries, which bitcoind i= sn't one of, so for people running bitcoind this default doesn't matter at = all. Just continue building without UPNP support as you're already doing. --=-ZDUAbbRKC4XibV5+/UiP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAABAgAGBQJODgjoAAoJEBrh01BD4I5UcW4P/iGclCwnq1/nfzrj3ORf8dut T4cq4gJMAui1c/S6QU9JvEVnX1JRy9O9cQ2atHAR18RNZfPA718OvIpnDr6oGrVa sUsQFbjqkcEE7FLrrJz3xlo0lRp/KfPpfHyHp1LIIQ5iwMwbWOJxkqqzfs+CfUEH E/A2aSqBOQToy7LSLD2nimeG4MndfSIB/Ub0wd6wi1l9Gkw3rIFRIrPeXVWGB4XS 8RV186AJzp/FRSNJG62WGVZFOOsTFrq/6z7yKhx6XR8PtmX1KoAdCmjN6wJ6YYaQ ZUOFZLLEIskFQFUbQW3bGwnb0PECEEyiDEyHuTwQR1XV3YDWKWdf4g87cDN5fX4u bke5yRqNac+F9eyoeIw5rx7Kx0xVJ5Ls3PIvak9XfLnKS+3HAMPW1pomKACqNn+u AFO0JvrxYwBU2h0Og0+RmDSpJiuH1+OULuRkOdVjZcMH05na6s1QFlaktYF0kptq 4GuIF3YIG78KhZDmXkmS5beOiKloedQ4sTwSlIsxm4O2LNumoFcgefbFr/ifEDvt XWALSgoN8uTp3YojiVKzqG2Gz3WxX6+1XCgNMLJKIka9MxEkZfV7077zn6slGyJ2 /or9z2FTVhGgYNso0KsU/Q9kO6sRtRWXOX/dX7uBzaK4PROHEmbEc6DY5FKyTjYQ uehCTuwDHawMIeWcyMTU =6RJl -----END PGP SIGNATURE----- --=-ZDUAbbRKC4XibV5+/UiP--