Not sure if this has been discussed before; I tried looking it up in Search but didn't find this specific question get answered.
Can we adjust the cross-note linking protocol to match the way Obsidian links?
In Joplin, the internal markdown link looks like:
link to [another](../tester%20book/another.md)
In Obsidian, the internal markdown link looks like:
link to [another](another.md)
This "another.md" is even in a different folder than the note that is linking "another.md" on Obsidian. (which has me wondering if Joplin is using the more acceptable protocol)
Even if I manually delete the "../" in every internal link, Obsidian would go and create a new folder before the note.
My intention is to get to "seamlessly" switch between Joplin and Obsidian. In my opinion, Obsidian is an overall stronger editor, while Joplin is notably safer and easier to collaborate with cloud-synced notes. If I want to get me and my group of friends on a single "second brain ecosystem", it is significantly cheaper to use Joplin. Since we would all need pc-to-mobile sync anyway, using something like Google Drive / Dropbox seems redundant with an Obsidian sync plan (for each of us).
Another intention is to build on long-term security. These are my first apps and I've been reading horror stories of export hell, so I would prefer to build on the most universally-acceptable methods.
With this intention and long-term security in mind, would it be better to change Obsidian's or Joplin's linking protocol? If either is even possible..
Also, huge thanks for being such a solid community!! I'm just getting in to (finally) organizing my life together and I seriously appreciate the passion the developers here pour in to this project. You all set the bar in my book. The world needs and loves heroes like you ![]()

html, pdfs, here we go!
), I think Joplin is the best notes & "second brain" app available now. It has the strongest foundation, the most promise, and right now the most flexibility in use cases. Obsidian has plugins to make up for what it doesn't offer vanilla, but Joplin with plugins can do everything Obsidian can and more
(perhaps the open-source nature of Joplin will allow any possible gaps to be filled with future plugins - of course currently Obsidian can do some things that Joplin can't, but I'm looking at the overall potential)




)
I just posted an article about it