pull down to refresh

36 sats \ 9 replies \ @ek 16 Jul \ parent \ on: SN release: wallets v2 meta
mhhh, not sure yet why it would load forever
will keep you updated
write
preview
100 sats \ 8 replies \ @siggy47 16 Jul
Okay. Can you explain how to unsync devices now? Maybe I can unsync, load a new passphrase on mobile, then live with them unsynced for a while?
reply
36 sats \ 3 replies \ @k00b OP 16 Jul
ek removed the ability to unsync.
  1. unsynced wallets are less secure
  2. it made the code more complicated
I'm sorry siggy. I'm confident you'll need to reset and reattach sending wallets.
reply
0 sats \ 2 replies \ @siggy47 16 Jul
That's okay, but I can't reset on mobile. It keeps reloading. The send ability I have on desktop is not synced with mobile, so I can't zap on my phone. Timing sucks, since I'm going away tomorrow and won't have access to my desktop, lan for nodes, etc. Oh well. I guess I'll be cc'ing for a while.
reply
36 sats \ 1 reply \ @ek 16 Jul
I should have added code to show errors to users. I think loading your wallets is failing.
Will do that now, we should definitely be able to get your wallets to load on mobile within the next few hours
reply
100 sats \ 0 replies \ @siggy47 16 Jul
Great. Either way I'll figure something out.
reply
36 sats \ 3 replies \ @ek 16 Jul
There's no unsync anymore, all sending wallets are now always stored encrypted on the server.
The first device you opened SN with today gets to set the key, and when you use a different device, it will either already have the same key, or it won't, then it will ask you for the passphrase to derive the same key.
But I think something went wrong with detecting existing keys, so we accidentally generated new keys for some 🙈
But not sure if your wallets loading forever on mobile is related to that.
reply
0 sats \ 2 replies \ @k00b OP 16 Jul
I was weary of that new vibe coded hook that you made last minute. Is that the cause?
reply
0 sats \ 1 reply \ @ek 16 Jul
The bug is at least happening in there, but it might also have happened with what I had before
it wasn't vibe coded though 👀
reply
0 sats \ 0 replies \ @k00b OP 16 Jul
lol
it just looked pretty thoroughly cooked, like most vibe code things
reply