Replies and all should stay in the originating client. But new conversations could spawn around the event being surfaced in kind 1 client. It does not need to be rendered in full - which is what I said in my original note.

Reply to this note

Please Login to reply.

Discussion

I’m not saying you couldn’t render it - that’s the client’s choice and how many and what kinds of nips they wish to support

I literally keep saying every other note that obviously is not the idea that clients will render all kinds, and even the idea of embedding opengraph data for rich previews as part of NIP-31 is nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcqyprqcf0xst760qet2tglytfay2e3wmvh9asdehpjztkceyh0s5r9cpvx58v (iirc)

Nostr has over 10 different "short note" kinds and chat kinds today.

And we will have 100s once Nostr becomes big enough.

It will be impossible to render them all just to offer visibility to other clients.

By now you must know that that's not what I'm suggesting.

Sure, but there are multiple ways to do that. People don't need to use kind 1s for everything to get that effect.

I am only talking about having the discovery mechanism - not about any technical implementation.