Both SpiderOak One and CrossClave boast 'Syncing' behavior, but they differ in some key ways:
Syncing in SpiderOak One Backup
Think of syncing on SpiderOak One as mirrored directories.
In SpiderOak One backup, you can keep folders between devices you have on your account in parity locally. This is done by creating a sync folder and then marking a folder on each device as part of that sync. SpiderOak One then takes any files put in those synced folders and it will keep them identical across both devices. If device 'A' and device 'B' are both involved in a Sync and then the file 'pictures.png' is added to device 'A', SpiderOak One will notice that, and then take that pictures.png file, make a copy of it, and put that copy in the sync folder on device 'B'. The file is already downloaded to device 'B' as soon as it can do so, so when you go to open up pictures.png on device 'B' it occurs right away.
Syncing in CrossClave
Think of syncing on CrossClave as a shared network drive.
CrossClave is oriented in its design to ease collaboration efforts while maintaining security. This is why in CrossClave we have Teams for users to join, and spaces within those teams for organization. When you upload a file to a space within a team on CrossClave every member of the team in that space then has access to that file. Anyone with permissions can then download that file, make changes, and then upload those changes back to CrossClave. Files are not automatically downloaded locally to your devices in CrossClave like they would be with SpiderOak One Backup. Instead when you wish to work on a file, you open it from the CrossClave application itself, whereupon CrossClave queries our servers for the file, downloads it, and then allows you to open the file. After you're done working on the file you can then save it and push those changes back to our servers. Other members of that space see the changes when they open the file from within CrossClave.
If you have any further questions or concerns regarding CrossClave or its uses please don't hesitate to write in to email@example.com for support!
Article is closed for comments.