which part was slow? the actual time to zap? or something else
Discussion
Yeah it kinda just takes its time to animate around and complete whereas primals experience is click and done.
It's not a deal breaker I just zap a lot and it's low key annoying to wait around on each post.
Which client are you on
Amethyst
Ok I’ll tag nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z to see if he knows how to make the alby integration animate more quickly despite the obvious slower connection that’s happening there.
You don't have to wait. It's not gonna be canceled if you navigate away or do something else.
Yep but people don’t know this 😆
It makes the experience feel slower and buggier
It's probably their integration with strike. Amethyst waits until the ln transaction fully completes and the receiver sends the zap receipt, which sometimes does take seconds. Strike's API is instant because the service keeps retriyng until it finishes. They probably run the animation before they receive confirmation from lightning. 🤔
Can we run animation before completing or are you not a fan of this because of possible false “confirmation” of zap?
Ln fails a lot less these days, but yes: Completing something before you receive confirmation seems confusing. 🤔
Yeah, tough decision. On one hand, it would feel less buggy if something happens instantly as people are used to reactions being instant. On the other hand.. what you said.
Any ideas on why LN is failing? is it a failure to map a route? liquidity? Such a great concept I really wanna see it succeed.
Yep, sometimes it can be as simple as lightning nodes being too busy with other transactions. Not being centralized means that each receiver offers their own reliability levels.