Event JSON
{
"id": "ded27d072e9b76a6720e93d431b2d06d5ac1a9af7d36177f5e35506ef4937588",
"pubkey": "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319",
"created_at": 1719339497,
"kind": 1,
"tags": [
[
"e",
"99497547aeeec2f6b2ea181c3e6fdc083c32390b9cb743fbe2fd20253c567851",
"",
"root"
],
[
"e",
"723bee06680f725a0156aaf4815b579e6c7f6ca395c36f9d8bcef4fbdaa2b48e",
"",
"reply"
],
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24",
"",
"mention"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"",
"mention"
]
],
"content": "If you look on Project Gutenberg, they have all of the different filetypes already created and stored, probably with a database.\n\nNostr already has a database, tho (relays, an event store), where we're storing the books as events, which are the smallest, simplest building blocks of such documents. So we can always work parts-to-whole and generate any other view on the fly, including HTML. With a book, you don't need the speed and convenience of a websocket, as the text hardly changes and there's hardly any interaction. It's just you, staring at a long text, occasionally highlighting something interesting, and maybe submitting a review of the book, at the end (like we do for relays).\n\nhttps://www.gutenberg.org/ebooks/13347",
"sig": "07ac07f4a75399561f506f9789021a21a9494af8700aa6cf5f7b932eca59eae77e1d036ffb702d70a8b8bf34a530620bdbf80db6d7be273104f9068b18663954"
}