Karl Bartel

I went ahead with this and
- switched my blog to djot
- plan to maintain cdjot and gemtext.lua
- marked my smu fork as unmaintained and added a short retro to the readme
- marked my md2gemini fork as unmaintained
- wrote a blog post about it

See https://www.karl.berlin/djot.html

#djot #markdown #geminiprotocol #blog

@dillo That sounds like #geminiprotocol (https://geminiprotocol.net/) in many ways. I assume you know about it, so I wonder why it is not a good candidate in your eyes. Too restrictive (no inline links)? Too different (no HTTP)?

#Markdown has horrible edge cases and despite the valiant effort of #CommonMark, the dialects seem to diverge and multiply over time. I consider switching my personal stuff to #djot where possible: https://djot.net/

Ideas:
- Stop working on #smu https://github.com/karlb/smu and maintain either https://github.com/karlb/cdjot or https://github.com/karlb/minipandoc instead
- Use https://github.com/karlb/gemtext.lua to generate #gemtext (for #geminiprotocol instead of the unmaintained https://github.com/karlb/md2gemini

Thoughts?