pull down to refresh
36 sats \ 5 replies \ @justin_shocknet 14 Oct \ on: Minor complaint meta
I had a few small UX suggestions through the CLINK integration since I switch between a lot of devices myself, but it sounds like the lack of password manager on graphene would be a blocker even to those...
Debits from a service key would solve it, and CLINK caters to that, but SN wants to avoid service-level spending ability...
Do you have a wallet installed on the phone that can grant access? A deep link authorization might solve it if so... I could conceive of logging into SN and your wallet popping up a simple accept/deny, sort of like LNURL-auth but not dependent on it.
Sorry. I don't think I made myself clear. I have no problem logging into the mobile SN wallet. The problem is that I also use my laptop, and the two wallets are linked. If one of the send connections are broken (usually when I clear my browsing history), the wallet is locked and cannot be unlocked without a passphrase. That wasn't the case until the synching of the wallets became mandatory.
Edit- wait, were you proposing a solution to that?
reply
Yea I follow, the extra passphrase is suboptimal... but do you have the same external wallet on both devices?
What I'm thinking is if your wallet is available on both it could be used directly instead of a password manager to populate the debit string on both devices without the passphrase.
reply
Right now I'm using alby hub connected to my own node on both.
reply
Iirc they have an app called "go" that connects to it as an app from devices, using that?
reply
Yes, I use that on mobile. Obviously I connect directly to SN on both through NWC on the SN dedicated app.
reply