#amethyst i've never once been able to 'zap the devs' with a new release. there's always one wallet that nulls the whole thing
Discussion
zaps from within #Amethyst have been hit and miss for ~a year now. I constantly have to open Zeus and use the same Alby wallet that's connected to Amethyst and zap manually. I used to think it was a WOS thing when they bounced, but it happens with other ln addresses as well.
yep. NOSTR will always have plenty of options and work-arounds, but i'm not always going to make the extra effort
I'm using nwc from my node from amethyst for over a year and it works except if receivers custodian has problems. π
That's unfortunately not mine or other's experiences as outlined above.
Might it be the Alby nwc service struggling from time to time?
I initially thought that as well but nostr:npub15pl6u3s6dlq0hfskercdu74jd6w6ec0hzcrg434nhgj4ylvrm7fq8e8439 does not use Alby and others who have mentioned the same issue over the past year have not all been using Alby, so I'm not sure.
I do understand Kenald was talking about an Amethyst dev wallet stopping the donation from going through, but still. It's a thing.
I just reshared my comment asking others if they have the same experience. Already someone else has commented.
It has always been that amethyst zaps need to be confirmed with Zeus.
You mean, after initiating a zap, it opens up Zeus to confirm before sending? Did you set up nostr wallet connect (NWC) inside of Amethyst?
Yes. I didnt setup NWC or don't know where those settings are at least. My lightning details are saved though.
set up nwc in amathyst for 1-tap zaps
hold down the zap button
I think it sends all the other zaps and only the dev without a working wallet don't receive the zap
Got your zap. Thanks!