TheFockinFury on Nostr: Thinking more about it, this would probably require support from the client too. Like ...

Thinking more about it, this would probably require support from the client too. Like NWC would need to emit a failure event and the client would need to handle it and notify the user to try the zap again? Maybe with a link to the note with the failed zap for the sake of ease of recall? 🤷‍♂️

quoting note1xs5…n2ku

My main beef with Alby (npub1get…0nfm) #NWC is what I perceive to be fragility. Every time I connect my node, I end up having to reconnect it a day or two later because I think the connection is broken.

But I’m realizing that this might only be partially true.

Say I zap someone via NWC. The zap shows up as pending. Sometimes the zap goes through, but sometimes it doesn’t. I only find out about this by refreshing several times. I don’t see a payment from my node, the zap didn’t work… what gives? NWC must be broken.

But as I’ve been using good old fashioned manual zaps I’ve realized it might not be a problem with NWC! Sometimes when I go to zap someone, my nostr client is unable to get an invoice. This could point to an issue with the node that I’m trying to zap. The zap via NWC might just be failing silently because of that.

I just wish there was a way to get that feedback from NWC. Like, “hey your zap failed because we couldn’t get an invoice, go try that again.” #wishlist