11–20 of 53 posts
If you want something self-hosted look into Foam[0]. You write your notes in VS Code with Markdown. Many web frameworks can then generate interactive sites from it. [0] https://foambubble.github.io/foam/
Obsidian is also self-hosted, so i don't understand your point. It's just a very fancy Markdown editor of local files.
If you want something self-hosted look into Foam[0]. You write your notes in VS Code with Markdown. Many web frameworks can then generate interactive sites from it. [0] https://foambubble.github.io/foam/
Obsidian is also self-hosted, so i don't understand your point. It's just a very fancy Markdown editor of local files.
If you want something self-hosted look into Foam[0]. You write your notes in VS Code with Markdown. Many web frameworks can then generate interactive sites from it. [0] https://foambubble.github.io/foam/
This looks very hackable too (in the good way).
I've previously been using Obsidian, and Bear before that, but always structured my notes as increasingly nested lists of bullet points.
Logseq is basically built around that abstraction, to make it very ergonomic (with each bullet point being a "block" - the smallest unit of text on which Logseq operates).
It also has querying built-in and the core is fully open source. So far very happy with it, and the new sync is great.
Besides, it's also written in ClojureScript, which makes my inner lisp nerd happy.
[0]: https://logseq.com/
https://medium.com/os-techblog/how-to-get-started-with-obsid...
Tiny suggestion - instead of .map(g => { return { key: g.key, rows: g.rows.map(r => r[1]) }}) you can write .map(g => ({ key: g.key, rows: g.rows.map(r => r[1]) }))
.map(({ key, rows }) => ({ key, rows: rows.map(r => r[1]) }))
If you like that, I also recommend taking a look at Logseq[0]. I've previously been using Obsidian, and Bear before that, but always structured my notes as increasingly nested lists of bullet points. Logseq is basically built around that abstraction, to make it very ergonomic (with each bullet point being a "block" - the smallest unit of text on which Logseq operates). It also has querying built-in and the core is fu…
I believe it has spaced repetition cards built in, too.
It took me a day to grok the "structured" lack of structure, but once I did, it has become an invaluable tool. I just throw notes on my daily journal and add tags/links (same thing) liberally. The knowledge network is practically automatic and I don't fall into the trap of prescribing a hierarchical system. A massive boon for someone with clinically significant ADHD.
The only extensions I use are for cosmetics, all functionality I need is included out of the box.
My biggest complaints are the querying language (a form of datalog) and that macros don't replace the text but are rendered dynamically instead (limiting referential utility).
Earlier quoted context omitted.
I am curious, is there any issue with just purchasing the license? I started out using Obsidian just for university related stuff but found it incredibly useful, so I ended up purchasing the license myself. While I'm not a big fan of subscription software, 50$/year is extremely reasonable, especially considering that your data isn't trapped in someone's cloud.
Currently that's 10% of a month's income, not exactly trivial. They make an excellent products, but I probably will move to a FOSS solution if I find one so I can use it for work.
Paragraph 1 in the EULA - https://obsidian.md/eula - say "You need to pay for Obsidian if and only if you use it to contribute, directly or indirectly, to revenue-generating, work-related activities in a company that has two or more people"