321–330 of 373 posts
Earlier quoted context omitted.
It's a fancy frontend for plain-text markdown files stored in a folder tree. Nothing proprietary about it.
How do you know, unless you have the source code.
Instead I've chosen to replicate Obsidian's functionality in VSCodium. The parts that are missing (Mostly advanced search/scraping functionality) writing scripts to do. This works well because I've already modified almost every aspect for writing code. Extending it to notes should be relatively simple.
I often see people in this community being fans of note taking apps. Yet, I never really found why it's useful, maybe someone can enlighten me on that :D 1. For tech articles / knowledge databases -> tech seems to change so fast that research done 3-4 months ago is mostly useless (except for a few more high level areas) 2. For recording / knowledge database purposes -> i never seem to go back to them tho, googling (o…
I use it for two purposes: 1. Useful practical information or checklists on disease topics (I'm a physician). Sometimes they are reminders, or useful knowledge that is generally gleaned from experience / colleagues. Things that can be hard to google. 2. Notes on general business stuff - i.e. "called such and such agency and Wendy said I need to speak to other person next Monday on tel xxxx". Or dates my car needs ser…
For 2, I usually just use notepad + calendar, seems to work good since it also has notifications
Thanks :)
Earlier quoted context omitted.
Why have I never heard of this before? And I'd really like to see some example top-level hierarchies. And I'd ask, still, is is unnecessarily hierarchical? If you only have 10 categories below "20 Finance", why not just stick the (maximum) 10 categories under 20-29 in the top level? You'd still have the conceptual grouping under 2x, but without the indirection.
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!
Earlier quoted context omitted.
>In fact, the whole programmer's fetish with writing everything with a plain terminal text editor needs to die. Markdown, YAML, JSON, INI files. It's the year 2021 for christ's sake, and we're composing documents with tools designed for green CRTs! Alternative take for this same sentiment: It's the year 2021, why has nobody figured out better ways to present knowledge than simple text files?
There are better ways [1] [2], there's just no paying customers. You can express knowledge using a Semantic Web Stack[3], encode data in N-Triple/JSON-LD/RDF/XML and query it with SPARQL or Turtle. Wikidata[4] is an example of this. But (afaik) nobody's selling a product that builds and queries a large semantic knowledge base for consumers . Some industries have Semantic Web-based solutions (i'm not aware of commerci…
Earlier quoted context omitted.
>In fact, the whole programmer's fetish with writing everything with a plain terminal text editor needs to die. Markdown, YAML, JSON, INI files. It's the year 2021 for christ's sake, and we're composing documents with tools designed for green CRTs! Alternative take for this same sentiment: It's the year 2021, why has nobody figured out better ways to present knowledge than simple text files?
Define “better”. There are a plethora of alternate ways to represent knowledge. Each has its own set of trade-offs. Which do you prioritize? Ease of editing Interoperability/readability in multiple systems Expressive styling Optimized for configurations Optimized for readable text Etcetera Fill out that list, stack rank it and tell us which format is better.
I know, we don't get many of these in this field anymore. I think this means something.
I often see people in this community being fans of note taking apps. Yet, I never really found why it's useful, maybe someone can enlighten me on that :D 1. For tech articles / knowledge databases -> tech seems to change so fast that research done 3-4 months ago is mostly useless (except for a few more high level areas) 2. For recording / knowledge database purposes -> i never seem to go back to them tho, googling (o…
Apart from the transfer aspect I identify two other reasons for taking notes: The act of note taking itself may help structure and focus thoughts, regardless of intent to review or transfer the note. It may also be cathartic. It gives peace of mind to know I own the detailed information on X, just in case. Or perhaps making a pretty list about something random lets me take my mind of work for a few minutes.
But I think it’s important to understand one thing about notes and organization systems in general: do you optimize for speed of writing stuff down or do you optimize for retrieving the information?
I know that I am in the former camp. That’s why my note taking system is as follows:
I have a folder called Notes in Sublime. I create a new file, use a text snippet to insert the current ISO date (2021-10-18) give it a headline, write everything down in free-form without a structure, save it as a plain text file and be done with it.
When I want to read a note (doesn’t happen that often), I mostly remember the headline I used: Cmd+O to open that file. If nothing comes up, Sublime has good regex search capabilities.
This is an incredible time for knowledge management tools. Just a couple of years ago I was pulling my hair out trying to get a local wiki to feel like a native app, and now we have a dozen great options to choose from. I started using Obsidian when it came out last year, and it instantly clicked for me. I immediately migrated 20 years of notes to it. What differentiates Obsidian from all of the other tools in this a…
I do love Obsidian mobile though, undefeated on mobile!
Earlier quoted context omitted.
Markdown, or CommonMark?
Obsidian has it's own flavor of Markdown there is bunch of stuff other Markdowns (including CommonMark) doesn't support. > We strive for maximum capability without breaking any existing formats, therefore we use a slightly unorthodox combination of flavors of markdown. It is broadly CommonMark, with the addition of some functionality from GitHub Flavored Markdown (GFM), some latex support, and our chosen embed syntax…