Page 2 of 11

La gente fa schifo. Vaffanculo alla speranza.

Il risultato a dir poco tragicomico delle ultime elezioni mi ha riportato alla mente uno dei migliori pezzi di George Carlin. Mi permetto di tradurlo in italiano sostituendo l’aggettivo «americano» con «italiano»:

Tutti si lamentano dei politici. Tutti dicono che fanno schifo. Be’, ma da dove pensano che vengano questi politici? Non cadono dal cielo. Non arrivano attraverso una membrana da un’altra dimensione. Vengono da genitori italiani, da famiglie italiane, da case italiane, da scuole italiane, da chiese italiane, da imprese italiane e da università italiane… E sono eletti da cittadini italiani. Questo è il meglio che possiamo fare gente. Questo è quello che abbiamo da offrire. È ciò che produce il nostro sistema: immondizia in entrata, immondizia in uscita. Se hai cittadini egoisti ed ignoranti, avrai dirigenti egoisti ed ignoranti. E i limiti dei mandati non aiuteranno di certo: finirai semplicemente con una nuova cerchia di italiani egoisti ed ignoranti. Quindi, magari, non sono i politici che fanno schifo. Magari è qualcos’altro che fa schifo qui… Come, la gente. Sí, la gente fa schifo. Per qualcuno sarebbe un buon motto per una campagna: «La gente fa schifo. Vaffanculo alla speranza.»

Do not let social networks destroy your social skills

You see them every day. People at restaurants, bars, pubs, clubs, or even private parties, constantly looking at their mobiles… Rather than living their lives, they are validating their lives on social networks. They share their current location, tag their friends, upload pictures of their meals (rigorously altered with some cheap filter), and, since they are already on it, answer messages and leave likes and comments here and there… You name it. All this when they could actually mingle with the people around them. 🙂

Seriously, folks… Social networks are are destroying your social skills. Do not let them win. Tonight, turn off your mobile. Spend a night out with the people you really love, talk to them, laugh with them, exchange positive vibes in a way that is possible in the real world only. That is socialising. The rest is just a surrogate of it.

The sad story of the vCard format and its lack of interoperability

I have tried to reach the zen of address book synchronisation for many years. However, I have always experienced that some contact information, especially instant messaging and social networking addresses, gets lost or corrupted during the synchronisation.

The most adopted format for representing contact information is the vCard, whose last version is the 4.0 (see IETF’s RFC 6350, 2011), while the most adopted protocol for accessing contact information is the CardDAV (see in the IETF’s RFC 6352, 2011), which is based on the vCard format. Hence, I performed a little empirical study of the actual interoperability of the vCard format.

First, I defined a sample contact, where the contact information is meant to be for home:

Joe Bloggs
+44 20 1234 5678
1 Trafalgar Square, WC2N London, United Kingdom
Skype: joe.bloggs
Twitter: @joebloggs

Second, I added this contact to four different address books:

Third, I exported each of the address books to a vCard file.

Fourth, I created a sample vCard file based on the vCard format 4.0.

Finally, I compared the exported vCard files and the sample vCard file among each other. The differences between these files blew my mind.

In the following, I show these vCard files and discuss the properties which are not interoperable. Note that I stripped the irrelevant properties and rearranged the remaining properties in order to make the comparison easier.

Sample vCard file

FN:Joe Bloggs
TEL;TYPE="cell,home";PREF=1:tel:+44 20 1234 5678
ADR;TYPE=home;PREF=1:;;1 Trafalgar Square;London;;WC2N;United Kingdom

The specification of the vCard is kind of shocking. Believe or not, it does not support social networking addresses yet. Even worse, it supports constructs which are not interoperable, namely grouped properties and non-standard properties.

Grouped properties are properties prefaced with the same group name. They should be grouped together when displayed by an application. I will show examples of grouped properties later.

Non-standard properties are properties defined unilaterally or bilaterally outside the standard. They may be ignored by an application.

Hence, I was forced to represent the Twitter address by a non-standard X-SOCIALPROFILE property:


Apple Contacts (version 7.1)

