Abstract: cloud services are simple and attractive, but what if they fail and loose your files?
          what if someone manages to get unauthorized access and stoles them?

Enter tahoe-lafs:
Most of those services just sync a local directory of your filesystem to their servers, what I'll try
to do in this experiment is to subscribe to many of them, installing each one in it's onw directory
on a local windows workstation, for example like this C:\cloud\dropbox, C:\cloud\googledrive,
C:\cloud\memopal, C:\cloud\sugarsync, C:\cloud\syncplicity, C:\cloud\ubuntuone
then I'll setup a tahoe-lafs storage node inside each of those dirs!

http://www.sickness.it/crazycloudexperiment1.png

Now I can setup a tahoe client in this machine or in another machine on the network, and just store my
files securely, encrypted, and striped across all these cloud services! :)

http://www.sickness.it/crazycloudexperiment2.png

The 3 big benefits of doing this are:
1) My files are encrypted BEFORE being stored on my local disk and BEFORE being sent to the remote cloud
   provider, so whoever stoles this local workstation or manages to hack the remote cloud servers will not get access to my files
2) I can configure a zfec factor of 3:6 so in the event that 3 cloud providers should lose my files, or close and go out of
   business, I'll still be able of recover my files from the remaining 3 cloud providers that still work, what we have here is
   effectively a RAIC (redundant array of inexpensive clouds) :)

http://www.sickness.it/crazycloudexperiment3.png

http://www.sickness.it/crazycloudexperiment4.png

3) I could instead configure a zfec factor of 5:6 so I can maximize the space that I have striping across multiple free "few Gb"
   accounts like in a RAID5 pool of disks, effectively building a cheap and inexpensive big cloud disk, and still being able to 
   recover my files in the event that one cloud provider fails.