Custom Query (1098 matches)

Currently the code that combines floods into one message only works for buddies, it should work for groupchats too.

I am running a local bitlbee server version 3.0.1 on a GNU/Linux system (Fedora 14).

Three accounts have been set up for a user (ICQ, Jabber, Google Talk). When BitlBee is run in daemon mode as local user "bitlbee", the ICQ login succeeds, but both XMPP logins (Jabber, GoogleTalk) fail:

@root | jabber(XXX@XXX) - Logging in: Connected to server, logging in

@root | jabber(XXX@XXX) - Logging in: Converting stream to TLS

@root | jabber(XXX@XXX) - Login error: Could not connect to server

@root | jabber(XXX@XXX) - Logging in: Signing off..

However, when BitlBee is run via "bitlbee -n -v -D" (for debugging), all accounts are successfully connected, using the same configuration for the user (explicitly dictated via "/etc/bitlbee/bitlbee.conf").

I find it odd that starting the BitlBee server with an option ("-n") that should not affect the configuration leads to a different result. If this problem is due to my own ignorance, I would welcome any hints and pointers, otherwise I would be happy to help to resolve this issue on my own. I did find it difficult, however, to track down the problem due to the lack of debugging output. Am I missing something?

Regards

Dasia

Currently bitlbee assumes that all libpurple protocols support server-side buddy list that is automatically downloaded from the server upon connection. That is not true for certain protocols like "gg" (Gadu-Gadu). This makes using those protocols with bitlbee impractical since one would need to readd all buddies by hand after every bitlbee restart.

I've written a patch for bitlbee which fixes this issue by adding client-side buddy list support for those protocols that require it (currently "gg" only). I've been using this patched version of bitlbee for quite some time now and everything seems to be working fine and stable. Please review and (hopefully) merge with the source tree.