# The new Great Library
We have all heard tales of Amazon or other booksellers banning customers from their bookstores or censoring/editing purchased books. The famous [Project Gutenberg](https://www.gutenberg.org/), and similar organizations, are performing a good work, to help protect many of our precious books from this fate, but it is merely a centralized website and therefore not censorship resistant. Also, it mostly posts books in English or German.
So, we at @GitCitadel have decided to move Project Gutenberg to Nostr and house it in the most distributed way possible: on relays. Specifically, our new, public [Citadel relay](https://thecitadel.nostr1.com/) for out-of-print books (and other documents), but also on any relay, anywhere.
And, because we are a very humble group, we're naming the effort "Alexandria". And the first book to be printed on Nostr is the Bible because *obviously*.
## Why on relays?
Well, why not on relays? Relays are one of the few widely-distributed databases for documentation in existence. The relay database spans the entire globe and anyone can maintain their own relay on their personal computer or mobile phone.
That means that anyone can house *their own* books.
Which books are their own? Any books they have in their own possession. Any books someone would have to physically pry out of their cold, dead, computer.
## Notes are perfect for publishing
Once we begin generating eBooks from notes with an associated header (which will be quite easy to do, so long as they are written in markdown or similar), they will also be readable, downloadable, and storable in ePub format (see [Pandoc](https://pandoc.org/epub.html)). And it is, after all, only a matter of time until someone enterprising makes an ePaper Nostr client for calmer reading of notes, and then you can download and read them, without having to bother converting beforehand, which maintains their Nostr-navigation.
The new event kind [30040](https://wikifreedia.xyz/nkbip-01/) allows us to take any sort of note containing any sort of characters and create a type of "note collection" or "book of notes", "journal of notes", "magazine of notes". And it can be nested or embedded in other notes, creating any sort of note-combination and note-hierarchy you can think of, only limited in size by the ability of your computer to processes the relationships.
## Save the Zettels
The associated kind 30041 adds the prospect of breaking longer texts or articles up into sections or snippets (called "Zettel" in German). We can then collect or refer to particular bits of a longer text (like a chart, elegant paragraph or definition, data table), directly. Anyone can create such snippets, even of texts they didn't write, as they can add a reference to the original publication in the tags of the new event.
This means we no longer have to "copy-paste" or quote other people's works, we can simply tie them in. If we worry about them being deleted, we can fork them to create our own, digitally-linked version, and then tie that in. This means that source material can be tied to the new material, and you can trace back to the source easily (using Nostr IDs and tags, which are signed identifiers) and see who else is branching out from that source or discussing that source.
## It's gonna be HUGE!
We are making a big, beautiful library... and you are going to build it for us. Anyone, anywhere can therefore publish or republish any document they wish, with Nostr, and store it wherever they have a relay, and view it on any client willing to display it.
You will own something and be happy.
Nag Hammadi library Will be added next?
Great idea! Ideally we'll get to a point where we can write a converter that transforms epub -> nostr and reverse nostr -> epub.
Yeah, @dluvian was talking about that. It'd be a simple script, really, so long as the document had only 2 levels: header and content-articles (which most would).
The 30040 contains the ePub metadata and the list of source files for the document, then you just have to find all the json files on the relays, extract them all into one markdown file, and convert them with pandoc.
And the breakdown would just go the other way around. We're actually usually starting with one markdown file, so that's actually how we're doing it, now, using a script to split it up into 30040 header and 30041 sub-events.
Highlighter now displays Kind 30040 and Kind 30041 events.
We can commence publishing.
I’d consider allowing buying access to individual notes (as a setting by the owner) vie LN and/or Ecash.
whoa this sounds coooool :) i can imagine subscribing to my favorite authors with my rss aggregator app (like grayjay, fountain, etc) and pulling the books (text, images, embedded peertube videos etc) right off my favorite nostr relays. cool stuff!
No one in the comments has mentioned this yet, but this could be the new format for publishing and maintaining specifications and docs for Nostr software.
This could even replace the NIPs repo...
That's true. It would allow you to match a document state with a software version. 🤔
The wiki is great for an overview, but probably not right for anything very technical.