31–40 of 47 posts
The Pidgin instructions are incorrect. The "Local Alias" field should be set to your name, not "Facebook Chat", as this field controls what name is printed next to your messages in your local chat window. Unless your name is actually "Facebook Chat", of course.
wow. Facebook will now know when, where and how long you are online.
It's annoying that once software products become extremely popular, the developers/companies often start adding features in an attempt to be everything for everyone. This in turn makes the software unusable, because the developers are too overloaded to properly maintain their once core business. Eventually it gets replaced by a new product, and the cycle repeats itself.
I already noticed a trend in which a large portion of my friends will use facebook chat now and not even bother to login to MSN Messenger (which is the most popular client in my geographical area).
Jabber support for FB Chat is nice, but failing to support SSL/TLS is not really acceptable...
It's annoying that once software products become extremely popular, the developers/companies often start adding features in an attempt to be everything for everyone. This in turn makes the software unusable, because the developers are too overloaded to properly maintain their once core business. Eventually it gets replaced by a new product, and the cycle repeats itself.
I thought it would be a more obvious question, but how do you think this will affect the other big messenger clients/protocols? MSN/YIM/AIM/GTalk ? I already noticed a trend in which a large portion of my friends will use facebook chat now and not even bother to login to MSN Messenger (which is the most popular client in my geographical area).
However, facebook's xmpp implementation is even more restricted than google's so far. It's not even federated as of yet (not that facebook sees a need for their users to communicate outside of their network). Not federated means things like [twitterspy](http://dustin.github.com/twitterspy/) won't work.
They also don't pass many stanza types through. For example, I've seen complaints of people trying to send jingle IQs through in order to establish direct connections between two users. That's not there (yet?).
However, it does mean that you don't have to get a new chat client. I added another account to adium as xmpp and all's well. Just hoping people don't actually start talking to me over it.
The Pidgin instructions are incorrect. The "Local Alias" field should be set to your name, not "Facebook Chat", as this field controls what name is printed next to your messages in your local chat window. Unless your name is actually "Facebook Chat", of course.
What instructions? I couldn't find any, and so I can't authenticate. In particular, I have no idea what the correct server would be.
I thought it would be a more obvious question, but how do you think this will affect the other big messenger clients/protocols? MSN/YIM/AIM/GTalk ? I already noticed a trend in which a large portion of my friends will use facebook chat now and not even bother to login to MSN Messenger (which is the most popular client in my geographical area).
I reckon that because Facebook has such a large number of users already, this has the potential to kill the other IM networks. Maybe it's not so good for properly federated XMPP, though, since this also presumably means that Facebook have no real incentive to implement it.
iChat: Add new account in Preferences, select type Jabber, enter username " @chat.facebook.com" (where username is selected in Facebook settings, and you need to logout from Facebook after that change). For password use Facebook password.
At first I didn't log out after setting my username and that made it hang. That step is important.