From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Rba5C-0008Pt-1u for bitcoin-development@lists.sourceforge.net; Fri, 16 Dec 2011 15:52:26 +0000 X-ACL-Warn: Received: from mail-vw0-f47.google.com ([209.85.212.47]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Rba56-0002We-0F for bitcoin-development@lists.sourceforge.net; Fri, 16 Dec 2011 15:52:25 +0000 Received: by vbbfc21 with SMTP id fc21so3567112vbb.34 for ; Fri, 16 Dec 2011 07:52:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.173.197 with SMTP id bm5mr6404790vdc.7.1324050734264; Fri, 16 Dec 2011 07:52:14 -0800 (PST) Received: by 10.52.37.80 with HTTP; Fri, 16 Dec 2011 07:52:14 -0800 (PST) In-Reply-To: References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com> <1323791208.31194.YahooMailNeo@web121013.mail.ne1.yahoo.com> <201112131622.08158.andyparkins@gmail.com> Date: Fri, 16 Dec 2011 07:52:14 -0800 Message-ID: From: Rick Wesson To: slush Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.3 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 HS_INDEX_PARAM URI: Link contains a common tracker pattern. 0.3 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Rba56-0002We-0F Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2011 15:52:26 -0000 On Thu, Dec 15, 2011 at 4:07 PM, slush 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:
" 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 wro= te: >> >> On 2011 December 13 Tuesday, Amir Taaki wrote: >> >> > Maybe I wasn't clear enough in the document, but this is the intent wi= th >> > the HTTPS proposal. >> >> I don't like the idea of a hard-coded mapping at all. =A0We shouldn't be >> making >> choices on behalf of server operators. =A0It's up to them how they arran= ge >> their >> domain names and paths. >> >> I also agree that DNS is not the technology to use. =A0DNS is a nightmar= e. >> >> > genjix@foo.org >> > >> > Contacts https://foo.org/bitcoin-alias/?handle=3Dgenjix 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 =3D strDomain + "/bitcoin-alias/?handle=3D" + >> > pszEncodedNick; >> > >> > Between HTTPS service and server service, I lean slightly towards HTTP= S >> > (automatic encrypted connection, CAs + all benefits of DNS). But still >> > interested in arguments in favour of a server service (daemon answerin= g >> > queries). >> >> Why bother with an encoding scheme at all? =A0If the address >> >> =A0genjix@foo.org >> >> always maps to >> >> =A0https://foo.org/bitcoin-alias/?handle=3Dgenjix >> >> Then forget the hardcoding of "https" the hardcoding of "bitcoin-alias" >> and >> "?handle=3D" and the original email-looking "genjix@foo.org". =A0Just us= e the >> URL. >> Then the author of the service can use whatever they want. >> >> =A0"Can I pay you 10 BTC?" >> =A0"Sure, send it to 'https://bitcoinalias.foo.org/genjix/'" >> >> While I might implement my alias server like this: >> >> =A0"Sure, send it to 'https://google.com/bitcoin/?andyparkins'" >> =A0"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. = =A0The >> world is already very familiar with URLs so this is no more scary than t= he >> email address. =A0What's more, the email address form looks _too much_ l= ike >> an >> email address, and will only lead to confusion ... "send it to >> genjix@foo.org" >> "so I use outlook express for that, right?" =A0"erm, no, you put it in y= our >> 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 =A0"https://" can be optional = when >> they're typing. =A0If, 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 >> andyparkins@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 Optimizatio= n >> 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! =A0Tuesday, 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 i= t > 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 >