From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] 0.3.24
Date: Fri, 01 Jul 2011 02:07:18 +0200 [thread overview]
Message-ID: <1309478838.3689.25.camel@Desktop666> (raw)
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
Due to the flood control limits becoming an issue again, it would appear
we need a 0.3.24 release. The idea is to have sipa's flood limit fix
(https://github.com/sipa/bitcoin/commit/df94ed7ac0ed7bb3a96cf434ca3c64c4b475e37e), dnsseed on by default, and maybe UPnP enabled by default as well.
I just got a DNSSeed up with reliable hosting which dynamically fills
its hostname with random nodes known to be up and accepting connections
(and on port 8333 and on version 0.3.19 or higher) (dnsseed.bluematt.me)
and I hope others follow suit with
https://github.com/TheBlueMatt/dnsseed (its poorly done but works just
fine). This was added to master in 44d16327. Since its no longer a
static list, I think its time to enable dnsseed by default (I have one
or two connections by the time the GUI opens when I use -dnsseed
-noirc).
Also, I think UPnP by default would be a good idea as it could increase
the percent of nodes which accept incoming connection (and other P2P
applications which depend on the ability to accept incoming connections
have it on by default as well, such as Skype). Jgarzik has also
suggested this, and I really dont see much of a reason not to.
Also,
https://github.com/bitcoin/bitcoin/commit/3a3eabb57ae41dd2162ca8230423abf4a90ef644 should be included to fix the no-connections-up segfault.
Matt
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-07-01 0:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 0:07 Matt Corallo [this message]
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
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=1309478838.3689.25.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