Thread - Nostr Hypermedia

Jumble now lets you sign up or log in with Google. It is not custodial, no server ever holds your key. Your private key is split into shards and signing uses FROST threshold signatures. Two roles cooperate: - Central server: the coordinator that verifies your Google sign-in and relays NIP-46 signing requests to the operators. It never holds a shard or your key. - Operators: independent servers that each hold one shard of your key. No single operator can sign on its own, signing needs a threshold of them. Google is only used to prove it is you, it never touches your key. If you already log in with an nsec, you can link a Google account under Settings → Account. Powered by Pomegranate: https://viewsource.win/fiatjaf.com/pomegranate/_/master

Replies (23)

Cody cody@jumble.social 2 months ago

Gives new users a simple way to get onboarded.

idsera 2 months ago

cc @novo

Bac0t b@nostr.my.id 2 months ago

video tutorial would be nice ser, still sounds complicated for dumb people like me

1 replies ↓

idsera 2 months ago

Great. No way to link Google if I'm already using @Jumble with @Amber? I didn't see this option on settings. Thanks

1 replies ↓

Cody cody@jumble.social 2 months ago

To split your key into shares and distribute them across operators, Jumble needs the key itself, so linking Google is only available for nsec users. With Amber, your key stays external and Jumble never sees it.

1 replies ↓

Cody cody@jumble.social 2 months ago

Good call, noted!

idsera 2 months ago

Cody, I logged using Google. I configured as 5of5. If I want change this settings to be 4of5, how do I do this? @fiatjaf

2 replies ↓

Cody cody@jumble.social 2 months ago

Just disconnect your account and connect it again haha.

1 replies ↓

fiatjaf _@fiatjaf.com 2 months ago

https://pomegranate-admin.netlify.app/

1 replies ↓

idsera 2 months ago

How do I know the central server?

1 replies ↓

idsera 2 months ago

@Cody When I logged with Google, this message do not disappear, but everything is working ok.

2 replies ↓

idsera 2 months ago

Ignore, now disappeared.

Cody cody@jumble.social 2 months ago

That message appears whenever the signer doesn't respond within one second. It's the same issue you see when using Amber.

Cody cody@jumble.social 2 months ago

By default, it's https://auth.njump.me/

𝕞ptf mypathtofire@iris.to 2 months ago

why would you want that though? lol

utxo the webmaster 🧑‍💻 _@utxo.one 2 months ago

I see fiatjaf convinced you to do it the complicated janky way, I will watch with great interest

2 replies ↓

Rod rb@rodbishop.nz 2 months ago

I am catching up and interested. Do you have another way?

1 replies ↓

utxo the webmaster 🧑‍💻 _@utxo.one 2 months ago

I do it by just encrypting the nsec with a pin and saving it to Google drive. This way with Fiatjaf's package has the issue that if the signers or offline, or abandon the responsibility of being a signer, users won't be able to login. Of course everyone on nostr hates how I do it

Cody cody@jumble.social 2 months ago

I couldn't think of a good reason to say no. The only thing I'm not entirely happy with is that the central server still isn't mature enough. Users can't manage permissions very granularly yet. But I'm confident fiatjaf will keep improving it.

Cody cody@jumble.social 2 months ago

People have to make it into your playground first. Then they can leave Google behind.

Ghost Mode ghost_mode@gmode7.github.io 2 months ago

Convenience kills the philosophy, or expands the reach? This debate is as old as the space itself. And it keeps coming back.

inkan dv@www.inkan.cc 2 months ago

This is interesting and it's good to have a reference implementation. It's not clear why one would want to use it.

Pickle Dan 🥒 3 weeks ago

Always doing great work! Jumble is still my favorite client.