We have a special place right over here, set aside just for you. Step inside and to try to make yourself comfortable for awhile. :)

As a Nokia N900 owner, I'm really impressed with the front facing video camera and skype integration. Skype is pre-installed, and Firefox mobile 3 is the default browser too. (Firefox 4 mobile is has officially been released for 1 month now for Maemo & Android and seems nice and faster too). Yesterday I did a 3.5 g skype video call that went really well between Europe and the USA, in the middle of a national holiday in the capital; the folks back home were impressed.

I digress. I like how the N900 profile feature lets me set availability to groups of apps like Skype, Jabber, SIP, etc. paired with my common net-connections like home wifi & mobile 3g. The contact book shows me who is online and available options to contact them, (Skype w/ status, SIP, cell, IM etc.) Also notifications is pretty sweet. It is a very nice linux PIM piece o' hardware. I for one, am looking forward to the next Meego device, the N950; to be most-likely announced next month at the Meego conference. (Where Meego 1.2 will also become available for N900 devices as well).

http://maemo.nokia.com/features/contacts/

http://sf2011.meego.com/

Oops, I should have written Firefox 4 for mobiles was released March 29th.

Have you tried FireFox 4 for mobile, which runs on both Android and Maemo? It was actually released Friday.

http://blog.mozilla.com/blog/2011/03/29/mozilla-launches-firefox-4-for-android-allowing-users-to-take-the-power-and-customization-of-firefox-everywhere-2/

Mostly, you are referring to Finland, or at least a huge chunk of the Finnish economy.

A classic Dilbert might be useful here:

http://dilbert.com/strips/comic/1995-02-26/

Since you asked, I'll be pleased to elaborate.

The Drupal Devs do not care about providing any kind of backward compatibility, like you might expect from a one-click installer. The reason is because no one has any interest in supporting old open-source cruft; all resources go towards the new, latest tech.

This does not mean your data fails to upgrade! The procedure in a nutshell is to temporarily switch of all extraneous modules (contrib repos), then upgrade the content between versions, then add next-gen modules.

Of course many of those modules being used do not have next-gen versions, so you might need to upgrade that code yourself; hopefully contributing back to drupal.org. Or find a replacement functional solution and implement that, or wait for the module devs to provide these upgrades for you, or ditch the functionality altogether. The stakeholders must question whether resources merit such an upgrade, and when. No matter what, skilled labor or patience and determination are required to see and upgrade a drupal website well. Bottom line it is the contributed modules used that determine the complexity of the upgrade.

How long does it take to learn to develop SAP or Oracle business applications, for example? How much does such a job pay? Maybe 'relatively complex' environments have something going for them after all? I mean these things are in-place with their own markets for developers to engage in. (And books exist, while open-source code is actually a.v.a.i.l.a.b.l.e, and legal!) If one expects everything to be sugar-coated as simple as an iPhone GUI, one might expect to earn less per day as well. The converse is true as well. Supply and demand always applies, like it's a natural law or something.

Drupal is first and foremost a professional publisher's platform with no compromises or apology. Drupal upgrades between versions are something I'll choose not even to discuss; because the pros know what to do already. Developer's are supposed to learn how to handle the professional tools for the job; it can take years for the pros to do this, and often does.

There's advantages and disadvantages to everything, so why not embrace the advantages while trying to work past any (initial?) disadvantages?

One advantage Drupal offers as opposed to rolling your own is the security of a lot of eyeballs against common SQL injection attacks, which seems ultimately responsible for taking down HBGary and the probably the Sony PSN network too. Hey, the White House uses Drupal publicly, and internally to replace famously-inept emails systems, along with NASA, the congress, the Economist.com...

Also from the owners' point of view, the Drupal framework is going to be easier to support than your system if you're not around, (and you can sell that as a feature, now).

Now, just try to imagine what you could do with it!

(Except it isn't what you have, but what you do with what you have, that really matters.)

https://spideroak.com/engineering_matters#true_privacy

True Privacy

Your SpiderOak data is readable to you alone. Most online storage systems only encrypt your data during transmission, meaning anyone with physical access to the servers your data is stored on (such as the company's staff) could have access to it. Or, even if your data is encrypted during storage, your password (or set of encryption keys) is often stored along with your data, thus making its easily decoded by anyone with local access to those servers.

With SpiderOak, you create your password on your own computer -- not on a web form received by SpiderOak servers. Once created, a strong key derivation function is used to generate encryption keys using that password, and no trace of your original password is ever uploaded to SpiderOak with your stored data.

SpiderOak's encryption is comprehensive -- even with physical access to the storage servers, SpiderOak staff cannot know even the names of your files and folders. On the server side, all that SpiderOak staff can see, are sequentially numbered containers of encrypted data.

This means that you alone have responsibility for remembering your password or 'Password Hint' (which you can create to help you remember) allowing SpiderOak to create a true 'zero-knowledge environment' – keeping your data as safe and secure as it can possibly be.

Nokia's project's just seem to be running very late is all. Nokia has said for a looong time already that they had 1 Meego device nearly ready for launch, and they were hoping for the end of last year.

This could very well be the N950: http://www.youtube.com/watch?v=tojSYC0Chms

Maybe you can imagine Nokia has this working internally with Meego, and just hasn't launched it yet for various reasons one can only guess at. Note that video is from last July. Compared to the currently shipping N8 running Symbian, well I offer that comparison as supporting evidence as to the authenticity of the video above.

Nokia CTO Rich Green has seemingly named the company’s first MeeGo device, the Nokia N950, set to launch later in 2011. Speaking at Nokia’s Developer Day keynote last week

http://www.slashgear.com/nokia-n950-meego-phone-named-very-elegant-hardware-says-cto-video-22135076/

The comments follow Nokia CTO Rich Green’s own teases about the N950, who told developers last month that “there’s a lot of work that’s gone into the technology, there’s a lot of really interesting user interface and platform design work, some very elegant hardware.” The exact nature of that hardware is currently unclear, though Nokia is believed to have axed the slide-out QWERTY keyboard of previously leaked prototypes in favor of a full-touchscreen candybar design instead.

http://www.slashgear.com/meego-gets-new-boss-promises-unique-appeal-in-n950-08138600/

Jukka Eklund at Nokia writes to the Meego Dev list: "I am thrilled to announce a little thing we started at Nokia. Basically we want to have MeeGo running in N900 device, so that it's really usable as your daily development device. Basic Handset UX should work, phone calls, SMS, web browsing. So we are concentrating on a few selected features and polish those to be "perfect". It might mean that we leave out some things in MeeGo 1.2 trunk for this edition, but that is not the default intention.

We are doing this fully on the open, and I hope this is an interesting project where we all in the community work towards the same goal: have a great MeeGo edition in the N900. This work is naturally based on the great work done already by N900 adaptation team lead by Harri and Carsten.

The wiki is up here: http://wiki.meego.com/ARM/N900/DeveloperEdition. It will populated with more information as we go, thanks for the patience.

Br,
Jukka
Developer Edition product manager" ...Also folks, be sure to stay tuned for the new Nokia N950 meant only as a (likely) unsubsidized Developer's hardware refresh of the N900. Only rumor has it that it will not arrive with a slide-out keyboard. How important is having a N900-style keyboard to you, along with the new Meego Love Nokia software continues to offer?"

[note this was posted as an article Saturday and wasn't accepted as newsworthy by Slashdot. I cannot imagine why not.]