> Finally, we describe the design and implementation of an open-source version of Dropbox client (and yes, it runs on ARM too).
I wonder how long that implementation will continue to work. The official Dropbox client auto-updates (well, the Windows one does; Linux doesn't, afaik), so Dropbox can almost change the protocol whenever they like.
This lets me setup a sub-folder under my account with no more than python present on a machine and perform upload / downloads of content. Nothing processor architecture-specific about it. And with python modules like https://pypi.python.org/pypi/watchdog it's pretty trivial to trigger a re-upload of local content when it changes. The API provides counterparts for detecting changes in remote content (the /delta command).
In fact, this is how I've got Dropbox access running on my gen1 AppleTV :)
I'm more generally interested in the process of reversing of the code and protocols.
Building your own is great, but all I really want is a small package that I can drop on my ARM NAS that will keep a copy of my Dropbox data. Dropbox themselves have been dragging their feet on this for some unexplained reason.
When did Windows Dropbox start auto-updating? I've never seen it update; one of my machines had a client from like 3 years ago and another machine had a client from a year and a half ago.
I wonder how long that implementation will continue to work. The official Dropbox client auto-updates (well, the Windows one does; Linux doesn't, afaik), so Dropbox can almost change the protocol whenever they like.