We originally chose keysend because you can send metadata (sender name, total amount before splits, message, podcast, episode, app name, etc) along with payments through the Lightning network. You didn't need any web server or service sitting in the middle.

Keysend also just lets you send a payment without requiring the other side to generate an invoice first. Most of our feeds have payment splits in them for the podcast hosts, crew, and anyone responsible for putting together a podcast and it's a bit cumbersome to have to generate multiple invoices for every single split.

We've since updated the spec to allow for a Lightning Address to be used in the feed which allows the app to use either keysend or LNURLp depending on what the sending and receiving wallets support.

But we haven't completely figured out how to send the metadata to the recipient since LNURLp doesn't allow the same amount of metadata that keysend does. nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5 solved the issue by posting the metadata as Nostr notes, but some in the community are reluctant to rely on Nostr or don't want their metadata to be publicly available on Nostr.

Reply to this note

Please Login to reply.

Discussion

nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2's proposal that has no feedback besides Yay Nostr and me pointing out the issues we face and being called an idiot.

https://primal.net/merryoscar/open-podcast-payments-with-bitcoin-and-nostr