pull down to refresh
0 sats \ 2 replies \ @ek 5 Aug 2023 \ parent \ on: Publish directly from Obsidian to Nostr with this new plugin nostr
I think the problem is we would need your private key to sign events. But we don't want your private key. And you also shouldn't want to give us your private key.
The public key in the settings is for NIP-05 ("nostr checkmarks")
Nostr extensions can sign events.
We may be able to safely wrap an in memory plaintext private key in a closure inside a web worker that can only sign events. Then pin encrypt it to browser storage.
I'm only 20% sure this could be made safe though. Even if it is safe it's creating bad habits for users.
reply
To be fair SN already has the "private key" to my SN account and SN wallet... so it's not ~that different. But I agree that integrating with signer extensions would be cool (e.g. Alby or Flamingo). SN could then store the presigned event and only broadcast it when it reaches some level of trust - this would be great, because that would only publish higher rating/trust posts to the wider nostr network and it would act as a great "marketing" for SN. Also consider there is a difference here between content post and a link. For content posts you may consider just always broadcasting those. For link posts, only broadcast when it reaches some trust or when it gets multiple interesting comments...
SN is the place where we have the best quality sorted content and conversations. That works well in tandem with the Nostr social type posting.
reply