I just spent the last 55 minutes or so doing over 1000 sats using Nostrgram + Alby Extension, though I may have attempted several hundred more.

This is a rate of over 1000 Zaps per Hour (ZPH). Maybe a small hill will show up on on some WoS charts between 0440 and 0535 on 2023-03-10. I was zapping for 1 sat on each of these.

Some lessons learned for maximum zapping...

- Pick layouts that provide multiple columns

- Don't work from the top down. Instead, load the view, and press End a few times to go down several pages.

- Work bottom up to allow so that expansion of the interface (for showing the countdown) doesnt intefere with your next click

- If you accidentally click a post, stay in it, and try to zap all the replies

- Click to the side of dialogs you want to close (like posts threads, error messages and prompts). Don't worry about hitting the X button or OK.

- Dont bother with the autoscroll option. Because its constantly moving it makes it tricky to land on the icon to zap.

- Because there were not enough posts in my feed I had to go through many views and even zap several of them multiple times.

Here are some errors I got.

1. Zap failed. Reason given: Unable to access the well-known URL of this provider. LN address copied to the clipboard instead.

2. Zap failed. Reason given: Unable to access payment URL of this provider. LN address copied to the clipboard instead

3. Zap failed. Reason given: Amount is out of bounds

Of the errors, the first two were fairly common. About once every 10-20 zaps. The last one I dont know what it means. Perhaps a request to zap was met with an invoice that didn't equal my amount?

#[0] Maybe an option could be added to Nostrgram to have these errors display as less intrusive toast messages instead of dialogs?

In the console, I would also see this alot: WebLN call alrady executing but didn't bother diagnosing what was causing that. Seemed to happen more often if I had more zaps queued up.

Regarding the WebLN call already executing, that sounds like Alby won't execute more than one Zap simultaneously. That is, if one hasn't been completed yet it won't do another. I'll see if I can code a check for that and have it retry should it happen.

Reply to this note

Please Login to reply.

Discussion

No replies yet.