Playing Around with Ubuntu One

So, after I’ve received my confirmation for my Ubuntu One account on July the 19th, this evening I’ve finally found at least a bit time to play around with it and check out how good this service really works.

For my tests, I was using a vanilla Ubuntu 9.04 with latest package versions/updates installed. The installation of the PPA was pretty simple, thanks to the DEB provided on the Ubuntu One site, although I could not install the Ubuntu One GNOME-Client using the one-click feature implemented on the official Install-site. This probably could be the first thing a regular user could trap on.

So, after installing the packages manually by using a terminal and aptitude, the client appeared in Ubuntu’s “Internet”-submenu of the panel-main-menu. When a user installs Ubuntu One on a new computer and clicks the client’s icon within the menu to start the service, he will get a browser-window containing an Ubuntu One authorization-page. There, the user needs to click the “Authorize this Computer” button, so the computer will be able to sync with the Ubuntu One cloud. I took a quick look behind the scenes and as far as I’ve seen, Ubuntu One uses regular OAuth to authenticate computers to the cloud. The OAuth-token therefor will be saved within the “Passwords & Keys” thingy, that’s found somewhere in the main-menu.

However, the sync service itself creates a “Ubuntu One” folder within your home-directory, which syncs up into the cloud. Within this folder, there’s also a sym-linked-folder for Public content. The client-daemon doesn’t seem to be using some mechanism like iNotify to sync the folder contents up to the cloud, or if it does, it’s simply broken. At least on my test-machine, the client synchronized periodically – and by periodically I mean cycles with noticeable pauses in between. On one way that’s good, because not every tiny-whiny change that will be made to the folder’s contents will be pushed up to the cloud, what would literally kill your bandwidth, but on the other hand, the actual duration from one sync to another is just too big to be used with multiple devices simultaneously (e.g. an Android implementation or even another client-computer).

Talking about the simultaneousness, I don’t think that Ubuntu One is (yet) planned to be used on multiple computers simultaneous. On my test-setup I’ve created a sub-folder named “Home”, where I moved some dot-starting-folders from within my actual $HOME to and soft-linked them back to their actual location. My setup then looked something like:


devilx@vm-ubuntu:~$ ls -la | grep ^lrw*
lrwxrwxrwx 1 devilx devilx 38 2009-09-12 20:32 .evolution -> /home/devilx/Ubuntu One/Home/evolution
lrwxrwxrwx 1 devilx devilx 36 2009-09-12 20:31 .mozilla -> /home/devilx/Ubuntu One/Home/mozilla
lrwxrwxrwx 1 devilx devilx 35 2009-09-12 20:33 .purple -> /home/devilx/Ubuntu One/Home/purple
devilx@vm-ubuntu:~$


By this, I’ve pushed the preferences and information of my Firefox, my Evolution and my Pidgin into the cloud. A quick test showed me, that none of those three applications complained about their new “home” being a symlink to some directory within the cloud – and neither about any insufficient permissions that could have happened, if the cloud was set-up crappy (+1P for Ubuntu One). Still, this setup seems not that perfect for me, at the moment.

The synchronization of a modified .mozilla and especially of a modified .evolution folder seems to take for years. While I’m writing this text, the client-daemon is still synchronizing the files (it started nearly at the same time I’ve started writing this entry) and says “Updating 6 of 270 files…” – this could become a looooong night. Though, I don’t want to complain about Ubuntu One’s performance, since yet, it’s still in Beta (even if I don’t know, if Beta isn’t just an upcoming trend every company has to stick with -> e.g. Google).

I’ll try to clone this Ubuntu-installation and run them both with Ubuntu One being active – first, one after another (to see, if the applications could be synced without them complaining about parameters, that are incorrect for the secondary host they get synced to -> e.g. hostname information) and then I’ll try to run them simultaneously and hope for the best. If it should work out (what I don’t expect, just from what I’ve seen in similar projects), it would be really cool, because then, most applications could be synced this way without much hassle. I’d be really surprised, if this should be working, because then, the cloud seems to implement some kind of “merge” service, which allows you to upload data from two (or more) clients and seamlessly merge it up in the cloud together to one, consistent state.

Eh, I will see. Altogether, Ubuntu One is yet already working pretty cool, though I’m not quite sure, what a regular user should do with it, if he’s already aware of service like Dropbox or Amazon’s S3 – because at the moment, Ubuntu One unfortunately isn’t any better than those services. It just integrates more seamless into the GNOME-desktop. Hm… oh well.