I'm writing this because while I've been wanting to move to 1Password for a while now thanks to stellar reviews from friends, I haven't been willing to make the leap without Google Drive sync support. Given what I've read about the numerous issues surrounding that feature, I've got an alternative suggestion that I believe might be a better fit overall.
Let us, as users and community developers, build custom/personal sync adapters that can be plugged into our accounts. Now, I'm sure this sounds crazy on its face, but hear me out:
I'd suggest specifically simply allowing the user to select this sync method and then set a URL (likely either a RESTful object or an RPC root) that would need to comply with an interface provided by 1Password. Doing so enables users to create any variety of integrations, thereby removing that particular burden from 1Password while also facilitating adoption by organizations and individuals with security concerns not currently met by existing options.
There are certainly drawbacks here - in particular, some very serious risks to users lacking technical knowledge - but I'd venture these could be mitigated using UI/UX gimmicks similar to the Android Developer Options trigger or simply some very scary warning screens/boxes.
I realize this is a stretch, but I'm hoping it might be less of a stretch than 1Password creating and maintaining the integrations themselves.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided