Seems to work. Had to move the **Abstract** to ## Abstract and ### References to ## References, but the content worked.
https://github.com/ibz/bitcoin-whitepaper-markdown/blob/master/bitcoin-whitepaper.md
Includes ASCII art, which could be a good test.
Discussion
So, we've got the Bible, Aesop's Fables, and the Bitcoin Whitepaper, so far. 😀
Slowly slowly all of sacred-texts and ccel catalogue lol
Wait until you see nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn pretty web app. Then we can actually read the files, rather than just writing them.
I found that it didn't like colons in the title, and like you said, `**Abstract**...` needed to be a heading level 2. I also found that the `## Abstract ...` needs to be broken up, not just made into a heading (saw the `\n\n` in your event published). Otherwise, the article event fails to create (that was the last key to making it work).
Some checks might be needed to provide the user feedback on what might have caused a book to fail to publish.
Ah, you mean like how I moved the text before Abstract to after?
Looks like you're relay didn't write. I have a check for that and one redo.
