Thanks, it’s really helpful to see people’s workflows for features like this; they can be so different from one another.
For the first part: what value do you get from seeing which day a tag was used?
Note that “Used” is kind of a loaded term here. For clarification, Deepdwn could only tell you which days had edits to files that currently have that tag, but not days that tag was added or removed, since that kind of history isn’t stored.
So, if you added a tag to a file today that had a lot of edits in the past, your whole calendar might light up. Similarly, if you had a file tagged for a while, and removed that tag (or the file itself), no days would light up for that tag, for that file.
If you could see all of the days that all files with “Notes For Future Me” were (ever) updated, what would you then do with that information?
I’m not against the feature, but I think there may be other ways that Deepdwn could help, and some of them might be helpful to people with different workflows as well.
is the document data specific to each machine?
It is, yes. As a core feature, all of Deepdwn’s data is local, including your global and per-document word counts. This info is store in a sqlite database next to your config file, but Deepdwn doesn’t have any facilities for merging these between multiple machines currently.