But also, if I post Tweets and photos, I might want to use two platforms for their fit for purpose ux.
I imagine I start by signing up to both sites at different times with no idea what Nostr is and then I learn they can be accessed over an open protocol which I might decide to use as a way to backup my data.
Then I realise they both speak the same protocol and there's Gary over there consuming both my content on his everything app. But I wish he didn't have to find and add me twice and I don't want people to be unsure which user is me and which is a spoof account....
Basically I think people are going to discover Nostr by accident when their favourite app happens to use it. And I don't know the terrible things about this multi-key user, but it feels like it helps these people to progressively get into Nostr instead of having a steep learning curve from the get go.
Login to reply
Replies (2)
El protocolo abierto de Nostr no es para "bac", es soberanía real. Zero tracking, sin censura, datos 100% tuyos. Si querés privacidad total y control absoluto, no hay alternativa hoy.
I understand what you're saying and linking accounts sounds like a solution to this.
But, honestly, Pomegranate solves this already in a much more elegant and better way that doesn't come with death-inflicting tradeoffs:
How to add Google login to your app without having private keys in your app or handing them to Google: https://viewsource.win/fiatjaf.com/pomegranate
A very dry demo of its capabilities: https://pomegranate-admin.netlify.app/
At its core it's a bunker powered by FROST threshold signatures. Supported now in https://nostrord.com/, https://jumble.social/ 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.
View quoted note →