- Timestamp:
- 2010-09-10T11:45:31Z (14 years ago)
- Branches:
- master
- Children:
- 665c24f
- Parents:
- 3c9b095
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/FAQ
r3c9b095 recae65f 62 62 These days, we replaced the Yahoo! code with libyahoo2 (which is a 63 63 separate Yahoo! module. It's derived from Gaim, but separately 64 maintained) and wrote our own MSN module. More modules are probably going 65 to be changed, so in the near future, the API might be the only thing 66 left from Gaim. 67 68 Q: What's that Gaim doing in BitlBee error messages and my Jabber resource? 69 A: Ah, well, as you probably know we use some of Gaim's IM-modules, and we 70 don't think it's worth our time to do a search-and-replace over the whole 71 source to get rid of every reference to Gaim. In fact, we don't want to, 72 since we don't want to pretend we wrote all that code. 64 maintained) and wrote our own MSN, Jabber and Twitter modules from 65 scratch. Most of the API has also been changed, so by now the only traces 66 of Gaim left are in the "nogaim" filename. 73 67 74 About Jabber: If you want a different resource string, you can set it 75 when logging in by appending it to your Jabber ID, like: 76 lintux@jabber.com/BitlBee 68 There is good news for Gaim (or now Pidgin, of course) fans though: 69 BitlBee can now be compiled to use libpurple for all IM interactions. 70 This makes BitlBee a bit more resource-hungry, but adds support for many 71 IM protocols/networks that couldn't be used from BitlBee so far.
Note: See TracChangeset
for help on using the changeset viewer.