A great idea! I think tags are definitely a better way to organize most personal data than trees.<p>Also I like that they describe what data they actually change on your computer right on the homepage: &quot;TMSU does not alter your files in any way: they remain unchanged on disk, or on the network, wherever you put them. TMSU maintains its own database and you simply gain an additional view, which you can mount, based upon the tags you set up.&quot;<p>Unfortunately building on a foundation of sand (meaning not TMSU&#x27;s code, but Unix filesystems) has downsides:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;oniony&#x2F;TMSU&#x2F;wiki&#x2F;FAQ#why-does-tmsu-not-detect-file-moves-and-renames" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;oniony&#x2F;TMSU&#x2F;wiki&#x2F;FAQ#why-does-tmsu-not-de...</a><p>&quot; Why does TMSU not detect file moves and renames?<p>To detect file moves&#x2F;renames would require a daemon process watching the file system for changes and support from the file system for these events. As some file systems cannot provide these events (e.g. remote file systems) a universal solution cannot be offered. Such a function may be added later for those file systems that do provide file move&#x2F;modification events but adding support for this to TMSU is not a priority at this time.<p>The current solution is to periodically use the repair command which will detect moved&#x2F;renamed files and also update fingerprints for modified files. (The limitation of this is that files that are both moved&#x2F;renamed and modified cannot be detected.) &quot;<p>Ouch.