On Thu, Dec 15, 2011 at 4:07 PM, slush <sl...@centrum.cz> wrote: > 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.
wow, really. Maybe you could review some RFCs, there are thousands of examples where some really smart engineers chose the exact opposite path which you propose below. -rick > 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. > > Best, > slush > > On Tue, Dec 13, 2011 at 5:22 PM, Andy Parkins <andypark...@gmail.com> wrote: >> >> On 2011 December 13 Tuesday, Amir Taaki wrote: >> >> > Maybe I wasn't clear enough in the document, but this is the intent with >> > the HTTPS proposal. >> >> I don't like the idea of a hard-coded mapping at all. We shouldn't be >> making >> choices on behalf of server operators. It's up to them how they arrange >> their >> domain names and paths. >> >> I also agree that DNS is not the technology to use. DNS is a nightmare. >> >> > gen...@foo.org >> > >> > Contacts https://foo.org/bitcoin-alias/?handle=genjix and the system >> > responds with a bitcoin address. Whether the system gives you a new >> > address from a pool of addresses, or contacts the merchant behind the >> > scenes is implementation defined. >> > >> > I'll clarify it later. This is the relevant line: >> > >> > string strRequestUrl = strDomain + "/bitcoin-alias/?handle=" + >> > pszEncodedNick; >> > >> > Between HTTPS service and server service, I lean slightly towards HTTPS >> > (automatic encrypted connection, CAs + all benefits of DNS). But still >> > interested in arguments in favour of a server service (daemon answering >> > queries). >> >> Why bother with an encoding scheme at all? If the address >> >> gen...@foo.org >> >> always maps to >> >> https://foo.org/bitcoin-alias/?handle=genjix >> >> Then forget the hardcoding of "https" the hardcoding of "bitcoin-alias" >> and >> "?handle=" and the original email-looking "gen...@foo.org". Just use the >> URL. >> Then the author of the service can use whatever they want. >> >> "Can I pay you 10 BTC?" >> "Sure, send it to 'https://bitcoinalias.foo.org/genjix/'" >> >> While I might implement my alias server like this: >> >> "Sure, send it to 'https://google.com/bitcoin/?andyparkins'" >> "Sure, send it to 'https://parkins.co.uk/"; >> >> ... or any other URL they want -- any of which suit might suit me and my >> webserver better than whatever mapping would otherwise be hard-coded. The >> world is already very familiar with URLs so this is no more scary than the >> email address. What's more, the email address form looks _too much_ like >> an >> email address, and will only lead to confusion ... "send it to >> gen...@foo.org" >> "so I use outlook express for that, right?" "erm, no, you put it in your >> bitcoin client". >> >> The URL form could easily be made to detect a browser connecting rather >> than a >> bitcoin client (and this is an area that would benefit from a standards >> document -- define the headers and user agent triggers that an alias >> server >> expects) and give them better instructions. >> >> https can be specified as the default, so "https://"; can be optional when >> they're typing. If, in the future, bitcoin gets a distributed >> peer-to-peer >> alias system, then a new URL type can be added easily >> "bcalias://andyparkins" >> might automatically find my node in the network and query it for an >> address >> (or whatever). >> >> All of the above is exactly why OpenID chose to use URLs for ID. >> >> >> >> Andy >> >> -- >> Dr Andy Parkins >> andypark...@gmail.com >> >> >> ------------------------------------------------------------------------------ >> Systems Optimization Self Assessment >> Improve efficiency and utilization of IT resources. Drive out cost and >> improve service delivery. Take 5 minutes to use this Systems Optimization >> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ >> _______________________________________________ >> Bitcoin-development mailing list >> Bitcoin-development@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >> > > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
