Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.93 as permitted sender)
	client-ip=62.13.148.93; envelope-from=pete@petertodd.org;
	helo=outmail148093.authsmtp.net; 
Date: Fri, 23 May 2014 18:17:26 -0400
From: Peter Todd <pete@petertodd.org>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Message-ID: <20140523221726.GA30143@petertodd.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
Precedence: list


--2fHTh5uZTiUOsy+g
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

FWIW

That said, keep in mind the github discussion(1) that was had: if all
the DNS seeds being down breaks your application, your application is
broken and insecure. The only exception is initial startup, and even
then you should have fallbacks such as hardcoded node lists and manual
peer entry. If for some reason you really do need instant startup, run
your own centralized high-availability/low-latency nodes; either way
you're depending on a centralized resource.

1) https://github.com/bitcoin/bitcoin/pull/4203

--=20
'peter'[:-1]@petertodd.org

--2fHTh5uZTiUOsy+g
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBCAAGBQJTf8j2AAoJEBmcgzuo5/CFrb4H/jNiAaM9bitqOjvphX+kDa9g
DI49LTWoVkokAxrw4jo8hn7KCQ3s+EXCONm6GaZylHXt9p4XrqBRM/PhdwOPEVWL
G8757hy2MDqYpevw0Z0AqXgb9hqbep7ao/p/pGWOlkcpkBLm3x3/Gs2VlErTwlpC
22zHrpkOwiMGphE7hrhJoEft6V2I7lb7xzTWG0Y/f74q3BnrWuDCjixq0PZYK3MS
Jaiym7QIa1pbrJNuvp3gowT+QMoX2qv7213uVAYOfeuMtcIt1mxR2zvFXNLqLtc0
4NrGM9wkCjDR1Qy33RioPHrn8l+6eBF+VzQD/CqnaawBIj2NZ4vz0w+EsUz8VTk=
=MreJ
-----END PGP SIGNATURE-----

--2fHTh5uZTiUOsy+g--