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?"
Sunday, June 21, 2009
Jingle Logo Proposal
I needed to create a project logo for one of my projects: minijingle.
When fooling around with XMPP logo, I came up with a proposal for Jingle Protocol logo instead.
The reasons that I like it is because it makes reference to XMPP Logo, with the J of Jingle and also to a musical note, meaning the "media" side of the protocol.

This is just the first proposal, let's see what the XMPP and Jingle fans think about it...
I will post the vectorial format here later, so we can have community contributions. (But don't forget to mention the Author! Open Source doesn't mean anonymity)
When fooling around with XMPP logo, I came up with a proposal for Jingle Protocol logo instead.
The reasons that I like it is because it makes reference to XMPP Logo, with the J of Jingle and also to a musical note, meaning the "media" side of the protocol.

This is just the first proposal, let's see what the XMPP and Jingle fans think about it...
I will post the vectorial format here later, so we can have community contributions. (But don't forget to mention the Author! Open Source doesn't mean anonymity)
Saturday, June 20, 2009
Erlang RTP Proxy
If you question yourself why move to an Erlang RTP Proxy if you are using openSER, Asterisk, or any other SIP based service. I can also say that the benefits don't seen so clear too.
But it turns out to be coolest solution for Jingle Raw-UDP Proxies! As you can integrate with your EJabberd as a module.
Check http://code.google.com/p/erlrtpproxy/ for the RTP Proxy application.
I've developed several RTP Proxy based on XMPP for the last few years, including Openfire RTP Bridge, which is pure Java and embed in all Openfire deploys.
Stay tuned! I will publish the RTP Proxy Module for EJabberd soon!
But I can give you a hint that this one looks specially promising:
But it turns out to be coolest solution for Jingle Raw-UDP Proxies! As you can integrate with your EJabberd as a module.
Check http://code.google.com/p/erlrtpproxy/ for the RTP Proxy application.
I've developed several RTP Proxy based on XMPP for the last few years, including Openfire RTP Bridge, which is pure Java and embed in all Openfire deploys.
Stay tuned! I will publish the RTP Proxy Module for EJabberd soon!
But I can give you a hint that this one looks specially promising:
Subscribe to:
Posts (Atom)
