pull down to refresh
59 sats \ 23 replies \ @ek 9 Nov \ parent \ on: SN Saturday Newsletter 11/9/24 meta
True. I don't remember what I did to cause another 100k of spending. I only paid for ~crypto this week.
I should definitely switch to yearly at least, but that the rent in sats is independent of the exchange rate totally messes with my way of approaching it. I can't tell if it's better to spend my sats now or later.
Any chance we can get a do your really want to spend like a drunken sailor prompt for custom zaps of 10k or more. I fat thumbed a 10k zap twice this week when I was aiming for 1k while I was on mobile. I seem to do it at least once a week. Haha
reply
What about zap undos which trigger at 10k? They should work well now unlike in the past sometimes.
Maybe you didn’t realize zap undos have a threshold at which they trigger? I have set mine to 1k.
We definitely want a prompt for big payments like for territories though. @k00b managed to accidentally found a territory haha. Seems like it even was for more than just a month?
reply
How do I do that?
reply
I’m sure if I don’t reply for a few minutes you’ll figure it out haha
I noticed that at least once in the past but not replying wasn’t on purpose
(It’s under advanced in your zap settings)
reply
Haha thanks.
Here is another question for you. I wanted to unlink my email which I did. Which wasn't smart because I tried to link my nostr and got this error message error: nostr extension failed to sign event
And so I tried to add my email back but it says it is taken. So right now I am living on the edge with only lightning as a way to login.
reply
Regarding email: Does it still say
it is taken after you refreshed the page? Just trying to figure out what could cause this before I look deeper.Regarding nostr: which extension did you use?
reply
Alby browser extension. Thought maybe it was because I was signed out of the extension but I signed in and tried again and got the same message.
I will refresh the page and try both again.
reply
There is also a timeout of 5 seconds on the call to sign an event. That's probably way too short if you still need to sign into your extension and confirm the signature so maybe that's related. We should increase it nonetheless, I think.
edit: Mhh, but you can just try again, then it should work. I think it also shows when it failed to sign because of a timeout.
I didn't know they had a threshold either. That means I don't have to wait for smaller zaps to process before navigating away?