Are we designing protocols or applications, its easier and better for all involved if we design a protocol and then let the applications implement it. <div><br></div><div>Lets stick to understanding how labels (dns) or URIs can be leveraged to securly obtain a bitcoin address, rather than reviewing capabilities of current applications.</div>
<div><br></div><div>-rick</div><div><br><div class="gmail_quote">On Wed, Dec 14, 2011 at 10:04 PM, Zell Faze <span dir="ltr"><<a href="mailto:zellfaze@yahoo.com">zellfaze@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<table cellspacing="0" cellpadding="0" border="0"><tbody><tr><td valign="top" style="font:inherit">It is a lot easier to set up an HTTP server to dynamically respond with addresses than a DNS record. It is considered a good practice to use a different address for every payment.<br>
<br>------------------------<br>"It stopped being just a website a long time ago. For many of us, most of us, Wikipedia has become an indispensable part of our daily lives."<br>— Jimmy Wales, <i>Founder of Wikipedia</i> <br>
<a rel="nofollow" href="http://2e740a1a.qvvo.com/" target="_blank"></a><tt></tt><p style="MARGIN-TOP:0px"><tt>Help protect it now. Please make a donation today: <a rel="nofollow" title="http://www.wikimediafoundation.org/wiki/Donate" href="http://www.wikimediafoundation.org/wiki/Donate" target="_blank">http://www.wikimediafoundation.org/wiki/Donate</a></tt><br>
</p><br><br>--- On <b>Wed, 12/14/11, Kyle Henderson
<i><<a href="mailto:k@old.school.nz" target="_blank">k@old.school.nz</a>></i></b> wrote:<br><blockquote style="border-left:2px solid rgb(16,16,255);margin-left:5px;padding-left:5px"><br>From: Kyle Henderson <<a href="mailto:k@old.school.nz" target="_blank">k@old.school.nz</a>><div class="im">
<br>Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases<br></div>To: "Zell Faze" <<a href="mailto:zellfaze@yahoo.com" target="_blank">zellfaze@yahoo.com</a>><br>Cc: "Luke-Jr" <<a href="mailto:luke@dashjr.org" target="_blank">luke@dashjr.org</a>>, "Rick Wesson" <<a href="mailto:rick@support-intelligence.com" target="_blank">rick@support-intelligence.com</a>>, <a href="mailto:bitcoin-development@lists.sourceforge.net" target="_blank">bitcoin-development@lists.sourceforge.net</a><br>
Date: Wednesday, December 14, 2011, 11:56 PM<div><div class="h5"><br><br><div>Just so we're clear, what is the need for HTTP at all?<br><br>A query for a string and an answer can all be handled via DNS.<br><br><div>On Thu, Dec 15, 2011 at 4:57 PM, Zell Faze <span dir="ltr"><<a rel="nofollow" href="http://mc/compose?to=zellfaze@yahoo.com" target="_blank">zellfaze@yahoo.com</a>></span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Could we combine this proposal and the HTTPS proposal?<br>
<br>
The DNSSEC TXT record could give instructions on how to query an HTTPS server to get the address. Then we get the dynamism of HTTPS without having a rigid URL scheme for querying the server along with the advantages of DNSSEC.<br>
<br></blockquote></div><br>
</div></div></div></blockquote></td></tr></tbody></table></blockquote></div><br></div>