> I would recommend not moving around files that are under program control. Have a means to do so through the program. Thank you. That is something I thought

> I would recommend not moving around files that are under program control. Have a means to do so through the program. Thank you. That is something I thought of, too. Maybe this requires sort of an "import procedure" with a frontend. Nice idea, but the hashing question still is important to me, just to understand, if this would be enough to avoid collisions > use an extended attribute to mark the files with a UUID or equivalent such as NTFS's OBJECTID Yeah that could work... inode number and mtime may be a problem in a docker environment - size is already part of my question (more accurate: audiodata size because the file size often changes when metadata does). I'll check that again. A custom metadata tag (like TXXX:tonehubid for id3) would also work, but I don't wanna embed this information directly into the file, because if I share files with a friend and he also uses tonehub, it could end in a conflict or data loss...