On 29 March 2016 at 16:47, Adrian Hope-Bailie <adrian@hopebailie.com> wrote: > On 29 March 2016 at 16:32, Melvin Carvalho <melvincarvalho@gmail.com> > wrote: > >> >> >> On 29 March 2016 at 15:48, Adrian Hope-Bailie <adrian@hopebailie.com> >> wrote: >> >>> This is a higher level function. >>> I.e. I give you some identifier for my account like >>> adrian@mywalletprovider.com and you have a well-defined protocol to >>> resolve the address of my ledger from that. >>> >> >> Have a look what happens when I hover over the link you pasted (image >> attached) >> >> firefox automatically translates it into mailto: >> >> this denotes an email address using a URI >> >> > Right, because in the context of an email program it makes sense to > normalize that to a mailto: URI. > > >> so how do you send money to an email address, this becomes a trivial >> problem with a super ledger, you just send it to the URI >> > > How? I'm not following how I would send money to a mailto: URI? > In a super ledger every entry is a URI, so you just have the mailto: address as the recipient. Problem solved. > > >> >>> >>> Following which you will do path finding to my ledger. >>> >>> If ILP is TCP/IP then we're trying to figure out a good way to do DNS :) >>> >>> On 29 March 2016 at 15:26, Xavier Vas <xavier@tr80.com> wrote: >>> >>>> Adrian, >>>> >>>> Sorry, I'm confused, how's this discussion separate from our discussions >>>> on path finding and routing? How exactly do you define "discovery" vs. >>>> "path finding"? >>>> >>>> Xav >>>> >>>> >>>> >>> >> >
Received on Tuesday, 29 March 2016 15:17:32 UTC