FN:Joe Bloggs
TEL;type=CELL;type=VOICE;type=pref:+44 20 1234 5678
ADR;type=HOME;type=pref:;;1 Trafalgar Square;London;;WC2N;United Kingdom

The vCard file exported by Apple Contacts is only partially based on the vCard format 3.0 (see IETF’s RFC 2425 and RFC 2426, 1998) and its extension for instant messaging (see IETF’s RFC 4770, 2007).

The web address is represented by a standard URL property grouped together with a non-standard X-ABLabel property:


This issue can be solved by changing the type of the web address from “home page” to “home”. This leads to a vCard file where the web address is represented by a standard URL property:


The Twitter address is represented by a non-standard X-SOCIALPROFILE property:


Cobook (version 1.1.6)

FN:Joe Bloggs
item2.TEL;type=VOICE:+44 20 1234 5678
item3.ADR:;;1 Trafalgar Square;London;;WC2N;United Kingdom

The vCard file exported by Cobook is only partially based on the vCard format 3.0. With the exception of the name, all the contact information is represented by either grouped properties or non-standard properties.

Google Contacts (15 November 2012)

FN:Joe Bloggs
TEL;TYPE=CELL:+44 20 1234 5678
ADR;TYPE=HOME:;;1 Trafalgar Square;London;;WC2N;United Kingdom

Google Contacts does not support social networking addresses natively, so I was forced to add them as URLs.

The vCard file exported by Google Contacts is only partially based on the vCard format 3.0 (see IETF’s RFC 2425 and RFC 2426, 1998).

The colon in all the URLs is is unnecessarily escaped.

Similar to Apple Contacts, the web address is represented by a standard URL property grouped together with a non-standard X-ABLabel property:


I guess this is because Google Contacts specifically targets Apple Contacts when exporting to a vCard file. This issue can be solved by changing the type of the web address from “Home Page” to “Home”. This leads to a vCard file where the web address is represented by a standard URL property:


The Skype address is represented by a non-standard X-SKYPE property:


The Twitter address is represented by a standard URL property grouped together with a non-standard X-ABLabel property:


Memotoo (15 November 2012)

FN:Joe Bloggs
TEL;HOME;CELL:+44 20 1234 5678
ADR;HOME:;;1 Trafalgar Square;London;;WC2N;United Kingdom

The vCard file exported by Memotoo is only partially based on the vCard format 2.0 (see Versit Consortium’s specification, 1996).

The Skype address is represented by a non-standard X-SKYPE-USERNAME property:


The Twitter address is represented by a non-standard X-TWITTER property:



Given the results of this study, it is not surprising that the import/export of vCard files as well as the synchronisation via CardDAV do not behave as expected most of the time.

Common contact information such as email addresses, telephone numbers, postal addresses, web addresses, and instant messaging addresses can be represented in two ways: by means of standard properties, or by means of standard properties grouped together with non-standard properties. The second way is currently used by Apple (and other vendors targeting Apple); it is unnecessary, prevents interoperability, and promotes vendor lock-in.

Other common contact information such as social networking addresses are not supported at all.

So what should be done? Here is my suggestion:

First, the IETF should remove grouped properties and non-standard properties from the specification, since open standards should promote interoperability and prevent vendor lock-in. Second, the IETF should add social networking properties to the specification. Third, the IETF should provide an official validator for vCard files. Finally, the vendors should implement the last version of the vCard format, and they should do it right.

Update 22 November

I have shared my concerns in IETF’s vCardDAV mailing list. You can follow the thread here.

A new beginning

Dear friends and colleagues,

I would like to thank you for these last five years in Bergen. They made me grow personally and professionally, and I will never forget them.

Now, however, it is time for me to move on. I have accepted a position as research scientist at SINTEF ICT in Oslo, and I am looking forward to starting.

My former supervisor Uwe once wrote me “Sometimes changes open unforeseen new perspectives.” This sentence has never seemed more appropriate.

See you in one month, Oslo.

Why I abandoned GNU/Linux on the desktop

