This is the fundamental problem with hierarchies - knowledge is multi-dimensional but folders are one-dimensional. You shouldn't have to decide if "Vanguard 2026 review" lives under /retirement or /budget or /investments. What if you could just search "retirement investment options I reviewed" and find it regardless of where it was filed - by meaning, not by path?
HN user
a_protsyuk
CTO, 15+ years in software. Winner APIWORLD 2024 Hackathon. Building ContextorAI. SF.
Chrome bookmarks + WhatsApp to self - classic combo. When you need to find a bookmark from months ago, do you actually find it or just google the thing again?
Email as inbox - do you ever actually process it, or does it just pile up with everything else?
Do you organize into folders, or just dump everything flat and rely on search?
Does the linking actually pay off when you need to find something, or do you mostly just search?
"Will probably regret it someday" - what's the thing you're most worried about losing?
LogSeq with WebDAV - nice setup. Do you use it mostly for linked notes/graph, or more as a daily journal?Zettlr is underrated. When you're compiling notes into something new - how do you find the right notes to pull together? Do you browse, search, or does the linking do the work?
Self-hosted wiki - what software? And do you access it on mobile when you're out, or is it strictly home network?
CherryTree looks interesting - hierarchical nodes. Do you split notes between Keep and CherryTree by type, or is there a different logic?
That's a solid workflow. The "cleaning" step is where most people fall off though - how long does it take you to process a batch, and how often do you actually sit down to do it?
The "low friction = actually use it" insight is real. When grep fails you - topic you don't remember the exact words for - what's the fallback?