Universal formatting rules and universal programmability. Universal options for Nostr-specific formatting, as well, through a common library.
We want to do more advanced publishing, including diagrams, style sheets, tables, formulas and graphs, newspapers and magazines, scientific journals, eBooks, etc. This stuff needs to work the same on every client, and be exportable to ePub, LaTeX, and etc. in a predictable way, or it'll be a formatting shitshow.
Our 30041 events will also be Asciidoc.
It's already going to be a nightmare including long-form articles in 30040s because they will be formatted in different markdown flavors. 😬
It's straight up disingenuous of you to pretend you can't imagine fixing this with non-English-centric markdown standardization instead of asciidoc
This is a protocol
Now all of wikifreedia can be exported as manpages 😆👍
1. For Zines, you're going to need something like Hypernotes (think Interactive PDF's) anyway: nostr:naddr1qvzqqqrcvgpzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qyw8wumn8ghj7argv43kjarpv3jkctnwdaehgu339e3k7mf0qqxks7tsv4exumm5v5kku6tszfpwwk
2. Diagrams, Graphs and advanced Tables are a b*tch when it comes to displaying them properly on mobile. Creators already hate it when they don't have the guarantee of proper display on the same platform, just imagine this across XXXX different apps.
3. If you're going for universality through a common library anyway, you might as well just go for Nostr flavored MarkDown: nostr:naddr1qvzqqqr4gupzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qq9y6ctjddjx7amw9d8qntf0u3
4. I'm making things like app and music album descriptions be wikis behind the hood, so that original publishers are filling in our great encyclopedia as a byproduct 💪 . Asciidoc complicates that.
5. There are a lot of WIki- and Nostr-specific things to standardize to make them usable, so you'll be flavoring all over AsciiDoc instead. Examples: a "quick facts" section for wikis, Nostr event embeds, zettels, ...
Markdown is completely variable and implementations are incompatible at source. We could end up with 15 Nostr markdowns that can't be interchanged. They aren't plug-n-play.
So Asciidoc is mostly a fresh start + some more default features. Ok.
You guys seem to be clearly going for this.
So I'll stop arguing against and start arguing for making everything Asciidoc instead.
You cannot have Articles, Descriptions, etc be MD now. You either have a Standard or you don't.
Next, how do I write Asciidoc in Obsidian? Or anywhere else offline on desktop + mobile?
Asciidoc actually handles some basic markdown, like headers, code, and bullets.
Use Asciidoctor.
Only just got used to MD and Obsidian, damn.
Adapt or die 😂
Well if it’s any consolation, I literally did just that not 5 minutes before I read the note about asciidoc. 😆
Now I’m back in OpenBSD where Obsidian is unavailable, trying to set up a new system with asciidoc.
🤷
Same. 😂 Installed Obsidian a couple months ago.
Oddbean new post about login | logout