keysend is not too much about wallet support, but the type of LN node behind it. If your node is a mostly a private node (unannounced channels) it will be almost impossible to be reached by a keysend payment. Why? Because even that you keep it online for a certain time when is about to receive the payment, the other nodes still do not have a 100% updated LN graph to "know" in real time about your private node that is online. You will depend of a LSP / public node with which you have a channel, to be connected to the rest of the graph. Blixt wallet (private node mobile wallet) for example, tried to deal with this issue and was adding the route hints payments into a special QR code for the node. But that QR code can be read only by other Blixt user (for now) and yes you can send keysend payments between 2 private nodes perfectly fine, even that they do not use the same LSP. Zeus also have the option to receive keysend, but still have some issues with the routing hints. So the conclusion is that if you want to receive properly keysend, you must have at least 2-3 public channels and always online node. You do not need any other wallet app, simply your LN node is enough.

That's what some of us including myself do but it's a lot to ask a user to setup. LND node with public channels for receiving and then add AlbyHub on top for sending since it has NWC and the other podcasting 2.0 apps support Alby with OAuth sign in.

I know, is a pain. For this use case, NWC is better than keysend because you can use it with whatever LN node, including a private/mobile one. I strongly suggest also to look into Lightning Pub / ShockWallet for regular users. Lightning Pub is a simple LND node in neutrino mode installed with just one line command and run behind any router, no need for any open ports or Tor or complicated setup. It also use automated liquidity or manual. You connect Shockwallet on multiple devices and is using NWC and CLINK for communications.

I've looked into lightning.pub a little in the past. Is shockwallet the front end wallet for it then?

NWC is a protocol that connects apps to wallets and supports paying invoices and paying keysend. Wallets can choose to support one or the other or preferably both.

GitHub

nips/47.md at master · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

GitHub

nips/47.md at master · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

The reason we prefer keysend is because it doesn't require a bunch of extra LNURL/HTTP infrastructure to make it work. Your wallet pays another wallet directly on the Lightning Network and that's it.