Thread by @roamhacker

1/ This looks important, interchange between TfT tools. Interchange historically fails due to competition between companies. (Lockin customers by controlling their data).

But it would be wonderful in #TfT infancy, if we can already establish interchange as a strong selling point

https://twitter.com/FISSIONcodes/status/1393223331482984450

2/ The truth is, no matter how loyal you are to one product, you will always need to at some point interact with other tools. Why? Other tools may have some feature that you need for some project? Or you might be working with people who use different tools.

3/ Regarding this, #roam is doing a good job. you can export your entire graph to EDN (full fidelity), JSON (close to full) and Markdown files. Their export is improving. Lacking:
+ Image export
+ MD doesn't export all data elements yet

4/@obsdmd by its nature is a living "export" since everything sits on the file system in markdown and physical files. However Markdown has some of its own limitations, so they add some special elements like YAMl to make data richer. It is a good solution, but not as portable.

5/ @rem_note also has good export, in fact they support a few more options: OPML, HTML and even ANKI cards.

@logseq plays well in the Markdown space as well.

6/ Challenge with interchange is these apps have unique features that don't make sense in other apps. For example, how would you export a @RoamResearch query? or @rem_note Flashcard? or a @obsdmd workspace? @logseq org mode?

Some things just can be exchanged without some loss.

7/ However, at the data & formatting level there are many commonalities. All these TfT apps support:
+ Formatting (simple MD)
+ Block references (yep all TFT apps have these)
+ Block embeds (or RN portals)
+ Backlinks
+ Tags

What other common elements do we need to exchange?