How to add Google login to your app without having private keys in your app or handing them to Google: A very dry demo of its capabilities: At its core it's a bunker powered by FROST threshold signatures. Supported now in https://nostrord.com/, and https://hallway0.netlify.app, with others incoming. If you already have NIP-46 bunker support this becomes very easy to implement, there is a step-by-step flow in the README there that even an LLM can follow.

Replies (16)

@fiatjaf I'm adding support for this and will launch a coordinator. I was about to add a #cordn coordinator, so I'll just do both at once. I already support bunker, but my app is specialized in flaky Internet connections, so what I need to do is add queued signing to the queued publishing, since the signers are all online. Shouldn't be too bad.
Actually you do have to create the private key in your app if the user hasn't registered any yet. I'll look into implementing a decentralized key generation algorithm into this.
It will be good to test the flow with a different coordinator (central) if we do the thing in which a user publishes an event with their address and pointing to what central server they're using, so they can login using their own even if an app defaults to one specific central server. Are you also going to run a signer (operator), because it would be nice to have another one to rely on.
Why have a Google login at all? Seems counter productive to the freedom tech cause with all the surveillance they commit. Host your own Nextcloud. That replaces all their services except email, and there are plenty of privacy options for email.
Nostr is definitely better than Silicommie Valley social media. You do you. I'm a purist. I personally will never onboard anyone through a Big Tech login.
↑