nip-38: chained stories.

[kehiy]

this pr defined a new status type wich let users to share a chain of stories.

@pablof7z probably it would be useful on olas.

[kehiy]

rendered version: https://github.com/nostr-protocol/nips/blob/9649cb29dbd06f099056a7c0093a195fb002a41b/38.md

[vitorpamplona]

I am not sure what this is trying to do (how do we render these chains of stories?) but it feels like it should be a new kind/nip just for that.

[kehiy]

@vitorpamplona what do you mean by render?

this works like Instagram stories mostly.

hmm, maybe we need to define it on another nip. not sure about that.

[vitorpamplona]

what do you mean by render?

What are we supposed to do with the event? How to render it?

User Statuses from NIP-38 are usually single-line texts that is displayed just below the user's name in many clients. There is no space for anything else. So, I am not sure what this is trying to do.

Also, we do Shorts with NIP-71 video events. Is that what you are trying to do?

[kehiy]

@vitorpamplona this is a bit different from nip-71. this is a temporary event (which lives as long as the user wants) and contains media which is the main content (like in shorts) and some additional info wich will be shown on the media.

when a client fetches a list of events, it knows their order. It shows them in order one by one, which a user can extend and, for example, show their journey to a city called Nostra City.

the points are: they are temp, they can contain media (if there were no media it would be only text of content on the center), they are ordered and users can attach different info to them which are mostly interactive.

traditional social media examples: instagram stories, telegram stories, whatsapp statuses, and more.