Actually, the file links are done at startup, so there’s no need for persistent metadata or yaml for this. Part of the point of the thread is about how far you can go from this very portable setup and still consider your workflow and data portable.
I was not talking about the linking itself. I talked about the indexing of the unlinked mentions, that you can transform into links. If it’s only links you need, obsidian with all its functionality might be overkill anyway. It’s its flexibility and versatility that makes it attractive. If you don’t want or need that, a simpler approach might be more attractive.
If your workflow has anything to do with functionality of the app you use, it is mostly not portable. At least not without significant overhead for the transfer. Every app creates a load of metadata of some kind, which you lose in the transfer. Just try different flavors of text-editors like word or libreoffice. They all need some data to structure the text.
It all depends on what amount of metadata you deem useful. But in the end there is no way around it. And within Obsidian at least most of it is viewable, accessible, and transparent.
1 Like