I just wrapped up writing my own. I’ve been following a lot of projects such as Archivy and Obsidian for a while, but neither of them were what I needed. Wrote

I just wrapped up writing my own. I’ve been following a lot of projects such as Archivy and Obsidian for a while, but neither of them were what I needed. Wrote a flask app that does exactly what I need. Obsidian’s business model is really smart: creating a knowledge management system that applies to the vast majority of use cases, add room for a little modularity, and monetize it. However for those edge use cases, which on HN might be closer to a majority, it’s important to first hash out exactly what sort of features you need. Do you need to link files as well as notes in a knowledge graph? Do you need to use advanced search filters? How much data are you dealing with? Just some food for thought.