Macworld Gives Dolly Drive 4 out 5 Mice

We get a lot of rave reviews for our service from all types of publications, but nothing means more to us than when our Apple peers stand up and take notice of what we are doing.  Macworld is the final say that is anything Apple related so we hope that if you have been waiting on the sidelines to make the switch from Mobile me, or Carbonite, or Dropbox, or Sugar Sync or Live Drive or all of these combined well now the proof is in the review.  We hope to welcome you to the Dolly Drive community soon–and you can see for yourself why we are the number 1 Cloud service in Customer Service and Customer Appreciation and why thousands of customers see the benefits of one cloud to service all their needs such as Sync+Share+Backup+Clone+Archive. We also have plenty more to provide in the weeks ahead so look for some great updates this summer…

Here is our favorite part of the Macworld review. Click on the link to see the entire article.

But the real gold is in Dolly Sync and Dolly Space. In the simplest explanation, Dolly Sync is Dropbox and Dolly Space replaces iDisk. The distinction between the two is fairly clear. Sync is confined to a folder on your Desktop. Anything dropped into the Sync folder remains on your local drive, is copied to Dolly Drive’s central servers, and is then replicated to any other computer on which you have Dolly Drive installed and the Sync option enabled. Sync combines local and central storage with replication. Remove something from the Sync folder and it’s removed everywhere. This works exactly like a Dropbox (or SugarSync, Google Drive, SkyDrive, or Box) sync folder.

Dolly Space is a Finder-mountable remote volume that requires the separate installation of OSX FUSE, which allows non-standard volume types to be mounted. (No restart is required after installing OSX FUSE.) Space is an Internet-hosted disk volume, and, unlike sync, a local copy of the file is not stored nor cached. You can move (Command-drag) files from local drives to the Space drive, and they are deleted locally and stored remotely. You can open files from the remote drive in applications, and the file is first transferred to your machine in the way that any file on a mounted volume is temporarily copied, and then opened. (iDisk could conflate sync and remote volume if you’d enabled the local caching option, although because it worked so poorly, I’m not sure if it was commonly used.)

iDolly: A free iOS app allows you to view account details and retrieve files in Dolly Sync and Dolly Space.

Both synchronized and Space-stored files can be accessed through Dolly Drive’s Web site when you’re logged into your account, as well as through the free iDolly iOS app. In the current release, the amount of storage allocated to Sync in a 50GB account is 6GB and to Space 12GB. However, Cirrus Thinking said users can request those allocations be changed, and plans to allow user-selectable allocations. (Allocations are proportionately larger with larger individual plans, and with per-machine storage allotments in a family plan.)

While Dolly Space can replace iDisk more or less entirely, Dolly Sync has some shortfalls if you use Dropbox et al. for anything but simple synchronization. In the current release, you can’t selectively sync, or choose or omit sub-folders in the sync folders for particular machines. There’s no option to share folders with other Dolly Drive users, and there’s no way to create a publicly shared item. It also lacks an interface for restoring deleted files or finding older versions. If you need any of these features, you need a full-featured sync/storage service.



facebooktwittergoogle_pluslinkedinmailby feather
This entry was posted in Dolly State. Bookmark the permalink.

One Response to Macworld Gives Dolly Drive 4 out 5 Mice

  1. Dominus says:

    / @Murk, replying here buacese my long comment is being eaten by the threaded design. :)I agree; there’s a whole very detailed forum post regarding the use of online syncing services (Dropbox, SugarSync, MobileMe and others) and package files in general. The .scriv format is really a sort of .app format; it’s a package of several folders and .rtf files all compressed together.When you update a .scriv file, there are actually dozens, if not hundreds, of files in there. You’d think online sync apps would sync only the changed files -within- the package, but apparently it doesn’t work that way; there’s metadata scattered all over the place and there’s an exponential chance of data loss. In any case, all of this, combined with the frequent auto-save features of Scrivener, means that working directly of a MobileMe or DropBox file is an -extremely- bad idea.Scriv 2.0 s lovely Sync To Folder option is very nice; I’ve used to to export my chapters and scenes and review/do minor editing on my iPhone. It only exports to .rtf or PlainText, and one of the better iPhone Apps out there for editing your Scriv documents (PlainText, which features some awesome DropBox support, right out of the box) is raw text only; meaning you can’t do any nifty bold/italics stuff with it.For more robust sync say, editing/continuing your story at work or on a different computer there’s always the new BackupTo feature which is really swell; setup a default export folder (I use something like ~/Dropbox/Written/Zip Backups/), setup whether you want to auto-backup on open/close/save or any combination of these and choose to zip each and every backup. You can pick how many you want Scrivener to keep before it starts overwriting the older ones, so you don’t end up with 300 backups, spaced ten minutes apart for every day you write.Once you get to your work computer, simply sync your DropBox, get the zip, copy it to desktop, unzip and open the .scriv file contained inside. When you’re done editing, BackupTo -> Your sync folder and you’re ready to go. Just keep in mind, this procedure is awesome for two reasons and evil for one: • Awesome 1 You get backups on the cloud at several points. I’ve setup mine to autobackup every time I close the project. So after every writing session, Scriv generates a backup which is then synced to my DropBox account. •a0Awesome 2 Backups are zipped and safe from corruption (mostly) and they’re also date stamped, for ease of finding them. It’s not too automated, which means that there are less chances of your manuscript getting overwritten and less chances of DropBox syncing on a corrupt file which overwrites your local copy.•a0Evil Sidenote When you unzip the date stamped backup, you end up with a copy of your original .scriv file. And that means, if you had a file called, for example, Gulliver’s Awesome Travels in Wherever.scriv and you backed it up as Gulliver’s Awesome Travels in, when you unzip it the file within will simply be called Gulliver’s Awesome Travels in Wherever.scriv, making it a complete duplicate copy of your original local file. Be careful there, buacese unless you check the metadata via the File->Get Info window, there’s no way to tell, once they’re unzipped, which one is the most recent one. And, even worse, if you’d setup your auto backup feature on project close and you open up the wrong local copy and close it, it’ll create a backup that is more recent than your actual real, up-to-date backup, and which will then be synced on over, date stamp and all, to your DropBox account!Ghhhh..

Leave a Reply

Your email address will not be published. Required fields are marked *