IM Freedom? Not yet...

Back in 80's electronic Mail, used to work only inside same network and protocols.
The reason was that the electronic Mail first appeared as a feature of proprietary communication platforms. Which usually is combined with market domination attempts.
In other words company A, didn't want to support company B, as they wanted the customers(medium/large corporations back there), to keep buying from the same vendor. Which used to guarantee long term agreements and easier support, as they were required to know only about their own solutions.
After some time the unavoidable happened, some integration companies started appearing. And after another period, some companies started using SMTP as a ready-to-use and plug'n'play platforms with out-of-the box interoperability with other networks, companies and vendors.
With TCP Protocol, we also had a time when Microsoft tried to force everybody into a crappy and proprietary protocol called InetBios. Which also caused same nasty effects before fading out.
The pattern always repeated:
1) Control Tryout;
2) Gateways;
3) Migration to a common and inter-operable solution.

It seems like we don't notice it, but, we are in the exactly epicentric(fase 2) point of the IM Monopoly tryout. The only difference is that it is lasting too long, as we have a mass of ignorant people that just accepts whatever the mass market push into their computer.
This is one of the most cruel monopoly ever! Proprietary IM networks REQUIRES you to have an account on their service in order to allow you to communicate to your friends!
In other words: "They make you drop your freedom of choice in order to keep in touch with your already converted friends!"
Stop this now! Start using federated or aggregation like nimbuzz.com and fight for your freedom putting pressure in order to speed up their surrender!

Never give up your Freedom!

Start demanding the same freedom that you have in or email service, phone, etc...!

Nimbuzz Jingle/SIP Gateway

Nimbuzz recently announced that they converted all their clients to Jingle.
Considering the amount of supported Calling Gateways by Nimbuzz, it also means that they have not only a SIP/Jingle Gateway but also: Jingle/Skype, Jingle/MSN, Jingle/Yahoo, Jingle/Flash, Jingle/...

It is one more time proven that Internet Users no more need several applications running in their computers or mobile devices in order to chat with other User in different networks like MSN, Skype, Yahoo, and all the other closed networks.

Looks like Nimbuzz is one step ahead on protocol unification when talking about single stack network solutions, doing ALL other networks did using several protocols and stacks, using only ONE big Joker, XMPP.

And XMPP proves again to be a perfect ecosystem for integration, interoperability, flexibility and extensibility.

I'm very excited about what going to happen when interoperability break through Instant Messaging, Social Networks and Microblogs. In my very personal opinion, whoever is ahead will win the race, as timing is and always were everything on Internet.

Quote:
"How big will the Cloud composed by: GTalk, Twitter, Nimbuzz, Facebook, AOL, GoogleWaves and all other players that already announced the convertion?"

Jingle on Streets

It is really cool to now how many new Jingle implementers.
In Jingle Thingle 2009 I noticed that the big SIP Companies were not only just present in the meeting, but also demonstrating and testing their Jingle implementations.

We know that Google is being using Jingle on GTalk to provide Voice and File Transfers for several years, but what we don't know or maybe we didn't summarize is:
* AOL Messaging migrate to XMPP.
* Nimbuzz migrate several millions of Mobile Clients from SIP to Jingle.
* Twitter solved their scalability problems with XMPP.
* CISCO the most important SIP vendor, bought Jabber.
* OpenSER has a XMPP interoperability module.
* Asterisk has now embed support for Jingle.
* YATE has the first real full featured PBX using Jingle.
* Nokia is planning to launch a smart phone with XMPP/Jingle embeded support.

So it really seems like the simple facts that in Jingle you can negotiate several transport types, several contents in the same session opened the minds of these SIP companies to have a look on it. And the fact of Jingle in real use cases is more reliable and much easier to
implement than SIP, consolidating the protocol as the internet age multimedia signalling negotiating protocol.

Follow Jingle specification evolutions at:

XEP-0166 - Jingle
XEP-0167 - Jingle RTP Sessions
XEP-0176 - Jingle ICE-UDP Transport Method
XEP-0177 - Jingle Raw UDP Transport Method
XEP-0234 - Jingle File Transfer
XEP-0251 - Jingle Session Transfer