I want to publicly apologize to my readers and to Google for my post regarding Google being evil. It was shortsighted and rash without level-headed thinking and clarity. I was misinformed, but had thought with Google supporting AIM that my gmail account could now login to AIM servers. In other words, I was under the impression that users had the ability to choose either Jabber or AIM as their protocol for Google Talk depending on which protocol their family and friends used.
This is clearly not the case. Every user who signs up for a Google Talk account is using the Jabber protocol. However, if they already have an AIM account, they can give their login information to Google, and Google will connect to the AIM servers via the method of transports- a long supported featured in Jabber. With my impression of users having the ability to choose, this lead me to the conclusion that Google was hindering the progress of Jabber by giving users another protocol to choose from.
Think of the following analogy: You are a Chevrolet car dealer, and have been selling Chevrolet cars for years. Then, all of the sudden, you decide to start selling Ford vehicles as well. You do this with the hope that you will bring more business to your dealership. Chances are good that you’ll sell more total vehicles. However, you will sell less Chevys than you were prior. This is because you are giving your shoppers a choice. As such, you are hindering overall Chevrolet sales. I was under the impression Google was doing this with Jabber and AIM.
Dax Kelson gave me a better analogy of what is actually happening. As a language institution, you sell Spanish courses. You decide now that you would like to sell Portuguese courses. However, the Portuguese package is a separate package that is added on to the Spanish package. In other words, every new customer still purchases your Spanish classes, but now they can also purchase Portuguese as an option if they would like. This is more fitting to what Google is doing. Every customer gets a Jabber account, however, they can add AIM support now too if they would like.
As with all assumptions, we can see where not clearly studying out the details takes you. In my case, public humiliation. I’m okay with that. I seem to do this to myself a lot. You would think I would learn my lesson, but I guess old habits die hard. At any event, I apologize.
Now, let’s look at why this is a good thing, versus a bad. First off, every account uses the Jabber protocol. End of story. I’ve known this for some time, even having to explain it to well established geeks in the community thinking Google Talk and Jabber are separate. They are not. Google Talk is a brand that uses the Jabber protocol. Even if you decide to give Google your AIM information, and connect to your AIM account with Google Talk, you are doing so via the transport feature of Jabber. So, let’s look at this transport feature.
One of the philosophies of Jabber is that anyone should be able to run a Jabber server under any domain. This means that I shouldn’t have to connect to a vendor-supplied server, such as MSN or Yahoo. Instant messaging should be like email, allowing any domain to communicate to any other domain. So, I have a Jabber server running under the domain of aarontoponce.org which should be able to communicate to Google Talk users using their gmail.com domain, as well as jabber.org domain users, and so on. Decentralized server-to-server communication is the main philosophy behind the Jabber protocol. So, how does AIM fit in?
With transports, the server that you are connecting to can, and should be able to connect to *any* IM server. This includes the proprietary networks and protocols, such as AIM, MSN, Yahoo, GaduGadu, Novell Groupwise, ICQ and more. This allows us to connect to our family and friends regardless of what protocol they are using. Of course, I would love to see them using Jabber instead of MSN, for example, but I can’t force them to switch, leaving behind their other contacts. So, using my Jabber account, I can use the server to connect to any server regardless. Because I support Jabber, and would love to see it’s global acceptance, I also support transports. Which means, I support the initialization of Google using AIM in their Google Talk product. Google has brought so many to the Jabber protocol, it would be silly to judge them harshly.
While I don’t support the AIM protocol, and don’t have an AIM account, I understand why Google made the move they did with their Google Talk product. The decision is to bring more users to Google and connect people to more of their friends and family without alienation.