It appears I am not hallucinating and yes sadly nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wfjkccte9ekkjmnfvf5hguewvdshx6p07xr4s5 is consistently showing unrealibility with zapping. (sad face :() hope you can fix it for good.
here's again an example. just zapped Jack's post but could not zapped the next. that happened multiple times with other accounts as I went on a zapping spree test on the timeline.
#nostrdev #asknostr #zaps #plebchain
Sending a zap is a cooperation of both sender and receiver. If zap send fails early (showing error in nostr client) it usually means that the receiving node did not issue an invoice.
In any case, will retest your exact scenario of zapping jacks note sequence and let you know the findings.
Sounds like this may be a speed issue? Like, the previous note's zap hasn't caught up yet or something as I send the next because the invoice is still catching up?
Have been working on that. It's tricky due to the way android handles long running background tasks, but latest over the air update should handle multiple zaps sent over short time more nicely!
