pull down to refresh
0 sats \ 22 replies \ @Undisciplined 3 Aug \ parent \ on: SN release: random zap amounts, webln attached wallet meta
That's what I expected, but that's not what it's doing. My range is 21-42 and oftentimes the second zap is also in that range, rather than 210-420. One time though, the second zap was between 210 and 420.
Is there a chance it's only scaling the max value on the range?
Oh it could be. I'll take a closer look. weareallsatoshi was the mastermind.
reply
IIRC it uses a random value in the range as the base before scaling it for turbo tipping, but I could be misremembering.
Edit: I think I didn’t do anything specific for turbo tipping, I just changed how the “base zap” is calculated to use a random value in range if that’s configured, else using your default zap value. From there, it should just follow the existing turbo tipping behavior
reply
I'll keep playing around with it, but something's acting funny. I double zapped you just now and it only did 27 sats. At minimum, you should have gotten 210, if I understand how it's supposed to work. It's especially odd that the second zap was only 5 sats, since that's outside the range I set.
reply
I wonder if there’s some delay in determining the “last” zap for turbo tipping. Also yea, being outside the range altogether does not make any sense
reply
Are you also using zap undos?
reply
No, I don't like the zapping lag. It slows down my SN'ing.
reply
Fair enough! I use it because I often fat finger zap things I didn’t mean to zap lol
reply
The problem is the turbo zapping loop.
If the range is 1-100, and the first random zap is 1 sat, and the next random value chosen is 2 sats, we don’t multiply by 10 because that loop only executes if zapN-1 >= zapN.
I’ll patch in a second.
reply
This is more tricky than it seems because the range grows exponentially with the bounds. And, if the upper bound starts as more than a power of 10 greater than the lower bound, the lower bound of the next zap range LBN+1 will be exponentially less than upper bound of the current range UBN (as N grows) which is extra counterintuitive.
reply
Well now I feel bad for clearly not going through turbo zapping with enough detail for this change
reply
It's fun discovering unexpected consequences.
It's always fun when seemingly simple problems turn out to be a bit thorny.
If people want to get really wild, you could only scale the upper bound.
reply
Ah!
reply