Monday, June 29, 2009

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 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...!

Sunday, June 28, 2009


A very cool and unexplored feature of XMPP is the easy way to build and deploy automated BOTs.
This is something that is not that easy to do on proprietary networks like Skype, MSN, Yahoo etc...
I will soon start to post here some XMPP BOTs including sources in order to build a collection.

Another great factor is that XMPP BOTs are totally about interoperability meaning that if you run in a XMPP Server with interoperability enable, you can have this BOT in your contact list even if you are not connected through that server. This is totally awesome!

If you have any BOT stable and interesting enough to worth a post, please send me the code and it might be added to the collection.

Let's start building another powerful and exclusive weapon against proprietary networks!

Tuesday, June 23, 2009

Nimbuzz, Jingle and XMPP at FISL10

I will be at FISL10 this year talking about XMPP mobile freedom, also presenting Nimbuzz as an use case.
I will also talk about Jingle and how to implement a client in minutes using Smack, Minijingle API and PJMedia.

Follow my twitter for updates:

Sunday, June 21, 2009

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.

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

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)

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 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: