The comments here made it sound exciting, but it seems like it's proprietary, which is a no-go for me. I'll stick to plain text file notes and the occasional org-mode for now.
As an open-source alternative, Joplin could be worth a look. It's a little different in terms of features, missing a lot of the linking which is kind of key to Obsidian's appeal, so maybe it's closer to Evernote. Still, they're fundamentally the same in terms of being a note-taking app built on folders of markdown files. It's quite actively maintained and improved too.
Obsidian – A knowledge base from a local folder of plain text Markdown files
271–280 of 373 posts
Re: Obsidian – A knowledge base from a local folder of plain text Markdown files
#272I have switched to Obsidian and I use multiple vaults for multiple purposes. One is for work, one is for personal projects and notes. One for Books and Movies I watched or want to watch. And one for Zettelkasten[0]. Obsidian is extremely customizable and user-friendly. And to make things even better, which is a must for many people including me, it saves the files as .md in the local storage. You can even sync it amo…
The one thing I found weird when I looked into Zettelkasten is the focus on having relatively hard to read IDs as the primary part of the title. It could certainly help in the original use case of having to categorise and store physical paper notes, but it just feels obsolete in a world where you have digital notes, hyperlinking, and search.
Some of my notes are literally just a bunch of links to other notes because the title of the notes is descriptive enough that stringing a bunch together I can form entirely new sentences.
Re: Obsidian – A knowledge base from a local folder of plain text Markdown files
#273Re: Obsidian – A knowledge base from a local folder of plain text Markdown files
#274Earlier quoted context omitted.
It does sound very interesting, but designing the system well at the beginning looks quite important (moving categories around later on probably causes large overhead) and difficult to do without experience. I would also like to see more examples. I'm an academic, if anyone here is also one and has implemented this system I'd be very interested in seeing what your tree looks like!
Not seeing real-life examples is the most frustrating thing about JD in my opinion. Not John Noble's fault of course. In that spirit. My structure is below. - 10-19 Documents - 11 Scans - 12 Health - 13 Travel - 14 Contracts - 15 Home - 16 Visas - 17 Education - 18 Employment - 20-29 Finance - 21 Banks - 22 Bills - 23 Investments - 24 Taxes - 30-39 Hobbies - 31 Hiking - 32 Running - 33 Climbing - 34 Music - 35 Progra…
Re: Obsidian – A knowledge base from a local folder of plain text Markdown files
#275The comments here made it sound exciting, but it seems like it's proprietary, which is a no-go for me. I'll stick to plain text file notes and the occasional org-mode for now.
It's a fancy frontend for plain-text markdown files stored in a folder tree. Nothing proprietary about it.
Re: Obsidian – A knowledge base from a local folder of plain text Markdown files
#276The comments here made it sound exciting, but it seems like it's proprietary, which is a no-go for me. I'll stick to plain text file notes and the occasional org-mode for now.
You might also want to consider vim-wiki if you want the hyperlinks feature.
Re: Obsidian – A knowledge base from a local folder of plain text Markdown files
#277Earlier quoted context omitted.
I’m slightly relieved reading this. I see markdown everywhere, I can’t stand it, and I wonder why people are so crazy about it. It’s nice to know I’m not alone. Unfortunately I don’t think markdown is going anywhere. I think I see it far more than ever and there’s no sign of it slowing down.
I have been sent word documents that I’ve been totally unable to read. I’ve never been sent a markdown file that I haven’t been able to read. I’ve been sent a PDF that looks correct, but I’m not able to easily edit. I’ve never been sent a markdown file that I’ve been unable to edit. For a document format to be able to be widespread it needs to be interoperable and work on all systems. Markdown is popular because plai…
It’s an interesting thing to consider. How do we get somewhere sane between markdown and say HTML for example? What would that look like? Can you get the ease of markdown with something that would let us do more too?
Re: Obsidian – A knowledge base from a local folder of plain text Markdown files
#278The Open Source solution which serves me well for years has been TiddyWiki (1). Supports Tags and various modes of output. Each page one file or all in one, very open so recursive changes can be applied on the shell in plain files. (1) https://tiddlywiki.com/
Re: Obsidian – A knowledge base from a local folder of plain text Markdown files
#279I just downloaded deb and was a bit worried that it has 60MB, quick check on forums and it us unfortunately Electron :( Oh well, back to vim and cd.
Always fun to see these original comments in a HN thread. If you write this on Twitter you can get hundreds of retweets, hurry before someone else writes the tweet! Jokes aside, Obsidian being a Electron application is not a issue. The app starts in under 3 seconds for me, barely uses any RAM and CPU usage remains stable and low. If you want to actually contribute anything to this thread, feel free to give feedback o…
Jokes aside: if they wanted feedback on what's wrong with it they'd have made it free software.
Re: Obsidian – A knowledge base from a local folder of plain text Markdown files
#280Last I checked there was no good way to do quick capture of articles from mobile iOS to obsidian. Scenario — I come across an article on my iPhone, and I just want to dump title + URL (maybe even the text content) into obsidian. This is a must have for any note taking tool. Anyone have a good workflow for this, please share. Ideally an iOS shortcut.
My main gripe with Obsidian. That, and the fact that it costs almost $100 to have the mobile app sync with the desktop. That's insane to me, and feels vindictive. I'm all for paying for the platform. Seriously. These ventures need bottom - up support. But, syncing is a basic feature that any mobile app should have baked in. Charge for 24-hour support, something that actually requires the time of the team.