Nostr Web Client

That's what Frostr does.

My assumption is that it's worse because it creates this requirement on all clients, while the Promenade bunker works anywhere with a generic interface. It's faster also in theory because signers are already connected directly to the coordinator.

See nostr:nevent1qqsqqq8klshrth20jlzpu9c9t0m3j3qqqudk5s7ndn3ltjyztqaghuqpr9mhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5q35amnwvaz7tmrdpex7mnfvdkx2tnyw3hkummw9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6wm5a5u

But yes, if everybody agreed and all apps included this coordinator then it would be technically better. We'll need a strong standard for it and bully everybody to support it.

reis 6mo ago

Thank you for the clarification. If it’s not worse in terms of security, I think it’s worth considering as a possible implementation.

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z what do you think?

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 6mo ago

Signer should be separate. Clients are too insecure to hold keys.

reis 6mo ago

Are you saying that the own shard in nshard should be eliminated in this example? Aside from that, does the rest make sense?

Vitor Pamplona 6mo ago

No, just the coordinator should be one of the signers.

reis 6mo ago

Understood.