France Telecom To Support Jabber
AmX writes: "I've just seen on Jabber.com that France Telecom is going to invest $7 million in Jabber.com in exchange for a 23% equity interest in the company. Nice to see a big company supporting this technology. The details are here." With that kind of funding, perhaps Jabber really will become the next big thing. Not getting locked out of proprietary messaging systems would be a benefit to everyone. (Psss, don't forget jabber.org, too.)
Taking a look at their site, not only do they plan on making money for the 'windows' version of the client, but if you pay attention to the pics shown, you can actually have your own internal jabber server.
.02 cents worth, which with the recent crash of the market makes it more like .000045 cents worth.
What that means is that companies such as cisco, could set up their own jabber server to allow their CCO members to instant message with a Rep regarding problems (maybe bad example because if your network is down, no chance of getting to cisco in the first place).
When IM (read: icq) started becoming popular, I could imagine big companies providing tech support via IM. What happened to that? I don't know.. maybe the technology was too foreign to some of the execs and what FT is planning to do with the software is making it friendlier to the big cheeses, which will mean revenue and a return on their investment.
--
That of course is just my
I'm just going to answer all of the why use Jabber questions here. :)
Security. Jabber has support for ssl and some clients (Gabber) have built in support for pgp. Also because it is really free and open you can set up an internal server if you want and never go to the internet.
It supports most of the protocols. I can still talk to my friends who use ICQ and can talk to my friends who are on Jabber and my friend who uses MSN from one client.
I have my profile wherever I go. Since contacts and all the other information are all serverside I can have the same setup at home, at work, on the road with no effort. Even if it was nothing but an ICQ replacement that feature would make it worth it.
It is open. That is a good thing by itself.
In short Jaber is good use it and support it add squadboy@jabber.org to your contacts.
Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
You forget that ICQ is controlled by a corporation. Here are the 3 main reasons to use Jabber:
1) No corporate control.
2) No central server.
3) Open standard.
This puts Jabber in the same class as email. I run my own server and I can say who can have accounts with my system. If some other server goes down, it does not affect me. This is how IM should have been since the very beginning. You can whine all day about the number of users AIM has, or how cool ICQ is, but when it comes down to it, they all suck because they violate those 3 items above.
Let's not forget that Jabber also has some good functionality:
1) Serverside contact list.
2) Multiple chat transports (for evangelizing to other IM users)
3) Authorization that actually works.
Go, quickly! http://www.jabbercentral.com/
-Justin
*DISCLAIMER* I work for Jabber.com. Thought I'd take a few moments to respond to a few things.
1. jabber.com hired pretty much all of the original jabber.org developers.
At one time a lot of different people worked for jabber.com but right now pretty much all of the original jabber.org developers DON'T work for jabber.com. And most all of them work on the open source code anyway.
2. The jabber.org guys changed away from GPL to jabber.com's own JOSL ("jabber open source license").
It's more we like adding onto, not changing away from GPL. Like many other Open Source Licenses JOSL allows dual-licensing. Best of both worlds.
3. It is unclear (to me) if you contribute to jabber.org how/if your work will be pulled into jabber.com.
You're work's under your own copyright. Like other open source code, you agree to submit your changes for inclusion in a derivative open source work but that's all. That work will have to be open source too. We can't use your stuff without your permission in any other way. No one can.
4. jabber.com is the "commercial" version of jabber.org. You pay them for it and they give various kinds of support. They've supposedly done alot of testing on it.
Yep. Following some of the best open source business examples.
5. jabber.com is a completely different codebase than jabber.org. (for example .com uses pthreads and .org uses pth different thread libs)). The .com people are trying to add clustering and scalability that .org's code base doesn't have. I'm not sure if they're giving that back to .org
Not completely, no. And a pthreads version of the .com code has already been released to open source.
6. I'm skeptical as to how much .org will continue to thrive (as opposed to before .com) now that its main developers are working for .com on a different code base.
There's no two ways about this: jabber.org will thrive. We're doing a number of things to insure this, most importantly creating the Jabber Foundation, modeled along the lines of the Apache Foundation. We don't have all the answers on balancing commercial and open source relationships. We're open to all kinds of suggestions on how to do this. But know this: we are bound and determined to commit the resources to insure the Project grows.
7. As of a month ago, the jabber.com server didn't support the msn/yahoo/aim connections because that code is contained in "transports" modules designed to work with jabber.org's vastly different pth-based code base. And my understanding was it would be a "couple of quarter" before they're in. When you try out jabber.com's open server and see that it does appear to connect to msn/yahoo/aim, the way they are doing it is they are running a jabber.org server side-by-side with the jabber.com server and doing a jabber-jabber intermediate transport (ie the .com server is relying on the .org server to do the msn/yahoo/aim connections). I'm saying this is good or bad, but it is definitely a factor if you're considering buying a jabber.com server and support to allow your customers to connect to aim/yahoo/msn.
We're all working on the best way to do this. I think you'll see some progress sooner than later.
8. jabber.com won't sell support for aim/msn/yahoo because they can't "indemnify" it (or whatever) - they can't supposedly guarantee the connectivity. While it is true they can't guarantee the connectivity (until aim/yahoo/msn license it) it seems to me they can still sell it while explicitly stating they can't guarantee it. (I believe Odigo does - odigo.com is another IM solution that sells server, client, custom IM stuff).
See above.
Hey, if you have any questions, I'm bauer at jabber.com.
10 January 1610