AeroFS/S3: Private syncing to Amazon's Cloud made easy
blog.aerofs.com
blog.aerofs.com
I just want them to support syncing existing folders rather than blessing a particular folder as the syncing one. Then we've got a nice zero-config p2p replacement for rsync.
* in development for years, * is owned by Rackspace * but also offers storage in s3, * the abstraction over s3 is open source (atleast, that was the pitch when the company was starting up -- I haven't been able to find the link to the source in the new rackspace branded site) * also offers AES encryption and de-dup, * syncs files, * has apps on windows/mac/ios/android
... so what exactly is the pitch here?
Something is bugging me though, what is AeroFS' long term viability if they don't charge for their services?
I haven't tried it yet, I still stick to the old fashioned solutions (Dropbox, Backblaze, Time Machine) as they serve me well, but sounds like something interesting with uses to explore (…maybe not the very same ones that have current services!).
Hasn't AeroFS/Regular been in beta for years now? I like this idea but perhaps some focus on the core product so the company survives would suit them better.
Additionally - how do they emulate any kind of locking? Backup to s3 is easy but multi-device sync requires substantially more coordination that needs a lock of some variety.
I hope they take some inspiration from the excellent tarsnap and use scrypt.
(PS: posting here because I refuse to register for yet another service or associate any social networking account with their site just to comment)
In this manner, the AeroFS client can (and does) access the data stored on S3 directly, but if you were to lose the machine that runs the client (but still know the password you used at setup), you can still decrypt those files by deriving the same key on a different machine.
Colin Percival's writings ([1] in particular) were very helpful in picking the appropriate set of cryptographic primitives to use. Thanks, cperciva! :D
[1] - http://www.daemonology.net/blog/2009-06-11-cryptographic-rig...
(edited to add that I work at AeroFS)
They claim that if you invite 5-10 of your friends you can get an invite, but I don't want to invite 10 people just to be a beta user of the product, it's unfair to my friends to do so unless I'm a rabid evangelist who genuinely loves the product (which I'm not, yet).
You don't have to invite the backlog of users straight away, but try to invite say 5-10% of the beta-requested users every month (I don't mind giving 3 months warning for AeroFS to get its systems ready, so AT MOST by September/November it should begin this)
Every time I search around the web for AeroFS I see claims of it being vaporware but then there also always seems to be pro-AeroFS employees astroturfing. Even here, the CEO (not a regular user) is linking to a company blog-post (a practise which I don't necessarily have any against, but it's worth noting)
AeroFS can be so much - it fills an incredible important niche (like someone said in another comment - an easy to setup P2P rsync). Local, cross-computer syncing is an important thing - many places in the developed and developing world have limited internet bandwidth but heaps of local network bandwidth. Hundreds of gigabytes to multiple terabytes of media, documents and data need to be shared and Dropbox would require immense amounts of money to do so.
It may not be as profitable as Dropbox on a per-user basis, but it doesn't need to be since we are using our own bandwidth so it doesn't cost AeroFS anything.
They had YC-funding, have like 15-ish employees last I checked. With that, Dropbox arguable is in the process of changing the internet forever. AeroFS can do the same.
I could not stop the action and was only able to recover bits and pieces of data from deleted blocks. On OSX, one might think that deleted actions would move the file to the trash but, nope, straight up deleted. These two unexpected behaviors have convinced me drop AeroFS and stop telling others about it.
There's a good chance you won't ever see this response since the thread has aged off the front page, but I figured I'd respond to it anyway, just in case.
We've actually addressed this behavior in the beta release recently by introducing local revision history. Unfortunately we haven't exposed this through the UI yet, but if this happens again in the near future I'd be happy to help you recover.