I'm writing a longer (as it seems) article on the lock-in effect of solutions like #Obsidian that are using open formats like #Markdown for storage. The file format is not the only thing that might lock you in.
I did already start with a list of arguments but also want to collect your ideas so that I don't forget a good argument.
Please, no emotions, just facts and objective arguments.
Reply here in this thread and I'll collect ideas from it. 🙇
@publicvoit I don't think, that Markdown per se is a lock-in factor. Ideally, every tool would save everything as flat text files. That would truly be open, imho.
Ages ago, I was using a simple, text file based local wiki. Things got complicated ever since.
I recently decided to start working with plain text (as in .txt) files for a few things, such as podcast notes. I'm not in the #OBTF camp (hat tip @mikegrindle) but I do find the plain, no-format text useful for notes. Now just trying to figure out the best app for my iPad for on-the-go editing and viewing.
I'm one week in to using One Big Text File #OBTF. It's a different kind of simple to the one-file-per-idea system I've been using (and haven't yet given up).
Personal experiment: Can OBTF be a worthy companion to my paper Bullet Journal? So far that's a firm yes, but one week isn't long enough to know for sure.
Looking forward to observing any friction in what's meant to be a frictionless approach.