Dropbox 2048(dropbox2048.site44.com) |
Dropbox 2048(dropbox2048.site44.com) |
I got attracted to this idea because it offers several security advantages. I've been working on a minimalistic javascript library (byoFS.com) that allows you to connect a Dropbox/Google Drive/etc. account and write automatically encrypted data to it. I tied for 2nd place at a recent privacy hackathon for making an encrypted chat application using only Dropbox accounts:
I actually tried to do something like this for a Comic Book reader, but the Dropbox API didn't allow for file requests to be made through JS: http://rkuykendall.com/articles/web-slinger-comic-reader/
With datastores, the changes are automatically merged according to developer-specified conflict resolution rules.
Interesting to note that the datastore isn't really deleted when one revokes Dropbox access to the app, even though it's no longer listed on the datastores page - relinking the app to Dropbox resurrects the previous data.
> Thanks for writing in. It looks like the issue here is that our content servers (dl.dropbox.com) don't currently allow arbitrary cross domain access in JavaScript. (This doesn't apply to accessing the file directly in your browser, or downloading to your server locally, which is generally what one would do with the link returned by Chooser.) […] This is something that would need to be enabled on our side, so I'll be sure to pass this on as feedback.