1 | Frequently Asked Questions about BitlBee |
---|
2 | ======================================== |
---|
3 | |
---|
4 | Well, maybe not exactly "Frequently", but definitely "Asked" ... mostly by |
---|
5 | the developers :-) |
---|
6 | |
---|
7 | Q: WTH were you guys on when you thought of that _weird_ name? |
---|
8 | A: Though we live in The Netherlands and one of us even lives in Amsterdam, |
---|
9 | we're not on drugs ... most of the time. |
---|
10 | |
---|
11 | Q: Okay, so the cops are so evil there, you can't even admit the truth, but |
---|
12 | WTH does BitlBee mean then? |
---|
13 | A: There are a few explanations. But the most symbolical goes like: the two |
---|
14 | colors of the bee symbolize the two worlds between which the Bee flies. On |
---|
15 | the one hand there's the IM-networks, on the other is IRC. |
---|
16 | |
---|
17 | Truth be told, it's absolute nonsense. The biggest nutcase in the |
---|
18 | development team just played around with words for half an hour or so. |
---|
19 | BitlBee was the result. We liked it, we kept it. We lovingly shorten it |
---|
20 | to "the Bee" or even "het Bijtje" (Dutch for "the little Bee") sometimes. |
---|
21 | |
---|
22 | Q: What is 'root' doing in my control channel? I didn't start the Bee as |
---|
23 | root. |
---|
24 | A: 'root' is just the name for the most powerful user in BitlBee. Just like |
---|
25 | in the system, it is root who is the ... eh ... root of the |
---|
26 | functionality. Luckily, in BitlBee, root follows your orders (mostly), so |
---|
27 | no BOFHs there. |
---|
28 | |
---|
29 | We get some complaints from time to time that 'root' is a confusing name. |
---|
30 | Because of that name, some package maintainers have renamed root to, for |
---|
31 | example, BitlBee. We recognize that some people see that need. If the |
---|
32 | package maintainer hasn't renamed root, you can do this yourself with the |
---|
33 | 'rename' command. |
---|
34 | |
---|
35 | The name root is not likely to change in the 'official' releases, though. |
---|
36 | We find the metaphor of root correct and feel that there is no important |
---|
37 | (security threatening) reason to change this non-creative piece of |
---|
38 | artistic creativity. |
---|
39 | |
---|
40 | Q: When is $random_feature going to be implemented? |
---|
41 | A: It depends on the feature. We keep a list of all wishlist "bugs" in our |
---|
42 | Bug Tracking system at https://bugs.bitlbee.org/ |
---|
43 | |
---|
44 | Q: The messages I send and/or receive look weird. I see weird characters and |
---|
45 | annoying HTML codes. Or, BitlBee does evil things when I send messages with |
---|
46 | non-ASCII characters! |
---|
47 | A: You probably have to change some settings. To get rid of HTML in messages, |
---|
48 | see "help set strip_html". If you seem to have problems with your charset, |
---|
49 | see "help set charset". |
---|
50 | |
---|
51 | Although actually most of these problems should be gone by now. So if you |
---|
52 | can't get things to work well, you might have found a bug. |
---|
53 | |
---|
54 | Q: Is BitlBee forked from Gaim? |
---|
55 | A: BitlBee 0.7 was, sort-of. It contained a lot of code from Gaim 0.58 |
---|
56 | (mainly the IM-code), although heavily modified, to make it work better |
---|
57 | with BitlBee. We were planning to keep BitlBee up-to-date with later Gaim |
---|
58 | versions, but this turned out to be very time-consuming because the API |
---|
59 | changed a lot, and we don't have the time to keep up with those changes |
---|
60 | all the time. |
---|
61 | |
---|
62 | These days, we replaced the Yahoo! code with libyahoo2 (which is a |
---|
63 | separate Yahoo! module. It's derived from Gaim, but separately |
---|
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. |
---|
67 | |
---|
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. |
---|