As I’ve written, moving the application-folders into the cloud seems to be working pretty good on one client. Now I’ve tested, how it is when using two clients and pulled the information contained in the cloud (from client A) down to client B. Each of the three applications worked in general, Pidgin started with the account configured on client A, Evolution started with the Inbox configure in client A but asked me for the password to access the mail-server (what’s clear, because I did not synchronize the key-rings) and Firefox displayed with the preferences configured, but prepended a message box that said:

Could not initialize the application’s security component. The most likely cause is problems with files in your application’s profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security features.

This confused me a bit, especially since the actual browser ran without any more problems. However, I’ve been to lazy to track down this permission problem.

After I’ve checked, if “one-after-another” synchronization worked, I tried out the simultaneous usage of both machines, while being connected and synced with the cloud on each of them. As I’ve expected, I ran into some problems: Suddenly, some more folder (thumbnail) appeared within the client B’s Ubuntu One folder, that contained his app-information. The folders remained until the actual Home folder finished receiving the data from within the cloud, then they just disappeared. I don’t know, if those have been merged or just deleted – it just worked afterwards.

Ubuntu One seems to be using “semaphores”, in a similar way token-ring was using: At first, client A is allowed to sync his data with the cloud. When this is finished, client B is allowed to sync. Then, it’s client A’s turn again – and so on. Theoretically, this is good. But in practice, Ubuntu One unfortunately seems to overwrite locale changes when pulling data down from the cloud. In comparison: MobileMe asks the user and merges the data, as good as possible.

In the end, simultaneous usage was unable to sync both machines in a way, so that data was kept consistent. Either one machine lost information, or the other. Especially when adding a new Pidgin account on client B, waiting for the sync, closing Pidgin on client A (which then seems to save a final account-info) and waiting for the sync there, you will be surprised your account not to be available when re-launching Pidgin on client A.

Of course, synchronization always is a tricky feature, but I guess, Ubuntu One lacks of an SVN-like back-end, that keeps track of all changes and makes merging possible. I’m really interested in how Ubuntu One will continue to evolve and I’ll try to keep tack of its development status. This could really kick ass someday, as soon as everything works seamless and simultaneous.

WebKit Development Tools

In the past few weeks, I was involved into heavy JavaScript web-development at work and had to work with tools that allow me to debug dynamic web-content in an effortless way. Most people would now say “Use Firefox with FireBug addition!” and I would even agree with them, if I would be using some Windows operating-system instead of my lovely Mac. Everyone who has ever used Firefox on a Linux or a Mac OS X will know, that it’s a pain in the arse. Due to the way Mozilla-developers have taken to make Firefox available on multiple platforms, it lacks of any speed and integration within most implementations.

So what to do on a Mac, where Firefox trying to render a full-blown AJAX-site needs more space and CPU-power than a VMware or Parallels instance of Windows XP, running the IE? Most people don’t really know, that the Mac’s integrated browser already provides a very good toolset for web-development which just got even better with the version 4 (yet, still Beta) of Safari.

The toolset is hidden, on a regular OS X, but it can be unlocked pretty easy. The only thing you gotta do, is quit your Safari, open a Terminal and enter this command:

defaults write com.apple.Safari WebKitDeveloperExtras -bool true


It should quit without any output. After that, you can quit the Terminal and re-start Safari. You might not see any difference to Safari’s appearance before spawning the command, but now just try to do a right-click / command-click within a web-site. You will see, that your popup-menu has just been extended by one new item at its bottom, called “Inspect Element“. By clicking this entrie, Safari either opens a new window or separates your current one with an additional view, depending on what Safari version you’re using. This command works on 3 and 4.

Within that window, you will see a lot of useful information about the page. You can see time and size measurements, script-warnings and -errors and many many more. This extensions to Safari’s WebKit provides you nearly everything you might know from FireFox Add-Ons like FireBug. And besides of that, it allows you to profile your page in a sleek and easy, graphical way.

