This is because for the moment my app only supports keysend. Contact your wallet provider and ask them to support the only truly peer to peer lightning protocol that doesn't rely on censorable things like DNS With that said my app will eventually support zaps as soon as an acceptable solution to the metadata "messages/boostagrams" is solved For now the only wallet solution is alby, though I hear that coinos has finally implemented keysend support but I haven't tested it yet.

I don't really understand, Google is saying keysend enables lightning without invoices... which is what zaps do 😵‍💫 can test with coinos.io

Zaps use lnAddress which uses a DNS reliant server in the backend to create an invoice on your node's behalf. So invoice are still required for zaps, it's just that they are created for you on the backend. lnAddress also limits the amount of characters to around 200. Keysend on the other hand just sends sas directly from node to node with no middleman in between. Even works with Tor. Also keysend supports the TLV record which gives crucial metadata about the boostagram including allowing for much larger messages. See

GitHub

podcast-namespace/docs/examples/value/blip-0010.md at main · Podcastindex-org/podcast-namespace

A wholistic rss namespace for podcasting. Contribute to Podcastindex-org/podcast-namespace development by creating an account on GitHub.

I will probably talk about this in the next episode of v4vmusic as it can get pretty confusing at times. https://v4vmusic.com/?album=cmixpr0vk00f0od0igxv4g9q2