Thread

Replies (64)

↩ replying to npub1kfkd...ycwx
Testing zaps on this note… we made seven attempts to⚡zap this note, at bitcore@lawallet.ar, over a period of 1 day. All seven attempts were successful. You should check on your end to be sure you received these. Average zap time was 3523ms (3.5 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce inbound zap latency.
↩ replying to conejo
Testing zaps on this note… we made seven attempts to⚡zap this note, at conejo@lawallet.ar, over a period of 1 day. All seven attempts were successful. You should check on your end to be sure you received these. Average zap time was 4950ms (5.0 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce inbound zap latency.
Hey @Yadunandan Batchu I think you are going to send zaps after 24 hours... Bulkzapadd needs to wait for upto 24 hours, then select all the users and send sats via zaps People won't feel enthusiastic because they loose interest in waiting 24 hours..! I feel users will be more engaged if the zaps are immediate... But sending zaps manually after every zap is almost impossible task 😅 Can u try something like automating and sending the zaps immediately after the reposts ( ofcourse excluding the duplicates) Let me know if I can freelance for this task for a solid amount of zaps 😎..!