Home » Forums » Kraken Support » Transports (AIM, ICQ, MSN, etc)

Facebook XMPP

Submitted by andbod on Thu, 02/11/2010 - 02:11

Facebook has launched XMPP integration :

http://blog.facebook.com/blog.php?post=297991732130

Any plans to update the Transport to be able to use new Facebook XMPP gateway ?

Thanks,

 

Andrea

‹ Problem with Yahoo transport and 1.1.3beta hermes.jabber.org?! ›
#1Submitted by Tim on Wed, 02/24/2010 - 11:17.

Re: Facebook XMPP

The FACEBOOK connection via KRAKEN worked for us, after 10 Feb.

////

But, there seems to be a FACEBOOK issue, the connection times-out or is easily broken; since, FACEBOOK is really using your log-in and FB status, not your Chat status.  If you are idle on FB, it can break the connection; whereas, with real IM chat clients, you can remain logged without timing out.

Also, connecting to FB chat via AIM-Client (which just added FB connect) seems to work, then disconnect; likely confusion between AIM and FB, nothing that the KRAKEN plug in can be modified to handle.  Hopefully, FB will build out their chat client so it's a standalone application that is stable.

-
Tim
#2Submitted by Flow on Fri, 02/12/2010 - 04:21.

Re: Facebook XMPP

Has anyone established a xmpp connection to facebook with the openfire/kraken XMPP (experimental) Gateway?  Isn´t that allready a way to connect a xmpp server with facebook? Why would one need an specialized facebook gateway?

I configured the Gateway with chat.facebook.com. A test returnes success, but if  I try to register I get a "wrong password" error. I´m pretty sure that I entered the right password.

#3Submitted by uded on Fri, 02/12/2010 - 06:29.

Re: Facebook XMPP

I was connecting via regular S2S. While it worked, the S2S is cripled on Facebook way worse then on GTalk for that matter...

#4Submitted by daniel on Thu, 02/11/2010 - 08:57.

Re: Facebook XMPP

Lol it JUST came out, of course there's no plans yet. I intend to try it out over the weekend and see if it's lacking anything. I'm told it lacks some key features at the moment. :/

#5Submitted by uded on Thu, 02/11/2010 - 18:56.

Re: Facebook XMPP

Yes, it does - it's cripled in so many ways, that I don't even want to begin whining. And the stability of that connection... awfull...

Well, better this then nothing, right?

#6Submitted by daniel on Fri, 02/12/2010 - 00:12.

Re: Facebook XMPP

Oh man.. I didn't want to hear that.  =(  In all seriousness, if you don't mind, do please whine lol  I'd like to know what you've experienced so far!

#7Submitted by uded on Fri, 02/12/2010 - 06:32.

Re: Facebook XMPP

Many users in my company was import Facebook via S2S and XMPP gateway today, so I'll look through the log files today and will try to come up with a list of issues.

I think it might be usefull, as in case of GTalk, to create a separate gateway based on regular XMPP to provide a way to connect to FB with less number of problems. Especially the connection stability is pissing me of - it's dropping like crazy, 7 times in last 15 minutes...

#8Submitted by daniel on Fri, 02/12/2010 - 09:13.

Re: Facebook XMPP

Oh whew - - I thought you meant connecting via c2s was doing the same thing.  Yes I intend to build a transport that connects directly to Facebook via XMPP -- with the expectation that I might have other Facebook only features from time to time.  (like I do with GTalk)  That sucks about the s2s though  =/

#9Submitted by uded on Fri, 02/12/2010 - 15:59.

Re: Facebook XMPP

Interesting thing - it's working stable since 13PM CET. And before that was terrible. They fixed something? Going to investigate...

Update - I'm not sure, but FB might be blocking S2S based on activity - we can't reconect via XMPP Gateway for over two hours now, remote system is actively blocking us...

#10Submitted by daniel on Fri, 02/12/2010 - 16:21.

Re: Facebook XMPP

How exactly are you connecting to Facebook then?  You mention s2s but also say XMPP Gateway -- if you are referring to Kraken's XMPP gateway, it's not an s2s connection, it's a c2s connection.  If you are indeed doing s2s then yeah, I guess their s2s sucks.  =/  If you are seenig this -using- Kraken's XMPP gateway though that highly concerns me...  =(  Please let me know which it is!

#11Submitted by uded on Fri, 02/12/2010 - 16:39.

Re: Facebook XMPP

We got three different Jabber installs at this point. One of them is ejabberd with XMPP gateway (c2s), the other one is using  jabberd2 without any XMPP gateway, so only S2S. And the last one running OpenFire, which is being used only by a bunch of developers as for today. This machine is doing a lot of logging and we're testing protocols on this as well.

The first one is failing miserably - no connection now, very poor statistics over last 24h.

The second one - even worse. It's working terrible for the whole time. We only managed to add few contacts and we still don't know how it happend - my colegue missed the moment, when that happend and did not saved the xml frames.

OpenFire is as bad as the two above. Failing miserably. C2S working very, very unstable. S2S did not worked at all, although someone reported that it did. But when I was checking the roosters and the logs - nada. Will be saving some frames and interactions between the servers today to investigate further...

#12Submitted by uded on Sat, 02/13/2010 - 16:44.

Re: Facebook XMPP

I can confirm, that S2S is not supported. There is a bug on Facebook bugzilla for XMPP federation.

C2S is supported, but I got a lot of issues with stability of the connection.