I’m now working quite some time with those tools, exactly because of all the problems I had with Firefox on my Mac, and I must say that I love them. I love the integration and the way it allows me to debug my sites. The only thing I liked more in FireBug was the precision of its GET/POST/PUT/…-output, but most of the time I don’t need that anyway.

Enjoy!

I’m using the service for the first time on a Mac, since at work I only tested out their functionality under linux and had quite some problems with S3. Amazon’s Simple Storage Service is pretty cool regarding their pricing and provides a very acceptable up- and download speed – other than for example my Strato FTP does. The only complicated thing for somebody who’s new in that domain might be the “How do I start?“-point. S3 uses a “web-interface” which communicates using a documented REST-API. Unfortunately, under Linux there aren’t many clients which actually can communicate with this interface. Actually, I’ve only found the S3-Firefox-Plugin, which provided a way to maintain the different buckets and their content. Under OS X, there are some more (mostly Java-based) clients, including the native Cyberduck more-than-FTP client, what surprised my pretty much. This was actually the point where I’ve switched from Panic’s “Transmit” to Cyberduck, by the way.

However, I created my own buckets and uploaded some content to use it as web-share and test out a bit more the speed it provides. One con I’ve found up to now is the bucket-naming. Your personal bucket subjects a global namespace, what can lead to period of time needed for finding a name which is not occupied yet. This makes it for example pretty hard to automize bucket creations, for using them in an own Cloud-Service.

Besides, the EC2 is pretty cool, too. It provides a very flexible and (in comparison to S3) very automatable solution for cloud computing in general. It’s very fast to set up a new instance of whatever linux or windows on EC2 and run the stuff needed on it. The only con is the pricing, I guess – In my opinion it’s way too much for a Xen-I-think-it-is machine. For the price you would pay within one frequent month you could get a real root server at some hosting provider. Of course, you would lose the flexibility, but surely it depends on what you’re looking for.

In total, I’m really stunned of the infrastructure Amazon provides with their EC2/S3/etc. Services and I like the smooth way everything works out on them. I could really think of some cool projects to realize on top of these services… hm.

So I thought, let’s upgrade to 3.0.3. And so I did. Well… same thing happend. After searching for a solution for around two minutes I completely deleted this bunch of crap and installed Apple’s Safari. Which works. Without touching anything. Nothing. Not even one thing.

However, I think I really got sick of all that stuff that doesn’t just work, at least at home.

The second thing is the more and more used Shockwave/Flash stuff. With Firefox, I can play videos on YouTube smooth, fluent and with not-that-much CPU load, while the Epiphany nearly hangs up when playing such videos, produces a very high CPU load and the videos itselves studder so that it’s really no fun to watch them.

The third thing that became really annoying is the crashing. My Epiphany keeps on crashing while browsing especially sites with much content or Flash components. That’s really annoying, and the only advantage is, that Epiphany now aks whether to recover the lost session. But even this can become one’s doom when Epiphany re-loads exactly that site what made it crash and understandably hangs up/crashes, again. You can’t even click on the [X]-button, since the interface stops reacting as soon as it’s being displayed. It’s a bummer.

Now I’ve started using Iceweasel for sites that might crash Epiphany and became even more disappointed about the whole stuff. I thought that Epiphany using the Webkit version could maybe solve my problems, but unfortunatelly it’s still very unstable development code and besides, it doesn’t have any Flash-plugins yet. So I think I’m forced to start using Mozilla’s original, even if I dislike it. The freedom to choose (a.k.a. OpenSource) really is a big deal when you have ten products, out of which eight are not using the toolkit you’re working with/do not integrate at all into your desktop, and the preffered one of the two choices left doesn’t do the job at all. On this situation, I say, feel free to restrict me to one choice, which at least integrates and works the way I expect it – talking about Safari on the Mac.

By the way: Webkit is the way to go. Forget this damn Gecko engine.