pull down to refresh
21 sats \ 8 replies \ @nout 5 Aug 2023 \ parent \ on: Publish directly from Obsidian to Nostr with this new plugin nostr
I agree with that. The main innovations on nostr are imo:
- the portable and decentralized identity
- spraying your notes to many servers at the same time instead of one server
So from SN perspective the question is - can you take advantage of these established identities and can you create or gather the best content across those servers?
Summoning @ekzyis here as we talked about this a bit.
I am working on a blog myself now. Then we can also start eating our own doog food (features) for long content creators (with or without their own blog). I didn't think too much about nostr yet. But it makes a lot of sense. I can just cross-post to SN and nostr and then integrate SN more with nostr (or with other blogs) for this use case.
reply
can you take advantage of these established identities
Our plan to allow any post/comment on SN to be broadcast as a nostr note so long as the stacker has given us a way to sign messages with their identity.
gather the best content across those servers?
Coming from nostr into SN is harder. I haven't thunk on it enough ... If a stacker has "linked" a nostr identity to their account, their content on nostr could appear on SN as a "freebie" if it's kind and tags are appropriate or is a comment.
We definitely should allow nostr content embedding/linking like you suggested with nevent.
reply
That would be cool.I just inputted by public key in the settings - as a noob here it's not clear to me where this is used?
Yeah I like your idea of connecting to a relay and getting Kind 1 events for this pub key. Maybe then to display them in a tab next to bio? Perhaps kind 30023 long-form events are a little too big/clunky in terms of UI/UX
reply
That would be cool.I just inputted by public key in the settings - as a noob here it's not clear to me where this is used?
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")
reply
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
as a noob here it's not clear to me where this is used?
It's just used for NIP-05 right now. But we have a nostr login PR waiting to be merged that will get the ball rolling on this other stuff.
reply
Nice, You guys have done some amzing work on SN. looking forward to diving into your repo and learning more
reply