See also: IRC log
<scribe> scribenick: AdrianHB
[Evan is presenting a talk he gave at WWW2016]
evan: have been working on use
case demos on top of ILP to test things and prove the
value
... looked for images for presentation but had to filter based
on usage rights
... what the image search does is actually look for creative
commons licenses
... many people use pirate bay etc to download content via
torrents but there are streaming service emerging as alts
... which are of course legal vs torrenting (which is only
piracy because there is no way to pay for the content)
... we need a license that is like CC but supports paying the
content producer
... [shows requirements for new strawman license]
... project is based on WebTorrent
... vision is an ecosystem where torrenting is legal because
everyone is paying for their content
... [DEMO: Five Bells Wallet Client] - https://github.com/interledger/five-bells-wallet-client
... simple wallet client for ILP
... bootstraps ILP users (as opposed to core developers)
... [DEMO: Instant.io + Interledger] - https://github.com/emschwartz/webtorrent-ilp
... allows someone to upload a file with a license file
embedded
... downloaders pay the uploader and content producer
... ILP allows this to be done without worrying about
currencies and interoperability of payment networks between
participants
... [Shows a downloader getting a file]
... note that second downloader is now paying the other
downloader as they are seeding the file too
... [Shows wallets of participants]
... note how the payments are rolling in real time
... ILP is efficient enough to facilitate very small payments
and between different systems
... no need for all participants to pick a common payment
network/system
... ILP is a payment standard designed to be used by other
standards
... it is open and neutral so it doesn't force anything built
on top to use a specific network
<jaime-ez> hi, got questions
<zmanian> Does the recipients wallet client need to be online?
<jaime-ez> ok, no iĺl just write
evan: the wallet provides a good starting point for developers that want to use ILP
jamie-ez: do you need to be logged into the wallet to be paid
@jamie-ez - there is a lot of background noise on your line
evan: not to be paid
jamie-ez: how does the sender provide permission to their ledger to send the funds
evan: right now it is based on
the reference implementation of the ILP ledger (five-bells) but
it could be updated to use any ILP-capable ledger
... auth into the ledger is not defined by ILP. The ledger
needs to support ILP and then provide a way to auth sending
transactions in whatever way it wants
<jaime-ez> yes
<justmoon> emschwartz: show "magic"!
<justmoon> (if you haven't already)
<emschwartz> https://github.com/interledger/magic
dmitri: have been hands-on with
the crypto-conditions
... working well so, so far so good
... may be concerns about long fulfillments (time to
unpack)
... figuring it out
justmoon: wrt length of fulfillments, there is a fixed ratio between the string and binary encodings so you can enforce your limits up front
dimitri: that will be something we'll investigate
<Dimitri> python implementation at https://github.com/bigchaindb/cryptoconditions
justmoon: we haven't forgotten
about routing. After establishing crypto-conditions test suite
we'll focus on routing
... plan is to move to a model more like the Internet stack.
I.e. routing at the switch (connector) not sender
... we already tried moving pathfind and the size difference is
already bug
evan: working on the wallet
client and thes routing changes is making it a lot less
complex
... will make implementations in many languages easier
... plan is to make it easier for devs to pick up Interledger
with minimal knowledge of the underlying prototocl
dimitri: is it possible to get the presentation to share?
evan: will send to the list
dimitri: in our impl we are JSON
based so we made a lib to serialize between JSON and string
formats for conditions
... also is it possible to add issues or PRs
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: AdrianHB Inferring Scribes: AdrianHB WARNING: No "Topic:" lines found. Present: ShaneM AdrianHB WARNING: Fewer than 3 people found for Present list! WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting Got date from IRC log name: 20 Apr 2016 Guessing minutes URL: http://www.w3.org/2016/04/20-interledger-minutes.html People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]