pull down to refresh

150 sats \ 5 replies \ @SimpleStacker 19 Dec 2025 \ on: SN release: stage one of isomorphic markdown to wysiwyg editor meta
This is also a huge win for SN's developers because a reliable mapping between formats means that storing posts and comments in either format allows us to generate the other. More specifically, we can store all posts and comments in SN flavored markdown yet display them with features you only expect to see in rich text

I don't understand the footnote. Don't you already store all posts and comments in their raw markdown and display them fully rendered?

write
preview
336 sats \ 4 replies \ @k00b OP 19 Dec 2025

Yes, it's a weird point to make. The main thing is that most systems that allow rich text editing do not store the result as markdown (because it's lossy), and instead store html/json.

Also

  1. We can do the reverse. We can store the html/json and give you markdown. (We still only store markdown though.)
  2. For folks that edit entirely in WYSIWYG, we still store it as markdown.
  3. We were limited to pretty simple markdown syntax extensions before because anything crazy novel wouldn't have been accessible and therefore not worth developing. (e.g. you're the only one to use your ToC extension.)
reply
136 sats \ 1 reply \ @SimpleStacker 19 Dec 2025

Ah, yeah, that's what I figured after writing my post: your reversible markdown renderer lets people create in WYSIWYG mode, but still let you store it as markdown.

you're the only one to use your ToC extension

I think @siggy47 uses it too!

reply
36 sats \ 0 replies \ @k00b OP 19 Dec 2025

Ah nice! I wish more people to use it

reply
100 sats \ 1 reply \ @sox 19 Dec 2025

This editor now speaks AST!

reply
100 sats \ 0 replies \ @k00b OP 19 Dec 2025

translation from italian: abstract syntax tree

reply