From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.3.24
Date: Fri, 01 Jul 2011 19:50:40 +0200 [thread overview]
Message-ID: <1309542640.2541.20.camel@Desktop666> (raw)
In-Reply-To: <C8D44AB3-1868-4255-9B6C-5AEE72C535C4@jrbobdobbs.org>
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
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:
>
> > 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?
> >>
> >> OK. I mis-remembered the poll:
> >> http://forum.bitcoin.org/index.php?topic=4392.0
> >>
> >> On by default 8 (20%)
> >> Off by default 22 (55%)
> >> On by default in the GUI, off by default in bitcoind 10 (25%)
> >
> > 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).
> >
> > I'm in favor of turning it on by default in the GUI and leaving it off
> > in bitcoind.
> >
> > I don't like UPnP much, I find it exemplifies exactly what is wrong with
> > computer security today: Convenience trumps security almost every time.
>
> 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.
>
> Also: the default will only apply to pre-built binaries, which bitcoind isn'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.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-07-01 17:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 0:07 Matt Corallo
2011-07-01 2:07 ` Gregory Maxwell
2011-07-01 2:44 ` Douglas Huff
2011-07-01 12:41 ` Douglas Huff
2011-07-01 8:00 ` Pieter Wuille
2011-07-01 8:39 ` Jeff Garzik
2011-07-01 12:31 ` Gavin Andresen
2011-07-01 12:40 ` Matt Corallo
2011-07-01 15:06 ` Gavin Andresen
2011-07-01 16:35 ` jan
2011-07-01 16:47 ` Robert McKay
2011-07-01 17:47 ` Douglas Huff
2011-07-01 17:50 ` Matt Corallo [this message]
2011-07-01 17:52 ` Douglas Huff
2011-07-01 22:03 ` Matt Corallo
2011-07-01 22:07 ` Douglas Huff
2011-07-01 17:59 ` Gregory Maxwell
2011-07-01 23:42 ` Jeff Garzik
2011-07-02 0:37 ` Jeff Garzik
2011-07-02 0:46 ` Matt Corallo
2011-07-02 0:51 ` Gregory Maxwell
2011-07-02 1:05 ` Douglas Huff
2011-07-02 1:12 ` Matt Corallo
2011-07-02 2:05 ` Gavin Andresen
2011-07-02 21:07 ` Jeff Garzik
2011-07-03 1:58 ` Matt Corallo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1309542640.2541.20.camel@Desktop666 \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox