pull down to refresh

173 sats \ 6 replies \ @SimpleStacker 3 Jan \ on: SN release: not custodians meta

Hmm, I just converted my remaining SN balance to CCs, then zapped this post, hoping that it would zap using my connected wallet, but it zapped with CCs instead. I thought zapping would prioritize your connected wallet and use CCs as a fallback?

write
preview
51 sats \ 5 replies \ @k00b OP 3 Jan

You're right - we weren't telling the backend you could send sats.

This should be fixed now.

reply
33 sats \ 4 replies \ @SimpleStacker 3 Jan

Ok, that worked :)

reply
21 sats \ 3 replies \ @SimpleStacker 3 Jan

Sorry for yet another bug report. My home internet is down meaning my connected wallet is down too. I'm on my phone right now using my mobile network.

I tried zapping a post but got a zap failed. I thought if my wallet is down I should automatically use cowboy credits instead?

reply
21 sats \ 2 replies \ @ek 4 Jan

Mhh, weird, will look into this tmrw

reply
43 sats \ 1 reply \ @k00b OP 8 Jan

We don't disable wallets for temporary disconnect/failure yet. We'll be shipping automatic retries on failure soon, but hopefully not long after we'll add CC fallback.

reply
57 sats \ 0 replies \ @ek 8 Jan

I keep forgetting that it currently only falls back to CCs only if all receiver wallet fail but not if all the sender wallet fail.

edit: and "falls back to CCs" means here the receiver will get CCs but the sender will still pay sats

reply