I have experimented with GNU/Linux in dual boot with Windows from 1997 to 2000, and I have had GNU/Linux only installed on any of my computers, both at home and at work, since 2001. I have changed distribution relatively often—3 years with Red Hat (now Fedora), 2 years with Mandrake (now Mandriva), few weeks with SuSE (now openSUSE), 1 year with Slackware (don’t ask…), 3 years with Gentoo, few weeks with Debian and 6 years with Kubuntu—but I have not changed desktop environment that much—1 year with FVWM ’95 (those were the days…), 1 year with Enlightenment, 1 year with GNOME 1, and 12 years with KDE.

I have been a loyal KDE user, contributor and advocate since the release of KDE 2.0. I have donated 100€ to the KDE e.V. organisation each year since the announcement of the “Join the Game” campaign. Last but not least, I acknowledged the KDE community in my PhD thesis (at the end of the Preface, page xi). This was just in case anybody wonders about my credentials as a GNU/Linux and KDE user…

Unfortunately, KDE does not satisfy my needs any more, and I was forced to look into other solutions. This post attempts to explain why I came to this decision, and I hope that the GNU/Linux and KDE communities will perceive this as a constructive critic.

KDE 4.0 was released before it had reached feature parity with KDE 3.5. This is because KDE developers intended KDE 4.0 as a technological preview aimed at developers, testers and early adopters only. However, the majority of KDE users did not really understand that, which is legitimate considering that .0 means at least feature complete in any other project. As a consequence, many KDE users (including Linus Torvalds) found themselves with a desktop environment which was just half baked, and eventually ditched KDE.

I expected KDE developers to adopt a more conservative release strategy in future major (point) upgrades, but apparently they did not learn any lesson. In fact, KDE 4.4 was released together with a new version of KAddressBook which was rewritten from scratch and based on the Akonadi storage service. The new version introduced several regressions compared to the previous version shipped with KDE 4.3. As a consequence, once again, many KDE users found themselves with a half baked KDE PIM suite, and eventually ditched KDE.

Actually, this time also my frustration started to mount. I wrote two verbose posts on the KDE forum to question this release management and propose a system of bounties for bug fixing. These two initiatives triggered a lively discussion in the community, but in the end nothing really happened.

KDE 4.9 was released one month ago. There are still many small nuisances with it, especially with the KDE PIM suite. And do not blame me or the packagers, please. Try to access an IMAP e-mail account with an unstable Internet connection: in the best case, Akonadi will spam the KDE notification system with connection error messages, which will eventually crash KNotify; in the worst case, Akonadi itself will crash. Try also to synchronise contacts and calendars with Google or any other well known social network: if you manage to make it work, consider yourself lucky if you do not have any loss of information.

Despite these years-old bugs, KDE developers keep spending resources on applications the world could probably do without, like the Rekonq browser and the Calligra office suite. Sometimes I ask myself if KDE developers use these applications for real, and apparently the answer is that some do not: as you can notice in the official screenshot for the KDE 4.9 release, some prefer Chrome and LibreOffice over Rekonq and Calligra, which is not surprising at all. I often read complaints about the lack of resources to maintain the KDE project. Why not focusing on less applications of higher quality rather than more applications of questionable quality then?

I tried to look into other distributions and desktop environments, but the situation seems to be even more tragic. Let us have a look at the top ten distributions on Distrowatch:

And these are just ten distributions out of hundreds, as well as just seven desktop environments out of tens—among which I can not resist to mention Trinity, which is a fork of KDE 3…

Am I the only one thinking that this fragmentation is beyond ridiculous? The developers of these distributions and desktop environments are spending massive amounts of resources to develop redundant software and compete on a mere 2% of market share. Why not focusing on less distributions and desktop environments of higher quality rather than more distributions and desktop environments of questionable quality then?

Maybe there is a question of ego, or maybe there is a problem with the bazaar itself. But the fact remains: GNU/Linux has missed all the chances to become a mainstream desktop operating system, and I do not want to use a niche operating system any more. This was a very difficult decision, and I am really sorry for that, but I need something that just works, and I need it now.

So long GNU/Linux, so long KDE, you served me well.

My new desktop operating system? Mac OS X. Do I love it? No, I actually hate it at times, but I will come back to that another day.