Is it limited to zaps via NWC, or is this lag also apparent with direct sends and invoices payments?
Try this!
lnbc10n1pnhrm20dqqnp4qv0nh8rz4lkk97vnntz2hs5dcjlhpvvc4pqskd35u4nkgch4jvh6vpp5fc8wfza4a5hd6cmm9t9849rfz4wyu8qtkz5r44rw6g0f5p6383rssp5l4z5lpd3wgyvg7tndawk6h9ddzt7h7mgjkw3kwf9vtjjqhdugp2q9qyysgqcqpcxqyz5vqu4ppfx4qwwuegasclqzmag3dvs2gg5ztl8gayxqfa3pqpp8cacf9n4067y3rfk8v0cnh3u9m8jzwf2762e3hz3ejew8a5legyte2nusph35yg7
That was fine. It took a little under 10 seconds to complete from the moment I submitted the send.
Hmm, could be how the NWC is designed. It uses the relay and passes all requests through it
Maybe I'm not patient enough? Sometimes taking over 10 seconds.
I have zapped notes and kept scrolling, when I come back I don't see it tallied.
Might be something in Amethyst. Would be nice to have an optimistic UI and notify when failure
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug would that be something you'd like to implement for zaps?
Yeah, I am thinking a lot about it. Maybe some form of zap outbox that the app keep retrying if it fails while also building a list of outgoing zaps the user can see if succeeded or failed.
I am just too afraid of retrying stuff automatically. Maybe if it fails it just marks as such and allow users to retry manually.. it's less interesting, but safer.
Yes, autoretry should be avoided, or it will open a door to hacks and abuse
I think your instincts are right on. An automatic process has the potential to go haywire. Providing an opportunity to manually retry is, I think, the smarter solution.
Maybe retry just once after a fixed amount of seconds. If it still fails, send to the zap outbox for the user to retry manually
I use Rizful for my Lightning node, connected to Amethyst via NWC, and zaps are almost instantaneous. The purple wheel of death spins around very quickly, and the zap indicator lights up almost immediately. I don't use Alby anymore, but when I did it was similarly fast. I think the only times when it lagged were due to issues on the receiving end. Are you running your own backend, or are you using Alby Cloud to host your node?
