Comment on My thoughts shopping around for a wiki solution
farcaller@fstab.sh 16 hours ago
tiddlywiki has one of the most insane search engines from this list. They have a whole filters syntax that can express pretty much anything imaginable, no? I went back to TW from Obsidian because I was tired from Obsidian’s trivial search functionality.
early_riser@lemmy.world 14 hours ago
Lemme tell ya somethin about Tiddlywiki. Actually a lot of knowledge base software has this problem (I’ve specifically encountered it in Trillium, Obsidian, and TW).
You have your body where you’re austencibly storing the meat of your information. But you also have configurable metadata fields. Obsidian has its YAML headers, and TW and Trillium have separate metadata forms. All three of these have scads of methods for sorting and querying and filtering the metadata but next to nothing for the actual note. But the note is already organized data. It has headings and subheadings and text under those headings. Why can’t that be queried? I got into this on the TW forums. Everyone was basically telling me to cram all of the actual data into the header, leaving the note itself virtually empty. Obsidian has its bases feature which does the same thing. Then why not just have a bunch of YAML files? A genuine question, I’d actually love a system for sorting and querying a bunch of organized YAML files almost like a noSQL database. But Obsidian doesn’t let you do that. It has to be markdown.
I got off track there, but there it is.
farcaller@fstab.sh 7 hours ago
If your note’s type is JSON (or TW’s native dictionary), you can query it as such in filters.
My search problem is that I rely on metadata a lot. It’s natural for me to want a UI that renders machine readable metadata in a way that my brain can process and that requires rich querying capabilities.
I tried them all and, so far, TW wins for me, with orgmode being second close (I like orgmode in vim, but it had some fatal rendering flaws and I don’t feel like using emacs just for notes).