Conversations about life & privacy in the digital age

SpiderOak to Become OSS & More: What to Expect From Us in 2014 (PART I)

To kick off the New Year, we asked our followers on Twitter what they wanted to see from us in 2014. Our CTO and Co-Founder Alan Fairless specifically addresses everyone who sent in their request, below. In Part II, our CEO Ethan Oberman will share even more about what you can expect from us throughout the year.

By the way – we just launched our new web portal design! Check it out and tell us what you think.

What you said you wanted to see from us (in no particular order):

SpiderOak improvement suggestion from Twitter

Alan: 5.1.1 was a big improvement in this regard, but there’s still some edge cases (particularly with garbage bin and many purges) or folders with hundreds of thousands of items that we’ll optimize further.

SpiderOak improvement suggestion from Twitter

Alan: SpiderOak already gives you your own encryption keys (derived from your password.)  We don’t control those! Agree we need to update our 2-factor option. Google Authenticator protocol and yubikey are top items to support.

SpiderOak improvement suggestion from Twitter

Alan: OK! We already sign our Windows installer but this is a great idea.

SpiderOak improvement suggestion from Twitter

Alan: Email support@spideroak.com anytime and we’ll make you a nice offer for these :) Otherwise we have plans to do more A/B testing on the pricing options we offer and make some changes in the coming year.

SpiderOak improvement suggestion from Twitter

Alan: Maybe…

SpiderOak improvement suggestion from Twitter

SpiderOak improvement suggestion from Twitter

Alan:  YES!!!  The need for this has never been greater, and it’s become a priority! We expect SpiderOak to become OSS in 2014. But also, every new project we’ve created in the last four years has been open source since day one, including Nimbus.io and Crypton.io.

SpiderOak improvement suggestion from Twitter

Alan: Point in time recovery! Yes! I agree this is a useful option.  Of course right now SpiderOak stores all historical versions, so all the information is there and you could do it manually, but there’s no current interface for doing this automatically.

SpiderOak improvement suggestion from Twitter SpiderOak improvement suggestion from Twitter

Alan: Underway! And our new web portal just went live yesterday.

SpiderOak improvement suggestion from Twitter

Alan: An easy fix might be to an a wildcard exclude (in preferences) for the lock files. Agree this can sometimes be annoying — deleting from syncs is a harder problem than it seems, because the app doesn’t always know exactly when the deletion happened.  It knows that the file was there at one point, and gone at another point, and knows the deletion happened sometime between those two, but not exactly when.  So sometimes getting the calculation of which files should be there is hard.  We err on the side of caution of not deleting the file if we’re not sure.

SpiderOak improvement suggestion from Twitter

Alan: Coming!

SpiderOak improvement suggestion from Twitter

SpiderOak improvement suggestion from Twitter

Alan: Coming!

SpiderOak improvement suggestion from Twitter

SpiderOak improvement suggestion from Twitter

Alan: AGREE!  Sorry, we just got absolutely slammed over the holidays, but we are hiring now and will have support caught hopefully in the next few days.  Thanks for your patience in the meantime.

Thanks to everyone who wrote in.

What about you? What do you want to see from SpiderOak this year?

SpiderOak 4.8.4 release

We are sorry for the blog update delay, dear SpiderOakians.

As of a week ago, in 4.8.4: Fix a bug causing upgrade from one version of 4.8.x series to a newer one to fail on Windows.

See all release notes here.