nips/63.md

90 lines
2.4 KiB
Markdown
Raw Normal View History

2024-11-23 19:28:52 -05:00
NIP-63
2024-11-23 17:55:35 -05:00
======
2024-11-25 15:57:56 -05:00
Build Your Own Adventure
------------------------
2024-11-23 17:55:35 -05:00
`draft` `optional`
2024-11-25 16:34:15 -05:00
This NIP introduces `kind:296` and `kind:297` as text-based notes designed to create interactive stories. These notes include options for navigating to subsequent notes, allowing readers to continue exploring the story. `Kind:296` serves as starting events for the reader, while `kind:297` represents individual scenes within the narrative.
2024-11-23 17:55:35 -05:00
2024-11-25 15:57:56 -05:00
The idea is to emulate "choose your own adventure" books, where each reader's journey through the story is unique.
2024-11-23 17:55:35 -05:00
2024-11-25 16:34:15 -05:00
Scene events MAY include an optional `title` tag and multiple `option` tags that point to the next possible scenes.
2024-11-23 17:55:35 -05:00
2024-11-25 15:57:56 -05:00
Clients SHOULD render the options in a way that allows users to select and seamlessly navigate to the corresponding posts.
2024-11-25 16:34:15 -05:00
### Example for kind:296 (Prologue)
Prologue events are entry points in the story.
They SHOULD contain `title`, `summary` and `image` to help clients render a preview of the story.
2024-11-23 17:55:35 -05:00
```jsonc
{
"kind": 296,
2024-11-23 19:25:36 -05:00
"content": "<the beginning of the story>",
2024-11-23 17:55:35 -05:00
"tags": [
2024-11-25 16:34:15 -05:00
["title", "<short title for the prologue>"],
["summary", "<summary for preview>"],
["image", "<image url for preview>"],
2024-11-23 17:55:35 -05:00
["option", "<description>", "<event_id>", "<relay_hint>"],
["option", "<description>", "<event_id>", "<relay_hint>"],
// ...
]
}
```
2024-11-25 15:57:56 -05:00
### Example for kind:297 (Scene)
2024-11-25 16:34:15 -05:00
Scenes describe a given point in a story with potential options.
2024-11-23 19:25:36 -05:00
```jsonc
{
"kind": 297,
2024-11-25 16:34:15 -05:00
"content": "<description of the scene>",
2024-11-23 19:25:36 -05:00
"tags": [
2024-11-25 16:34:15 -05:00
["title", "<short title for this scene>"],
2024-11-23 19:25:36 -05:00
["option", "<description>", "<event_id>", "<relay_hint>"],
["option", "<description>", "<event_id>", "<relay_hint>"],
// ...
]
}
```
2024-11-25 15:57:56 -05:00
The story concludes when no `option` tags are present.
2024-11-23 19:25:36 -05:00
2024-11-25 16:34:15 -05:00
The `.content` field SHOULD follow the same formatting rules as `kind:1`.
## Reading State
Kind `30296` stores the latest state of the story.
The `d` tag of the replaceable event MUST match the root event's id.
The `e` tag points to the latest scene the user has read.
```jsonc
{
"kind": 30296,
"tags": [
["d", "<root_event_id>"],
// cached to simplify preview purposes
["title", "<root_event_title>"],
["summary", "<root_event_summary>"],
["image", "<image url for preview>"],
// root with relay hint
["E", "<root_event_id>", "<relay_hint>"],
// current scene with relay hint
["e", "<event_id>", "<relay_hint>"],
// reading status
["status", "<new|reading|done>"]
]
}
```