I like Obsidian, too, having recently switched over from 9 years of OneNote (the fact that there's a tool to import my OneNote notes helped a lot).
The most important tip for getting started with Obsidian, in my mind, is to absolutely ignore all of the Obsidian "power users." I'm 99% convinced that no one actually uses zettelkasten seriously, but even if so, it's overkill for when you're just checking out the app. And, please, don't buy one of these $500 Obsidian courses. It's just not necessary.
With that said, I have started extending out my own setup, and one of the plugins that I like the most is DataView, which allows me to automatically link to other notes, or pull in tagged text, or to-do items. It has allowed me to really take daily recaps reliably for the first time ever, because, even if I have nothing to write, I at least have a repository of what I was doing for that day.
1. Obsidian imposes its own take on Markdown. For instance, why can't we disable "indent using the tab key"? It's so annoying to accidentally indent/quote text while pressing tab to do something like "accept autocomplete suggestion". Obsidian's response to users' complaints about this was not reassuring: https://forum.obsidian.md/t/option-to-disable-tab-to-indent/...
2. I had to install tens of plugins to give Obsidian the features I needed, which felt too hacky and unstable in the long term.
3. I don't want to learn a new set of keyboard shortcuts for simple things like expand/collapse the sidebars. You can customize lots of things but at that point, why not stay in your IDE (e.g., VSCode) and simply add Vim Wiki extenions?
> Obsidian's response to users' complaints about this was not reassuring
This is my main worry about choosing Obsidian for the long run. The devs seem very opinionated about a system that is meant to be customizable to each user's workflow.
Their Vim implementation does not support setting hard line breaks, making modal editing a little funky (every paragraph is just one long line and any action working on a line will work on the entire paragraph, such as "dd").
Came from Vim-Wiki (and Org-mode and some other short-lived note-taking systems) and I think the plugin hell of Vim/Emacs (or VS Code) is much worse than Obsidian. You can get by without any addons in Obsidian as it's built to be a notetaking system first, not a general text editor. You can't do the same with Vim (hence needing "Vim-Wiki" plugin).
I've also noticed that Obsidian hides text automatically inside of <div> or other HTML elements if they contain the property "markdown='1'", thereby blocking you from writing perfectly valid HTML inside of a Markdown file which was designed to be HTML-compatible.
Attributes dont need to be in the spec, if I add an attribute mycustomattr="xyz" and it changes how the document is rendered, that probably violates the HTML spec.
Yeah, I wasn’t super-thrilled with their response. OTOH, I eventually came back to using it, my (arguably justified) snit in that thread notwithstanding.
I kept trialing alternatives like VimWiki, Joplin and Logseq, but everything else is even quirkier. Org-mode is about the only thing that seemed really competitive, but since I’m not an emacs person there’s a big ramp there for me. Plus, as with most of the alternatives, that loses Markdown compatibility entirely.
Re learn new hotkeys, that’s actually not been a huge issue. Most of them simply aren’t mapped by default, which is its own pain. I did a lot of bouncing between VSCode hotkey lists and the Obsidian hotkeys UI to align shortcuts. At least they do enable you to remap most every UI action. I haven’t used the built-in vim bindings, but supposedly they also work fairly well, fwiw.
For now, Obsidian + Obsidian Tasks just does way too good a job for my work journaling for me to completely ignore. Plugins do work around most of the more questionable behavior, though it does sometimes make for an inconsistent experience.
> I don't want to learn a new set of keyboard shortcuts for simple things like expand/collapse the sidebars. You can customize lots of things but at that point, why not stay in your IDE (e.g., VSCode) and simply add Vim Wiki extenions?
This is what I used to do with Vim, but I had two problems: (1) I would often forget to `git push`, (2) I wanted to easily access notes on my phone.
Importing into Obsidian and paying for Sync made both issues go away.
Those are all good points. But to be clear for point #1, the devs never responded to this feature request. What you see in that thread is a couple of the community moderators (myself included, and all of my replies are tempered with "and I'd like it too") discussing some of the reasoning for why it likely is the way it currently is, and mostly just trying to simmer strong accusatory language. (But I totally understand the passion for our tools!)
#3 I'd likely be using my IDE (nvim) as well, except that I rely a lot on media and attachments for my work. And I just like to have dashboard/Kanban style views of things.
In retrospect, you all did a decent job of evenly responding to my spicy comments.
I will admit I assumed at least one of my direct responses was from someone involved directly with the development or design, or I probably wouldn’t have taken the confrontational stance I did. A year or so later, it does feel a bit accusatory, as you say.
All said though, I also don’t use that forum anymore (though I sometimes land on it from Google searching for plugins or tips) and I certainly don’t submit bug reports.
Obsidian’s biggest flaw remains, IMO, that there’s not a good way to report an issue with any confidence it’ll get an even chance of being addressed.
As far as I could tell, at least at the time, if the devs didn’t jump on it immediately, it’d end up automoved to a graveyard before it could ever possibly get traction. When things felt like they started getting actively argued down without considering user stances, that’s what tipped me over.
But, as I said in another comment, I eventually came back to Obsidian and renewed the commercial license so I could use it at work. It is a good system. I just think it’d be that much better with a more effective feedback loop.
Since the time of that thread, the dev team has grown, and WhiteNoise has joined the team officially in charge of bugs. I don't know the full systems they use in the background.
But I think I can definitely see where some of the burden of sorting and cleaning things up (following bug templates, or avoiding duplicate feature requests, etc.) could be abstracted away from the users, so that even if they can't be guaranteed any followup, they at least don't get the experience of being instantly shot down, just because we're trying to organize a busy forum.
For example, I really like how Linear App takes feedback. They have a button in the app, with a simple text-field prompt, "What if...". All the sorting and prioritizing is invisible to the users, but then somehow they even send a courtesy email to users after a related change has been made. That might be a function of team size vs. userbase size. No idea.
Definitely some room to improve. I'll pass this conversation on to the team, thanks.
Off the top of my head, things like "Paste URL into Text" (which VSCode Markdown supports out-of-the-box), an extension for being able to define shortcuts for heading 1, 2, etc., connecting to Zotero, converting links to Markdown before exporting PDF, exporting PDF using pandoc templates, "Zoom" in sections while hiding the other sections (it was a neat extension), etc.
As a heavy OneNote user, I was stymied by Obsidian for a long while as the mental models are different. OneNote is best thought of as an actual paper notebook, where pages can inserted, re-arranged to one’s liking, images pasted into the page, etc.. Obsidian is better thought of as a sophisticated overlay to the file system. It’s ultimately more powerful than OneNote, but does have some frustrating limitations for the OneNote/Notion/Scrivener user as not being able to manually sort notes. For now I’m using both but ultimately will switch to Obsidian as it develops (hopefully) further.
As a OneNote person for two years now, how do you deal with the added friction of linear notes in Obsidian (or any other plaintext based tool)?
In OneNote I can just dump down anything literally anywhere (because each page is an infinite canvas). It feels as easy as having a pen and random free papers. But with my notes increasing, I do want to have some way to manage this data which OneNote fails at. I can do basic text/OCR search but that's it. There is no linking etc. All note management is manual.
I usually search for an actual open source OneNote alternative (with easy jottable infinite canvases) every 6 months or so. Obsidian has added Canvases but they are definitely not a OneNote alternative at the moment.
I never understood the appeal of infinite canvas. Something about it makes me feel like I'm not in full control of my notes/documents. I like it when the information is clearly structured.
I don't use the width of the canvas, but what I do love/appreciate is the way I can click anywhere and start writing. It feels as easy as pen and paper. I can go in any direction.
It doesn't have to be infinite canvas in practice, just allow enough width and length to let you put down your cursor anywhere and start writing/pasting images or whatever you wish.
I use OneNote at work, but it's just for mostly plain text and a few images pasted here and there. However, OneNote seems to get really flaky when the Notebooks themselves become too big or have too many PDF attachments inserted.
I ultimately just didn't end up missing it as much as enjoying what I gained. I do miss how in OneNote I could keep a list of study questions next to the notes, but it's okay that I don't have it in the end, because I'm taking better notes in Obsidian.
I tried zettlekasten and found I just didn't use it enough to justify the effort involved.
Instead I just have an org-mode folder that I dump documents in. I search across them with Deft in Emacs. Sure, the links between documents can be incredibly useful to some people, but I've found I'm more chaotic than that.
I’ve written off Zettelkasten. It’s not for me. It seems to be optimized for turning notes into publications, but that’s not my own goal behind taking notes. For me, good ol’ wiki style interlinking is much more useful (and vastly easier). I use the “Map of Content” ideas to have a few quick indexes, like “Current work projects” or “orders from restaurants we like”, but that’s about the most formal organization I do.
If I had a career in writing, I might seriously consider Zettelkasten. But even then, I’d be cautious with its output. I’ve seen some results that looked like it was great for shoving words onto paper, so long as you don’t worry about the quality of the end result.
I do write for a living, and I found Zettelkasten too high friction to be worth using. Plus, as Cal Newport has argued, it solves the wrong problem. The whole pitch of ZK is that you can jump into your notes and quickly generate new ideas. But experienced writers and researchers rarely struggle to come up with ideas—rather, the real challenge is execution.
My guess is ZK is used primary as a very complex and tedious form of procrastination. Writing the book is hard, so instead, one can endlessly tweak and tune their notes and feel like progress is being made.
I have read a bit about Zettelkasten and watched a video explaining it, and to me it feels like a pretty random collection of mostly good ideas on organizing information.
Esoteric and personal are both adjectives I didn't find before to describe what Zettelkasten represents. That kind of thing that you need to visit again and again until you realize it doesn't fit to your own way of thinking
I just use "search" on my Obsidian notes, and that's enough for me. Instead of zettelkasten, I would prefer to have AI hooked to my notes, which I can query like "Find my notes about Symfony request life cycle". I don't think it would be a life changer, just a nice addition.
100% agree. The barrier to using Obsidian can seem intimidatingly high before jumping in. I tried and failed a few different systems before I just started using the daily notes as scratch pads. From there, I figured out more and more slowly over time. I’m now at a kind of system that works for me, but probably won’t work for anyone else.
Obsidian has the sama problem as Bullet Journaling does.
It's really simple and not complicated unless you want it to be, but then you watch a video about one Mega User who is really into the System and get demoralised by the amount of crap and whizbangs you see.
Why would anybody get demoralized? Does the tool get the job done or not?
Your goals are not the same as the person making a Youtube video. Nobody's going to put down "Highly Proficient with Obsidian" on their resume in hopes of it giving them an edge in the job search.
The problem is that in niche tools / gear / whatever, the message 'you must do it this way' plays to the curiosity and concerns of new users looking to get into something.
A cottage industry of people have thus sprung up around providing this content, and recommendation algorithms and search results wind up being dominated by this content.
For a new user who's just heard about something, the path is often straight to this content, which then leads some to bouncing off of it because it seems too daunting.
One thing I appreciate about Ryder Carroll‘s original explanation about bullet journals, was that it was pretty simple. It seems it was the Pinterest and other such social media folks who complicated it.
I use a semi-bullet journal method in my Obsidian notebook for work, but it’s even more basic than what Ryder Carroll outlined and I don’t care that much. Not caring is extremely helpful.
I have a similar thing, I was a semi-regular BuJoer some years ago but then I noticed that even though I did enjoy the physical action of writing stuff down - I forgot to write things down eventually. The time from idea to finding my notebook and the correct place to write something down was too long.
Now my system is geared towards minimal friction from "crap, I need to remember this" to actually storing it in Obsidian.
Currently I have a Keyboard Maestro macro that activates when I double tap the key on the left side of 1 on my keyboard, which then will activate Obsidian (or start it if needed) and brings it to the front with a QuickAdd dialog where I can write down whatever I was thinking about.
QuickAdd will then append it to an Inbox file with a timestamp. I might take a look at it later or maybe not, but at least it's written down _somewhere_ =)
I was doing something similar for a particular work function where I had to log things constantly throughout the day. However, since Obsidian simply uses text files, I used a keyboard shortcut to bring up a text prompt, which then appended the text to the correct file (which was based on the current date. This way it didn't matter if Obsidian was open or not, it would all get logged. In theory, I could have switched to a different text editor to manage the notes and kept by automation in place, I like that flexibility.
On the Mac I was using Hammerspoon for this. On Windows it would have been something like AutoHotKey.
yeah exactly. The problem is that the Mega Users are the ones who are most likely to share their system. People who say "I just use X as a notepad" aren't as likely to share.
In case it helps anyone: I use Obsidian as a notepad. I put in text in notes and sometimes put those notes in some folder if it seems to make sense. It works great and the only plugin I added for editing is a latex helper. You don't need a system or many modifications to be a happy Obsidian user.
Agreed on the power-user stuff and the courses. I use Obsidian in a simple way, but it's nice that the extensibility and the community is there.
Unlike VS Code, Obsidian is (for me) an actual example of an Electron app that feels fast. The quick open/command palette features are more responsive than similar features in native Mac apps I've tried.
As mentioned elsewhere, users frequently ask for Obsidian to be open source, but the fully transferrable file format is enough for me. I don't think most of those drive-by open-source commenters have thought about the work that goes into running an open-source project.
In other words, on some theoretical plane I'd like Obsidian to be an open-source native app, but in reality those things haven't bothered me at all. The app is as simple as I want it to be, as complex as I need it to be, and it's regularly improved in a thoughtful way.
> Unlike VS Code, Obsidian is (for me) an actual example of an Electron app that feels fast. The quick open/command palette features are more responsive than similar features in native Mac apps I've tried.
VS Code feels fast to me (on linux), but perhaps I'm just slow. I remember when VS Code came out, I was surprised at how responsive it felt, compared to Atom which felt like typing with a molasses membrane keyboard.
Actually, I realize now that I'm using Codium with lots of things disabled that made it less responsive to me (like code completion), so I'm probably an outlier.
You can paste images now as of the latest version; it was driving me crazy as well. Even in older versions you can drag an image in but that was an extra step.
> Unlike VS Code, Obsidian is (for me) an actual example of an Electron app that feels fast. The quick open/command palette features are more responsive than similar features in native Mac apps I've tried.
Dude, VSCode is a freaking IDE, running all sorts of processes in the background (at least one terminal, language servers, type checkers, linters and formatters, possibly extensions, etc.) whereas Obsidian is just a text editor.
> running all sorts of processes in the background (at least one terminal, language servers, type checkers, linters and formatters, possibly extensions, etc.)
That's a terrible excuse.
Your terminal is a separate process and should not affect how the editor itself feels. The language server exists out of process. The linters / type checkers exist out of process. (Or at least shouldn't block the main interaction/GUI thread) If those things make editing slow, either the design or the implementation is bad.
Sublime text runs the same stuff for me and works much faster than vscode. No excuses.
This is an example for context. We've got 3 cases: Obsidian (non-ide/electron/fast), vscode (ide/electron/slow-ish), sublime (ide/non-electron/fast). My point was that neither the electron not the ide part is an excuse for vscode not being responsive, because we've got counterexamples for each.
Not arguing with that. In discussions about Electron, there are often comments along the lines of "Electron apps can be fast if done right, just look at VS Code" and that just doesn't hold true for me.
> users frequently ask for Obsidian to be open source, but the fully transferrable file format is enough for me.
Completely agree. Not everything needs to be open-sourced. If I'm looking for a framework/library to build something upon, sure, I'll prioritize open-source. But -- and this may be a hot take -- for a consumer-oriented software, sometimes a great vision trumps community development.
"I'm 99% convinced that no one actually _understands_ zettelkasten"
Fixed that for you ;)
For real, anyone interested should go read the original book (How to Take Smart Notes[1]) and you learn that it's not about creating backlinks between your notes (that's just a wiki or personal knowledge base). It's about capturing ideas inspired by your reading, etc. and linking them other ideas.
Yes, building your own personal knowledge base can be very powerful, but that's something different.
That was one of the worst books I’ve ever read. I went into it expecting practical advice and found mostly vague hyperbolic promises of the magical benefits. If the hypothesis was that this note taking method produces lower effort, higher quality output, then the author either didn’t use the system or the book is evidence against its effectiveness
Thank you. Those are my thoughts exactly. The title was wrong: it should've been "Why to Take Smart Notes". I'd already decided I was interested before I ever bought the book and I wish it hadn't wasted 3/4 of pages trying to further convince me. I finished it and still had no idea how to practically implement the magical system it described.
I've also never read a book so packed with redundancy.
I kind of understood Zettelkasten only after I implemented it with slip notes in analogue form. I had read How to Take Smart Notes, zettelkasten.de, watched several videos, etc., but I only got more confused. Then I read Antinet Zettelkasten, by Scott Scheper, implemented the system on paper, and finally I understood the system. Now I could go back to Obsidian and implement my Zettelkasten in Obsidian again in a way that would be much more straightforward than what I had tried the first time (and honestly, sometimes I think of doing that because of the convenience of digital). But I enjoy writing on paper and using my fountain pens.
Zettelkasten was created for a world which didn't have computers.
People are cargo-culting it today without thinking if it still makes sense.
Zettelkasten author would not have created it today, because it makes no sense when you have much more efficient ways to index/search information with a computer.
What many people ignore from Ahrens description of Luhmann's Zettelkasten, is that it isn't an indexing system to find pre-existing knowledge/texts. It is the place where he stored his own insight, his own summaries, his own formulation of ideas he found somewhere. The book quotes Luhmann even before the table of contents with "One cannot think without writing." Strictly speaking, this is obviously not true. Metaphorically speaking it is something that many proficient authors have concluded as well. They need to write in order to make progress. And then Luhmann used this one space of notes, the Zettelkasten to work on all his publications. This allowed him to find shared ideas between different projects of him.
I've got the impression that many tried Zettelkasten as the one true note taking system just dumped stuff they found in blog articles into pages in their storage system for later retrieval. Nothing is wrong about that, but that is not Luhmanns idea of Zettelkasten.
Me too, one of my favorite pieces of software (I've been using Obsidian for a few years now). The fact that there are courses is hilarious, but anyways. I found it enjoyable to start from the absolute bare install and add notes like a regular to-do. Eventually adding up additional plugins that you need. My use case is daily software engineering notes, and I have a simple button/command that creates a new note for the day in a specific format. I love that there isn't so much extra junk that came along with the big note taking apps.
Other than that, I have vim mode and a few other things, but not much. Themed it to match the rest of my setup and terminal, it feels like an easy extension to the workflow. I have a few folders broken out for commands and constants I like to refer back to (and can search for!) Maybe a neat one-liner. Plenty of code snippets.
No affiliation, just a happy user for over a year now.
If you take kindle highlights when you read, the https://github.com/hadynz/obsidian-kindle-plugin plugin is amazing for auto generating source files with those highlights in (and other templated sections you wish to include in a review).
It started with Notion and Roam. There's a whole cottage industry of courses designed to make you "master" these tools. A lot of their users are in school or university, and given that the marketing of these tools is all about improving productivity, I can see why those courses sell.
One tip I’d have is to go easy on plugins. One can try to explores what are available, but when committing (to have it enabled and relying on it) be cautious about its implications on performance and startup time (there is a setting that can show you plugin load time at every startup.)
And as you scales the number of plugins and files, test it on multiple platforms.
P.S. I learn this the hard way that each time I open Obsidian on iPhone (14 Pro which is not slow) it will hangs indefinitely without being able to open a file. On iPadOS it is ok albeit slow to start. I suspect it is related to having too many files (including git and git sub modules) inside and relying on iCloud sync. But basically I tested out things works great on Mac without constantly checking how well it works on iPhone and then now I’m in a situation it’s difficult to roll back some of the decisions I made.
This is good advice for anything that supports plugins. Web browsers, VS Code, whatever else. Plugins can be useful, but too many is almost always a problem.
iCloud removes files from local storage randomly and downloading them again is very slow and gets stuck often.
I think that is the main reason why obsidian hangs at the start on the iPhone.
I have not yet figured out, how to keep iCloud files reliably on local storage on iOS. It seems independent of free storage and file size and is driving me mad.
Very sad that Apple does not succeed in syncing files. The same issue was there with iTools, mobile me, and now iCloud.
People using Obsidian Sync said it solves these issues (I guess by using a database rather than directly via file I/Os.)
There are other solutions via plugins too. E.g. Dropbox, Google Drive, or GitHub. There was a post earlier in HN which is a reimplementation of Obsidian Sync, but it seems their reversed engineering uncovered something not secure there and Obsidian soon made a patch breaking that. There might be workarounds to fix it, but I haven't closely follow it.
When I have the time to do the refactoring and cleaning, I will probably choose one of these alternatives (or even an alternative of Obsidian if there are better solutions for me.)
That’s what I was alluded to when I mentioned GitHub. I have that app, but I already foresee that workflow won’t work for me and my wife. So I didn’t do it that way.
But the way you say it seems to mean it no longer work?
You definitely can't just jump into zettelkasten, but it is actually used in various modified forms. I've been doing so for years and know of a number of others that do as well.
Yeah, most of the academics I know have a pile in OneNote or mountains of paper notebooks. I don't know if zk is good for research tbh, but I do think you can take some ideas from it. I personally use "bullet journaling" + a modified zk method.
I'd be curious to hear what the "highly productive" academics you know use.
OP here. Absolutely! I didn't want to go too in-depth into plugins because I wanted to emphasise Obsidian's basic features but DataView is also a plugin that I love!
I don’t use Obsidian, but I use wikilinks in markdown.
Recently I wrote a lightweight alternative to Dataview, which renders directly into the markdown itself. It’s a lightweight standalone script that embeds any references and builds those “recaps” in a more portable way.
More specifically, Obsidian shows me, at this moment, 1382 plugins available from the app itself. Some more are probably not available there. And an insanely large amount of them also seems to be already broken, abandoned or having a rather poor quality or just duplicating each other's features with a slight twist in flavor.
I guess, it's now big enough, that having some pre-selection of high quality-plugins accessible from within the app, would make sense.
It feels like WordPress. Core product is solid but minimal in features, expectation is for plugin developers to provide the rest. WordPress was FOSS though.
The most important tip for getting started with Obsidian, in my mind, is to absolutely ignore all of the Obsidian "power users." I'm 99% convinced that no one actually uses zettelkasten seriously, but even if so, it's overkill for when you're just checking out the app. And, please, don't buy one of these $500 Obsidian courses. It's just not necessary.
With that said, I have started extending out my own setup, and one of the plugins that I like the most is DataView, which allows me to automatically link to other notes, or pull in tagged text, or to-do items. It has allowed me to really take daily recaps reliably for the first time ever, because, even if I have nothing to write, I at least have a repository of what I was doing for that day.