public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Douglas Huff <dhuff@jrbobdobbs.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds returning gone peers
Date: Wed, 3 Aug 2011 16:39:57 +0200	[thread overview]
Message-ID: <CANEZrP0DDkeuDwNZA+WV3LGXp0Q31ZJeJAWiV=6Xm+f=ZusrhQ@mail.gmail.com> (raw)
In-Reply-To: <CAPiTikUc5At5r8XH_5paQ2odx_bib0FGO4OqhGCeQEZ_VRkz0w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 426 bytes --]

>
> There's a bigger problem here honestly. The p2p network is just starved for
> connectable slots.
>
Suggestions:

- massively increasing all the anti-DoS limits in 0.4, so far they've caused
a lot more damage than they solved.

- broadcasting an "upgrade now" type announcement. The alert system is
intended for informing users when there's a threat to system stability and
that's exactly what has been happening recently.

[-- Attachment #2: Type: text/html, Size: 654 bytes --]

  reply	other threads:[~2011-08-03 14:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 10:04 [Bitcoin-development] DNS seeds returning gone peers Mike Hearn
2011-08-03 11:38 ` Matt Corallo
2011-08-03 12:00   ` Mike Hearn
2011-08-03 12:15     ` Johannes Henninger
2011-08-03 12:17       ` Mike Hearn
2011-08-03 12:27   ` Caleb James DeLisle
2011-08-03 12:40     ` Mike Hearn
2011-08-03 14:00 ` Rick Wesson
2011-08-03 14:10   ` Mike Hearn
2011-08-03 14:18     ` Rick Wesson
2011-08-03 14:28       ` Douglas Huff
2011-08-03 14:39         ` Mike Hearn [this message]
2011-08-03 14:48           ` Gregory Maxwell
2011-08-03 15:32             ` Matt Corallo
2011-08-03 14:37       ` Christian Decker

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='CANEZrP0DDkeuDwNZA+WV3LGXp0Q31ZJeJAWiV=6Xm+f=ZusrhQ@mail.gmail.com' \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=dhuff@jrbobdobbs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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