This way the user can pay the invoice using any wallet type he likes.
I wonder if any crypto service would be interested to implement that. In theory this could be combined with crypto (or even fiat) echange allowing users to use more payment methods.
=> More informations about this toot | View the thread
I'm thinking about some methods that would allow users to use any lightning wallet they like for V4V payments.
One can imagine an API that a hypothetical crypto exchange service could implement: a P2.0 app supplies a list of splits (lightning addresses and corresponding amounts) and get in response a bolt11 invoice for the total sum + some fee. Once the invoice is paid, the service distributes all the splits to their destinations.
=> More informations about this toot | View the thread
So is the lnaddress options file is still a thing or people already decided that it wasn't such a good idea? I just finished implementing that lookup in our Android code 😅
=> More informations about this toot | View the thread
Regarding the "method" attribute of the podcast:value tag. In the specs it's marked as required. We used to have "keysend" there. Now that people are transitioning to lnaddress - do we omit the "method" at the podcast:value level completely? Fountain Radio feed doesn't have it. @merryoscar @dave @StevenB
=> More informations about this toot | View the thread
@adam @dave @merryoscar It would be really cool to allow people to use as many different wallets as possible, but all this stuff is rather new to me and I don't quite see how it is technically possible. Will bolt11 invoices help with that? We are not talking about podcast app users having to manually pay for every split as an invoice?
=> More informations about this toot | View the thread
Regarding the "Walletpocalypse" that's coming (last P2.0 podcast episode). 😀 Is the idea to have more alternatives to Alby to do V4V payments? Alby has Oauth and a nice API for payments and it was quite easy to integrate. Does Strike (or any other alternatives) have that? @adam @dave @merryoscar
=> More informations about this toot | View the thread
@dave Hi! We had been contacted recently by a couple of podcast authors about incorrect/outdated data for their podcasts. The data comes from podcastindex.org API. What's the right way for podcast authors to update their data?
=> More informations about this toot | View the thread
=> This profile with reblog | Go to algrid@podcastindex.social account This content has been proxied by September (3851b).Proxy Information
text/gemini