I really like this proposal with standard URLs. All other proposals like DNS mapping or email aliases converted to URLs with some weird logic looks strange to me.<div><br></div><div>Plain URLs (returning address in response body, redirecting to URI "bitcoin:<address>" or anything else) are very clear solution, easy to implement in clients and very easy to understand by people. It's also extremely flexible - almost everybody can somewhere setup static file containing his "personal" addresses or it's very easy to integrate such solution with eshops (providing custom address for given order) etc. I'm definitely for this solution.<div>
<br></div><div>Best,</div><div>slush</div><div><br><div class="gmail_quote">On Tue, Dec 13, 2011 at 5:22 PM, Andy Parkins <span dir="ltr"><<a href="mailto:andyparkins@gmail.com">andyparkins@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 2011 December 13 Tuesday, Amir Taaki wrote:<br>
<br>
> Maybe I wasn't clear enough in the document, but this is the intent with<br>
> the HTTPS proposal.<br>
<br>
</div>I don't like the idea of a hard-coded mapping at all. We shouldn't be making<br>
choices on behalf of server operators. It's up to them how they arrange their<br>
domain names and paths.<br>
<br>
I also agree that DNS is not the technology to use. DNS is a nightmare.<br>
<div class="im"><br>
> <a href="mailto:genjix@foo.org">genjix@foo.org</a><br>
><br>
> Contacts <a href="https://foo.org/bitcoin-alias/?handle=genjix" target="_blank">https://foo.org/bitcoin-alias/?handle=genjix</a> and the system<br>
> responds with a bitcoin address. Whether the system gives you a new<br>
> address from a pool of addresses, or contacts the merchant behind the<br>
> scenes is implementation defined.<br>
><br>
> I'll clarify it later. This is the relevant line:<br>
><br>
> string strRequestUrl = strDomain + "/bitcoin-alias/?handle=" +<br>
> pszEncodedNick;<br>
><br>
> Between HTTPS service and server service, I lean slightly towards HTTPS<br>
> (automatic encrypted connection, CAs + all benefits of DNS). But still<br>
> interested in arguments in favour of a server service (daemon answering<br>
> queries).<br>
<br>
</div>Why bother with an encoding scheme at all? If the address<br>
<br>
<a href="mailto:genjix@foo.org">genjix@foo.org</a><br>
<br>
always maps to<br>
<br>
<a href="https://foo.org/bitcoin-alias/?handle=genjix" target="_blank">https://foo.org/bitcoin-alias/?handle=genjix</a><br>
<br>
Then forget the hardcoding of "https" the hardcoding of "bitcoin-alias" and<br>
"?handle=" and the original email-looking "<a href="mailto:genjix@foo.org">genjix@foo.org</a>". Just use the URL.<br>
Then the author of the service can use whatever they want.<br>
<br>
"Can I pay you 10 BTC?"<br>
"Sure, send it to '<a href="https://bitcoinalias.foo.org/genjix/" target="_blank">https://bitcoinalias.foo.org/genjix/</a>'"<br>
<br>
While I might implement my alias server like this:<br>
<br>
"Sure, send it to '<a href="https://google.com/bitcoin/?andyparkins" target="_blank">https://google.com/bitcoin/?andyparkins</a>'"<br>
"Sure, send it to '<a href="https://parkins.co.uk/" target="_blank">https://parkins.co.uk/</a>"<br>
<br>
... or any other URL they want -- any of which suit might suit me and my<br>
webserver better than whatever mapping would otherwise be hard-coded. The<br>
world is already very familiar with URLs so this is no more scary than the<br>
email address. What's more, the email address form looks _too much_ like an<br>
email address, and will only lead to confusion ... "send it to <a href="mailto:genjix@foo.org">genjix@foo.org</a>"<br>
"so I use outlook express for that, right?" "erm, no, you put it in your<br>
bitcoin client".<br>
<br>
The URL form could easily be made to detect a browser connecting rather than a<br>
bitcoin client (and this is an area that would benefit from a standards<br>
document -- define the headers and user agent triggers that an alias server<br>
expects) and give them better instructions.<br>
<br>
https can be specified as the default, so "https://" can be optional when<br>
they're typing. If, in the future, bitcoin gets a distributed peer-to-peer<br>
alias system, then a new URL type can be added easily "bcalias://andyparkins"<br>
might automatically find my node in the network and query it for an address<br>
(or whatever).<br>
<br>
All of the above is exactly why OpenID chose to use URLs for ID.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
Andy<br>
<br>
--<br>
Dr Andy Parkins<br>
<a href="mailto:andyparkins@gmail.com">andyparkins@gmail.com</a><br>
</font></span><br>------------------------------------------------------------------------------<br>
Systems Optimization Self Assessment<br>
Improve efficiency and utilization of IT resources. Drive out cost and<br>
improve service delivery. Take 5 minutes to use this Systems Optimization<br>
Self Assessment. <a href="http://www.accelacomm.com/jaw/sdnl/114/51450054/" target="_blank">http://www.accelacomm.com/jaw/sdnl/114/51450054/</a><br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
<br></blockquote></div><br></div></div>