Kinda sorta very much a lot pumped cause ive seen some of the cool shit youve done (relay.tools).

As I understand it... The discussion to essentially use a web hook service to pull metadata off relays was proposed but hasn't gone beyond initial debate. As someone with expertise in relays, your opinion could be valuable. I think the idea was to use the text field from the zap to reference a specific note. That note would contain the boost data. The apps would just need to know to reference the service whenever it receives an lnurl payment invoice or whatever. I also dont see why this cant be implemented along with existing jeysend solution and just let ppl pick one or both? Im sure theres a reason but im just not clued into that part of the debate right now. (Would love to get caught up)

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. @Fountain 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.