May 6, 2010

Single File Sharing

by with 14 comments

A few months ago we posted a blog listing some new features that we planned of implementing. Among them was the ability to share just a single file – a feature we had not previously included with the sharing functionality. A good many responses came in suggesting that the ability to share one file at a time would be a welcome feature and certainly be easier than having to create a folder with a single file inside (as our ShareRooms only operate at the folder level).

I am very happy to announce that we have launched our single file sharing capability. Well – to be fair – we pushed this feature a release or two ago but I wanted to make sure I mentioned it in the blog now that it is fully functional and all of the kinks are ironed out. As it so happens, the planning for single file sharing emerged from our recent iPhone development as it integrated the ability to send a link to any file stored in your SpiderOak Network from your phone.

To access this feature in the application, you will find a new menu button on the View tab labeled ‘Link’. When you highlight a file on the View tab, the ‘Link’ button will become active and pressing it will generate a URL to that particular file. You can then cut & paste that URL into an email or other message and send it to friends, family, colleagues, or clients. And similar to our ShareRooms, only that one file will be exposed as the rest of your data remains secure in our ‘Zero-Knowledge’ privacy environment. Further details are available here: release notes for 3.6.9643.

As a last mention, we are now working on our OS integration such that SpiderOak will be embedded inside the Finder/Explorer window on Mac OS X and Windows respectively. In addition to being able to see which files are among the backup set and eventually a status indication, through the contextual menu you will be able to both select additional folders/files for backup and enact the single file sharing feature such that there will be no need to interact with the SpiderOak application.

Please don’t hesitate to send further thoughts and/or ideas on features as we do greatly enjoy hearing your feedback and it is crucial in our efforts to best serve you.

Comments
  1. @ android?: We are indeed starting work on our Android development. We will send out one more release to the iPhone and then use that feature set as a platform for developing on the other mobile platforms – Android is first on the list followed by Blackberry. I apologize for not mentioning this above.

  2. The release note says the link is only good for 3 days. That won't work so well for posting on a blog.

  3. I don't understand how SpiderOak can provide a link to a file for download if the encryption key is a function of my password and not a universal key.

    "With SpiderOak, you create your password on your own computer — not on a web form received by SpiderOak servers. Once created, a strong key derivation function is used to generate encryption keys using that password, and no trace of your original password is ever uploaded to SpiderOak with your stored data.

    SpiderOak's encryption is comprehensive — even with physical access to the storage servers, SpiderOak staff cannot know even the names of your files and folders. On the server side, all that SpiderOak staff can see, are sequentially numbered containers of encrypted data."

  4. I don't like the way this link button works. If I simply click the "www" button by mistake, it sends, with zero confirmation, the name and content of the file to the web.

  5. First of all, my compliments for making such a great product. While using the single file sharing utility, I found that the version of the file which was present at the time of creating the URL is what will be shared. If some changes are made to the shared file after creating the URL, those changes will not be reflected in the file one gets from the URL. I understand that the particular version of the file is what is decrypted for a few days, I just thought that it would be helpful if you could just let the users know that when they click on the 'www' button.