Gigi on Nostr: What's your response to this particular UX issue? ...

What's your response to this particular UX issue?

quoting
nevent1q…lndl

Great article. One thing that wasn't really touched on, although maybe tangentially, is the idea that you could have no idea that you received any on-chain Zap at all. Only two clients support this misguided feature. That means that for all other Nostr users that are using other clients, they could have no idea that they've received on-chain Zaps to their npub.

Since most clients (thankfully) don't support on-chain Zaps, their clients have no way of notifying them that they're receiving money to their npub this way. Furthermore, people who are using on-chain Zap clients (Ditto, Amethyst), these clients can't in any way determine if the person they're sending on-chain Zaps to use or have ever used one of these clients. It is far more likely than not that they'll be sending Zaps to a person who won't be notified in any way that they received anything.

Putting aside all the horrible practices that on-chain Zaps have for privacy that you outlined, the entire argument for on-chain Zaps at the moment is convenience. But I can't think of a worse UX for a common user than to have build a payment system that will in all likelyihood result in the recipient not being notified that they received anything at all or not having any means for the sender to know who they can actually successfully send money to and who they can't.

At least if I try to send a lightning Zap to someone without a LN address, it will say that I can't. That's what proper UX should do.