<oembed><type>rich</type><version>1.0</version><author_name>npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58</author_name><author_url>https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-05-15&#xA;📝 Original message:On Thu, May 15, 2014 at 7:50 AM, Andreas Schildbach&#xA;&lt;andreas at schildbach.de&gt; wrote:&#xA;&gt; I&#39;m bringing this issue up again. The current Bitcoin DNS seed&#xA;&gt; infrastructure is unstable. I assume this is because of we&#39;re using a&#xA;&gt; custom DNS implementation which is not 100% compatible. There have been&#xA;&gt; bugs in the past, like a case sensitive match for the domain name.&#xA;&#xA;While I agree that the problem seeds should be fixed, it also sounds&#xA;like a problem with bitcoinj / other layers, if a malfunctioning seed&#xA;is a problem for your app.&#xA;&#xA;Seeds are fundamentally a backup for peer exchange.  You are going to&#xA;run into problems if you rely 100% on seeds, always.&#xA;&#xA;Further, there are multiple seeds so that we are not impacted if a&#xA;couple seeds malfunction or die.  All bitcoin apps must take this into&#xA;account.&#xA;&#xA;-- &#xA;Jeff Garzik&#xA;Bitcoin core developer and open source evangelist&#xA;BitPay, Inc.      https://bitpay.com/</html></oembed>