So it is August 23, 2017- about 5 months after I initially asked you about odrive’s support for the Dropbox v2 API which was released to the public on November 4, 2015 which provides full metadata support for files so that things like “Date Created”, “File Ownership”, “File Permission Mode”, and so forth were preserved.
To refresh you memory, this is because the lack of full metadata support causes all sorts of problems for people who were previously relying on Dropbox to sync files while preserving this important information so that things like development environments, scripts, and so forth not only were identical across all of my workstations, they would still function as expected. Because odrive only supported v1, things like file ownership, permissions, creation dates, etc… this caused all sorts of breakage at the time for those of use who thought there was equivalent feature support between Dropbox and odrive.
This is an aside of course of the other problem of having files be uploaded and downloaded for no reason even though the files were otherwise identical because of the files having their creation dates changed. Normally it would seem the file cheksums are designed to prevent this, but this method was not fool-proof, so complete repository refreshes occurred inexplicably, which in my case caused the resync of hundreds of thousands of files.
So again, now that we are approaching two years since Dropbox publically announced the vs API - a feature set making it a cloud tool of choice for “power users” who require perfect copies of synced files and metadata - I am left to wonder if this is something that the odrive developers ever plan on implementing or if it is just going to be talked about for eternity. Full file metadata support in Dropbox seems like a high priority item since file sync accuracy is the cornerstone of any cloud sync utility. If you can’t trust the sync, you can’t use the utility. It’s as simple as that.
I have been running with odrive using Google Drive for the bulk of my files which has been fine for most stuff where file metadata is not critical, but for anything that relies on accurate file scripts, sensitive files, etc… I am forced to keep the Dropbox agent running to handle those files which is obviously suboptimal.
Fortunately for odrive, the Mac clients for the other big cloud players like Google Drive (which now uses the already-panned “Backup and Sync” app) and Amazon Cloud (whose cloud sync app for MacOS and iOS iare unquestionably the worst cloud sync agents available, not to mention the very unwelcome change in their pricing structure) are absolutely terrible, so the bar is already pretty low. But at this point, as much as I wish odrive word work properly, wishes don’t keep the lights on, and I am already looking build my own private cloud on my home network using a QNAP device. My patience is just about expired.
If you could find out if there is an updated official target date for the Dropbox v2 API, I would really appreciate it. Quite simply, if there is no support for this 1 year and 10 month old API, I am just going to have to abandon odrive, which I really would like to avoid because it offers so many other user-friendly features. But again, if you can’t rely on file integrity, you can’t use it in good conscience.