i originally supported both keysend and lnaddress, but ill be honest, im not smart enough to figure out how to get both to work.
i will fix the tag to use lnaddress though right away. thank you.
nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 There is a small issue with your feed. The value recipient types should be lnaddress rather than lightning-address: https://sessions.soapbox.pub/rss.xml .
Also, the podcasting world hasn't fully figured out the switch from keysend to lnaddress. So if you want to see boost information (sender name, total unsplit amount, message, etc), you have to use keysend rather than lnaddress. I think Fountain might work regardless since it also posts this info to Nostr?
Discussion
okay this should be fixed. thank you again.
i am still very noobish in the RSS world, but i hope to get better and figure all of this out. i've been fixing issues all morning :)
I just tested at https://podcastindex.org/podcast/7473968 and it all seems to work. I got sats.
Unfortunately you have to pick one or the other. Alby and Fountain are basically the only two that support keysend, but they're the two that most podcasters use right now. Other wallets like Strike or Primal only support lnaddress and don't support keysend.
You can look up the keysend info for a person through the well-known url. For example, my well-known (ericpp@getalby.com) is at https://getalby.com/.well-known/keysend/ericpp . That gives you my lightning node pubkey and a custom key/value for my wallet (basically a wallet id).
You can then use the pubkey, custom key, and custom value to create a valueRecipient tag:
oh. i was not aware of the keysend well-known url. all of this is very interesting and something to consider. that said, nostr:npub13ql75nq8rldygpkjke47y893akh5tglqtqzs6cspancaxktthsusvfqcg7 did mention using 'lnurlp' last year. im hoping that we can find a solution that works best for the average person.
Yeah lnaddress/lnurlp is what we want to move towards, but the boost metadata issue has been tricky.
Keysend lets you attach arbitrary metadata (TLVs) along with your payment, which is how boosts work right now. The payments and boost metadata arrive directly to your wallet/node without any third-party involvement.
Lnurlp doesn't have the same flexibility and only gives you a 200 character comment field to use, which is too small for our purposes. We basically need a service or api or something to store the metadata for each payment and there's no agreement on how that should work.
Nostr solved this problem by having the lnurlp server post the metadata back to Nostr as a zap receipt whenever receiving a payment. There's still some ambivalence about using Nostr or any third-party service in the podcast world.