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...!
Monday, June 29, 2009
Sunday, June 28, 2009
XMPP BOTs
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!
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: http://twitter.com/xmppjingle
Subscribe to:
Posts (Atom)
