pull down to refresh
@ek
4,919,264 sats stacked
stacking since: #57444longest cowboy streak: 233 verified stacker.news contributornpub16x07c...2j2s96s89dekzyis
Does this section in the FAQ answer your question?
During triage, someone who screams could be in a better medical condition than someone who isn’t, as screaming tells you they are conscious and breathing, which further means their life isn’t immediately in danger.
Very similar to #898691 but I like that you included a reason why you didn’t use the crew entrance (assuming it exists).
However, I think it’s better to only have an excuse in mind but don’t immediately tell the security, only when asked. If you tell them immediately, it can look like a guy who is guilty and immediately tells the police in detail when they arrive what he allegedly didn’t do.
Yes, music festival!
Not bad, I can see this work to get in, especially if you’re a fast runner. I didn’t mention this in the post, but how do you get out without consequences though? And are there no security patrols that would immediately see you don’t have a wrist band? Essentially, what is your exit strategy?
I also assume you choose specifically hat and jumper because it’s easy to get rid of a hat and update your description and with a jumper, you only have to undress since you can wear other clothes below.
Sorry for the late reply, I missed this.
but it just gets stuck atWaiting for authorization
and I see nothing on desktop browser where I hitConnect
after signing up on nsec.app.
Mhhh, when you see
Waiting for authorization
, it should have prompted you in nsec.app.Login via remote nostr signer is a 3-step process:
- Create new app connection in remote signer (nsec.app) and copy bunker url
- Paste bunker url into SN
- Confirm login in remote signer
Is this what you tried but the confirmation prompt didn't appear in the remote signer?
Will test myself to make sure this still works.
We wait one minute between each attempt and after one hour or two retries, whatever comes first, we stop retrying. I think that answers your actual question since how long an attempt takes depends on a lot of factors mostly outside our control.
Payments will be retried in the background two times so I suspect you zapped something again because you thought it failed but then the retry was successful. If a failed payment doesn’t show up in notifications, it will still get retried so I recommend only retrying from your notifications, not based on what you see in satistics.
Thanks for mentioning, that’s an UX issue. It’s not shown anywhere that we retry payments.