4 ms·
That’s a great constraint: local-only, read-only access, and on-demand (pull) rather than push. I’m thinking the safest/lowest-friction version would treat tho
by item007 8mo ago
That’s a great constraint: local-only, read-only access, and on-demand (pull) rather than push.
I’m thinking the safest/lowest-friction version would treat those TextEdit drafts as an ephemeral “inbox”: index them locally, never rename/move/touch the files/windows, and only generate summaries or “possible action items” when you explicitly ask. If it ever became noisy, it should default to doing less, not more.
Out of curiosity: would you want this as a one-command “summarize all open drafts” tool, or something you run against a selected subset (last 7 days / containing a keyword)? Also, which matters more to you: preserving privacy (strictly local) or preserving the exact TextEdit workflow (no export step)?
Details in my HN profile/bio if you want the longer idea.
- ebhn 8mo agoI think that for me with things like notes/writing, privacy is #1 by a lot. Preserving the textEdit workflow is nice, but I (and I imagine other users) could definitely be convinced to modify it given the right tooling and confidence in it. I know my workflow is not a productivity global maximum (and probably not even a local maximum), but everything I've seen so far does not justify itself as moving me far enough up on the productivity scale to offset the discomfort of changing habits. Fwiw I really like the way you summarized the "constraint". Maybe I'm out of the loop on what's out there, but I don't think I've come across too many tools like that aside from lower level things like git.