fileregister: permanent IDs for your files that survive renames, moves, and new machines
Fileregister: Tagging and reference layer for your files, in plain text
fileregister is a plain-text tagging and reference layer that gives every file a permanent ID, stored in a JSONL index next to your notes. It survives renames, moves, and even a change of machine, with references that keep working via handles like `car-policy`. Bind files into self-documenting binders with Markdown sidecars for annotations, query everything with grep or the companion grubber tool, and rebuild the macOS metadata cache anytime. The index is the source of truth; everything else is derived.
The index is the source of truth.
- braiamp
I wanted something like this for a org, but I wanted it to be integrated with the OS/file browser. Windows 7 had some tagging, which is the flat structure you need for that, but never got the buy in from management to use it (they preferred a strict tree folder structure), so this seems cool but I want to see it integrated into something else, maybe a library?
- aerzen
It seems like this has few benefits over using a directory for the bundle and puting your files in there, no? What am i missing?
- rippeltippel
What are the use cases for this? On other words, what problem(s) does it aim to solve?