Alexandria is organized as the inverse of a Kindle book. Instead of having one big document, that you can interact with through linking to parts of the text, it's a bunch of smaller blocks that can be displayed or exported as a big document. And you can't take one section out of a Kindle book and embed it (along with the link to the original author profile data, such as lightning wallet information) within another book. You can only copy-paste the text or create a link. Only Nostr events can be truly embedded because only they are truly atomic.

It's similar to the difference between a hyperlink (reference to a different web page), and literally copying part of the HTML out of a web page and inserting it into a new webpage, but more absolute, since the inserted HTML stays a separate document and you still have the ability to click on that HTML and open up the originally-containing page. Or to say, "Show me all other pages that contain this page-section. Show me all similar page-sections. Show me all citations of this page section. Show me other page-sections by the author of this page..."

Reply to this note

Please Login to reply.

Discussion

And, don't forget, unlike a hyperlink to the original document, you can link to your own local copy of that document. That means that they can't rug you, by changing the document after-the-fact, as you can archive all of your references and your atomic copy is an absolutely verifiable and signed edition.

That's why I said it's like the Internet Archive, but distributed and uncensorable, and you can take it local. You can keep the content of the references important to the books you read right on your phone, and secure them. You could tell Alexandria to download the book, research paper and wiki page, and all references n layers out, and then pull that and secure the data.

So, that's why the next minor version is where you'll finally see the point of all of this data structure design. When you'll see, why we didn't just add zaps to ePUBs and PDFs.