@kepano I was as transparent as possible about the LLM-character of that article - my first one, btw.

For an article that tries to help users of #Obsidian although I don't use it myself and although I already wrote an extensive separate article that should cover the basic premises, I do think the hour spent was quite adequate.

I took great care to come up with a decent prompt, checked the output to find indicators of hallucination and spent time to make the complex syntax work with my blog generating software.

The link you provided is helpful for a subset of the issues (comments and internal links only, as far as I see), thank you for that. 🙇

But other than that I would love to learn about the things the LLM got wrong because I doubt that all the rest is based on hallucination.

After all, it's a conceptual issue that relates to all tools using #Markdown in a non-trivial way.

#20260408_ObsidianMdPortability #pim

"Potential #Markdown Data Loss When You Will Move Away from #Obsidian"
https://Karl-Voit.at/2026/04/08/obsidian-md-portability

In many discussions, users of tools like Obsidian did not understand the somewhat abstract/generic warnings in my article on Markdown: https://karl-voit.at/2025/08/17/Markdown-disaster

So I asked Claude to generate a concrete list of problematic #MD syntax elements when you will leave Obsidian.

Plain text is not everything. You still need to make sure that your (meta-)data survives conversions of problematic MD flavors to target formats like other MD flavors or (in my example) HTML.

Please do report back in case of LLM hallucinations.

Edit: there do seems to be issues with the LLM result. Until manually confirmed (this is going to be time-consuming), do not trust its output literally, get the idea behind the warning and check your own data with an example export.

#publicvoit #20260408_ObsidianMdPortability