Ok, nice, it seems you agree

So given that, the only way out of this mess is not to link to files' path names anymore but to link to files via their everlasting unique identifier. Then you can move your file around and the links keep all valid and working! I believe that this (new) thinking is not only a nice but unrealistic dream. There are only 2 steps to go. The second step would be to create working links to such unique identifiers once we have them. But let's defer this second step for now (I am very busy at the moment but I will follow up later on).
Step #1, getting a unique identifier for each of the files in a file system seems solved by Microsoft's NTFS specs: read this blog post https://blogs.msdn.microsoft.com/oldnew ... 0/?p=11363 . After this lengthy introduction here comes my feature request for everything: Can you please also grab the 128 bit GUID of every file, store it in the everything database, and to add a column "GUID" to show up in everything?
After implementation of this GUID feature, everything could support a step #2a: the everything API could be extended by a new function that returns a pathname of a file for a given file GUID.
What do you think?
Best regards
echo21