Dear developer and dear requesters,
Any feature request which adds additional tags or etc to our markdown files i think against vision of the project.
All changes to markdown files special to obsidian should be easy removable by a plugin.
Markdown files should be compatible with pandoc always.
So developers should draw a line. More feature at last will convert obsidian to rich text file editor. Obsidian should work on integration with other open source projects. Pandoc first.
Or obsidian may develop a new light markup text format. Because with embedding blocks we are on that way. We should name it. And think about new format properly.
I prefer both way. Glad with the first one which is following github format. But i know there is a huge need for a new markdown format which is natively support backlink and cititation support(an alternative footnote). Which i really want it. Of course with a new parser for mobile developers. And working with pandoc team.
Summary: you should stop or run for a marathon.
It’s an interesting dilemma. I think the plugin architecture of Obsidian is the ideal approach—it puts power in the hands of users. If you don’t want a feature that might potentially lead to compatibility issues in the future, don’t use it.
The light syntaxes Obsidian (and its future plugins!) provide are really neat, I think. The best plugins will add functionality in plaintext while still being interpretable in other apps. See, for instance, the “Expander” plugin. It adds cruft to the text, but it’s easy to tell what it is by looking at it.
For what it’s worth: the developers are encouraging app metadata to be added to YAML headers at the front of each document (another markdown semi-standard).
(Note: I added detail to the topic title for clarity.)