the mobile connectivity one is interesting. I don’t know how clients behave there… this is something I need to test more.
don’t paste your private key.
use a signing app like Alby.
we have:
client -> relay -> nwc -> node -> nwc -> relay -> client ; and nwc -> relays -> zaps
send more zaps, we need to zapstress NWC! #zapathon
Drink and zap they said! #zapathon 
sorry, I did not want to sound harsh. please always keep the comments coming, we all try hard to build the best Nostr experience and make things better and I really really appreciate your input. You made NWC and the tools around already so much better.
We still have a lot of moving parts here. NWC problems have to be fixed in NWC. Client problems have to be fixed in the client.
If the client can not send the payment request then NWC can not do anything.
The client needs to be resilient there and also give the user feedback.
From my side zapping is still the most unreliable that I see right now. Too many zap events are rejected.
And clients (damus) needs to give users proper feedback.
With the logs I meant the NWC application logs (you run your own, right?) The app logs information about received events, payment status and responses.
There we should see what goes wrong - if NWC receives the event, if not we need to look at some other part.
exactly, NWC has responses for that reason.
which ones?
if it’s your own node then let’s have a look at the logs. (and improve logs if needed)
if it’s alby, then let me know which ones and what’s your app connection pubkey.
we put a lot of work in this and improving the lightning experience in Nostr.
that can not be… can you open an issue and share your logs?
and we need to get Damus and all clients to implement feedback on the payment.
fire and forget and hope everything works is not enough user feedback.
esp. as there are still many new moving parts (clients, relays, nwc. zap publisher,…)
and I am not happy about such general claims/FUD.
yes, that's currently a problem. Damus does not show any payment error right now. I guess in the official version this will all be done.
happy #zapathon!
sure, maybe in those cases just check if you see the payments in the web dashboard on getalby.com/user
sadly this is a bit of a protection.
a big zap problem are the zap events.
I see many payments going through but zap events being rejected from relays (for various reasons: rate limits, paid relay, etc.)
clients should give the user feedback here that the payment went through but the zap event is awaited.
do you run your own NWC or do you use the Alby one.
is there any error message you see? any feedback and details would be great to improve it.
what error do you see? there should be an error message in the logs
zapped! and the node should actually be well enough connected that there should not be any problem if you can receive from anywhere.
I'll ping you with a channel.
should I go out again in Friday? or should I stay for the zapathon? 🤔
or both?
thanks so much! it always had put a smile on my face.
now you tell me when you go partying!
