this post was submitted on 14 Jun 2023
40 points (100.0% liked)

ObsidianMD

4102 readers
2 users here now

Unofficial Lemmy community for https://obsidian.md

founded 1 year ago
MODERATORS
 

Hi, I love Obsidian. It's part of my daily routine since a year or so, and I use it to store all my work and personal notes for the future. The main reason I use it is because of its note storage method. Instead of relying on a database, it utilizes plain text files written in Markdown, as most of you already know.

However, I have a strange feeling about it not being open source. The recent events with Reddit have only increased this discomfort. My notes are in plain Markdown, so I have the assurance that no one can forbid me from accessing them. I also take precautions by creating multiple backups, which provides additional security against virtual loss if I handle things correctly (which I do).

That being said, I would love to have alternatives like Joplin or LogSeq that adhere to the same philosophy of work as Obsidian.

Joplin is not suitable for me due to its reliance on database storage. I prefer to have total control over my notes. On the other hand, LogSeq is more focused on serving as a diary rather than a personal knowledge manager, and it does not use pure markdown, wich will be a problem in the future when (not if) I'll need to migrate out of LogSeq.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 1 year ago (1 children)

There is a loooog thread on the official forum on open source for Obsidian app: https://forum.obsidian.md/t/open-sourcing-of-obsidian/1515

IMO the best approach would be for them to make the promise, that they'll open source the code if they become unprofitable or uninterested in further developing ObsidianMD and then leave. In that case, the community has a fully open source stack.

I am aware, that Obsidian is closed source, I try to keep the number of non-compliant uses of markdown minimal. While I use quite many plugins, I am aware, that the plugins being open source removes the risk a bit.

[–] [email protected] 1 points 1 year ago (1 children)

Is there a good overview of compliant vs non-compliant markdown? Just wondering as I've been testing different editors/viewers and even basic things like diff blocks (git diff output in a ```diff block) seem to only be supported in some of them. Sorry if that's a dumb question. I'm a markdown noob.

[–] [email protected] 1 points 1 year ago (1 children)
[–] [email protected] 1 points 1 year ago

Cheers, looks like differences between implementations are to be expected. But I agree it's probably easiest to just minimise use of non-standard stuff to keep the option to switch to another tool.