hello folks,
so being curious here: how would teamdrive build-in encryption go with a filesystem with deduplication enabled? Being quite sceptical here about benefits of deduplicating repo that stores encrypted chunks. What happens if user stores the same file twice - does it result in the same set of bytes after encryption?
EDIT:
so i've tried it with a repo stored on lessfs deduplicated filesystem and it didn't make any sense. It was not a thorough test, but with the few files i transfered it was apparent that it is impossible to deduplicate those files that were encrypted and compressed by teamdrive.
Having some sort of deduplication built-in within the client that would kick in before the data is encrypted & compressed & sent to server (this would have to be confined to single space, so benefits would be limited - but still...) - this would be nice to have imho