A new behavior scheduler with Cron-style scheduling, Org-mode timestamp integration, and dynamic template variables. Automatic sync and conflict detection enhance task management and productivity.
Yes, you’re right. Many people have mentioned this to me. I’ve updated the README in the latest version, hoping it will make it easier for everyone to understand.
Org-roam uses a database, but it is not fully database-based. It only stores the mapping relationships between IDs in the database, but the content itself is not stored in the database.
However, org-supertag is database-based, storing both the content and the relationship mappings in the database.
I didn't say "another version of org-roam", I said "looks like pretty much the same idea". My words suggest nothing of what you're accusing me, but rather suggest of what I thought it was, after reading the description in the readme. I'm not alone in that, other commenters have noted that as well: "the description is pretty abstract", says one of them.
To me, a long-time Org-Roam user, "TODO" is just adding a link to an org-roam node with the same name - which, again, after reading the description of the package, kinda, sorta feels like "pretty much the same idea". If you want to avoid unwarranted criticism (which my original comment was not), I suggest perhaps try explaining it better. I'm still not sure how org-supertag can complement Org-roam and Denote workflows.
You can’t represent others’ opinions. And you’re free to use whatever you want, it’s your choice. I was just pointing out that it seemed like you hadn’t really explored org-supertag but were making comments on it, which felt a bit like trolling.
