I love Cryptomator for it’s simplicity and security and use it now over 3 years. With Cryptomator Hub im even more hyped. When I use Nextcloud or other cloud platforms I love the file versioning feature. So I hope Cryptomator can implement something like this. A simple workaround solution would be to see where the certain file is encrypted stored so I can use native tools from Nextcloud etc. This is in my opinion the better solution then an native build in Version control system. Cryptomator works great but I always get a bit stressed when I don’t know where a encrypted file is stored, when such a feature would be available it would also be possible to encrypted just one file. Also maybe for collaboration you can encrypted a citrine file with multiple keys.
I second this feature - per-file versioning inside Cryptomator vault.
I just found this workaround if we need to restore old version of a given file:
Accessing Vaults (Locate Encrypted File) — Cryptomator Documentation
Still, it would be great if this feature exists some time in the future, even if it’s challenging to define the vault format that supports this architecture.
I agree with this proposal. I am using the iPad Cryptomator app when traveling, fetching file from OneDrive (deposited there by my PC in the first place). It would be very helpful if I could request the history of a given file and have access, at least read-only, to any of the previous versions.
I would definitely like to see “file versioning” support in “Cryptomator”. But I would prefer if it would integrate with existing cloud provider version history, instead of implementing its own version control. A feature to easily identify the encrypted backend file would allow “Nextcloud” or “OneDrive” to handle restores while keeping a simple and efficient vault format.