Facebook enabled their XMPP support today. And unlike AIM, I think it’s here to stay!

How do I log in?

Well, just use your Facebook Username and Password, and use the server chat.facebook.com.

So, what does it do?

Well, so far as I can see, it only does Chat. I heard from some people that vCards work, but I cannot confirm this. Service Discovery / Disco is also currently not available. The resource name is your pre-defined one in lower case, followed by a long hash (probably cluster routing information), here my example for Homer-LAN: homer-lan_5769bd69_47F44ABA3F597

I am sure that more and more functions will become available over the course of the next few months. It’s just a matter of slowly scaling it.

One thing which would also be cool is S2S connectivity.

But we’ll see how it goes.

No related posts.

After having had a very productive Sunday, I seem not to be able to stop doing stuff

So I started playing with chat.facebook.com (Facebook’s XMPP Server).

Having read P1’s article that Facebook would be using Ejabberd made me curious, as I don’t believe Ejabberd would scale anywhere near the needs of Facebook.

So I investigated the XML responses, and got a hint by Artur that the message IDs look nowhere near the message IDs of any server.

Now, if Facebook would’ve used an existing piece of code, they wouldn’t rewrite the message ID generation. That would be useless.

So, I checked every server I had access to, and I can say, it doesn’t behave like: Tigase, M-Link, Ejabberd, Jabberd14, Jabberd2, Prosody and Google’s XMPP Server.

Thus my conclusion: They have written their own XMPP server.

Update: Or maybe they are actually using EJD.

No related posts.

This morning at 6:01 AM (CEST) Facebook enabled username support. So you can now access your profile via: http://www.facebook.com/username .

My profile can now be viewed via: http://facebook.com/florian.jensen

What username did you register?

No related posts.