I’m slowly developing a note-taking ecosystem that’s kind of duct-tapey but works well for me. Nothing is hosted anywhere yet, but the main thing is the ideas.
I find I want to _accrete_ information, not mutate it (in most cases), so the main organisation is chronological. But tags are important to find related information and see the chronological development of one “thing”, be it a work task, a personal hobby, etc.
But here’s the big idea: information can have an expiry date so that you can use it for years and not get buried in clutter. It’s as simple as tagging, say, exp+3w to set an expiry date three weeks after creation. There are other meta-tags too, like imp+2m means the information is “important” for two months but not after that, and it doesn’t expire.
The ideas have been percolating for years, and it’s fun to finally be working on it properly, albeit in fits and starts.
This is the area I've been eyeing for a while. I strongly agree with your "accrete, don't mutate" approach. Reduction via highlighting / summarizing is also important, but the default copy-paste and overwrite workflow of many systems means you lose so much context via destruction and mutation. Yes, restate and re-express ideas, but that should add to or shadow previous ideas, not destroy them.
I want to make something similar for myself. Starting from basically a log of everything: webpages visited and how I arrived, comments & posts written and related articles, emails, PRs, notes, transactions, messages, photos, books, podcasts, heart rate (lol), meetings and appointments, etc etc, then snapshot any relevant links with ArchiveBox. This forms the base of the "accrete" step. There'll be a lot of junk in that, so the next step is summarization: some of which will always be manual, and some sources I hope to gradually summarize in a declarative query language with a flexible output formats. In all cases the goal is to always be able to "reverse query" and see how any summarization ties back to the original source(s). E.g. maybe heart rate should be summarized into a chart that I review once a week, which itself is a new 'feed' that 'shadows' the minute-by-minute details in the usual chronological view. But if I notice a blip in the chart I can dive in and see what else I was doing at the time -- "ah, I knew reading the news was bad for my health" or whatever.
Of course this is gonna need some kind of categorization-like aspect as well, like tags or something. I've been looking into information organization methodologies, and I found PARA [0] -- which stands for Projects, Areas, Resources, Archive -- to be a pretty nice general starting point, if a bit loosely defined. In this terminology I think an audit log is the most basic "resource" for an "area", and my goal is to construct this basic audit log resource for the broadest area: "My Life" and spawn other more interesting areas out of that. I don't really like the formulation of "Archive" which I think is better conceptualized as a more general "Time" dimension. So maybe my version would be PART instead.
I really need to "just start" already.
Good luck on your note-taking journey, even "fits and starts" is much better than not started at all. :)
I find I want to _accrete_ information, not mutate it (in most cases), so the main organisation is chronological. But tags are important to find related information and see the chronological development of one “thing”, be it a work task, a personal hobby, etc.
But here’s the big idea: information can have an expiry date so that you can use it for years and not get buried in clutter. It’s as simple as tagging, say, exp+3w to set an expiry date three weeks after creation. There are other meta-tags too, like imp+2m means the information is “important” for two months but not after that, and it doesn’t expire.
The ideas have been percolating for years, and it’s fun to finally be working on it properly, albeit in fits and starts.