I'm having bog problems with zaps last few days, it's like I can make it happen on every 2nd or 3rd try. Or the zap doesn't even pop up. Amethyst/WoS. Does anybody have a clue what's happening?
#asknostt
Discussion
Seems like you're timing out. Could be your connection or an ISP routing issue to their servers or something else. Does WoS not support nostr wallet connect (NWC)?
I understood the first sentence, my friend.👀😃
NWC fixes having to bring up your wallet for every zap. Hence, unlikely you'll time out when zapping
I'll check it out tomorrow, thanks. It's unbearable.
Maybe give nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq a try. The support NWC and I switched a few weeks ago, 0 issues so far.
#smij #zapd #amethyst & #wos
#grownostr
Same here with alby. Says relay and api outage. Weak sauce
Working now fwiw.
Nostr without zaps gives me blue balls- don’t even want to scroll cause I’ll feel bad for not zapping good stuff
Whenever that happens try my wallet... 😀
We actually specialize in zap testing, would like to look into this. So the first question is... does this happen when you try to send ANY zaps? Or just zaps to walletofsatoshi.com addresses? Or to some address and not others? We'd like to investigate.
To your note it went roght away, to nostr:nprofile1qqsxua0hju3e0j3jjhs0fjs0h3htnnreh6zm4lw4d0fhsgsv4rhwwnspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszplynk twice and didn't even start the dialogue.👀 I suspect new version of Amethyst has something to do with it, afaik nothing else changed👀
@TheGrinder and nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq use the same service to receive zaps -- rizul.com -- so if you are finding different results, that points to an issue on the SENDING side. Is your network connection intermittent?
I'm on house wifi, no issues there.🤔
And when you try it again? If you consistently find that you can zap only ONE of nostr:npub1de6l09erjl9r990q7n9ql0rwh8x8n059ht7a267n0q3qe28wua8q20q0sd and nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq , then that is a really interesting/unusual problem. What happens when you try a different Nostr client?
I can't zap this note now. I have no other nostr clients to try🤔
ok thanks. You are using Amethyst?
Yup
Thanks. Just installed a fresh version of Amethyst on my Android emulator and am having no problem zapping Rizful addresses. So our next stop is to look at your NWC service -- are you using Wallet Of Satoshi NWC? It might be a problem with their lightning node(s). A good way to test this would be to try a NWC code from a different service -- for example Alby Hub or Rizful.
This stuff is complicated to test ... you really just have to swap out parts of your setup to figure out where the problem is..
You lost me completely. Thanks for trying to help though.
Yeah, my best guess is that Wallet Of Satoshi is having issues routing certain payments. For more reliable Lightning, we'd recommend Alby Cloud or Rizful.
I don't think they support NWC at all. If I remember correctly "it's for your own safety".
outbound liquidity bottleneck?