Lines 1-442
Link Here
|
|
|
1 |
BitlBee User Guide |
2 |
|
1 |
Jelmer Vernooij |
3 |
Jelmer Vernooij |
2 |
jelmer@samba.org |
4 |
|
3 |
Wilmer van der Gaast |
5 |
Wilmer van der Gaast |
4 |
wilmer@gaast.net |
6 |
|
5 |
Sjoerd Hemminga |
7 |
Sjoerd Hemminga |
6 |
sjoerd@huiswerkservice.nl |
8 |
|
7 |
This is the BitlBee User Guide. For now, the on-line help is the most |
9 |
This is the BitlBee User Guide. For now, the on-line help is the most |
8 |
up-to-date documentation. Although this document shares some parts with the |
10 |
up-to-date documentation. Although this document shares some parts with the |
9 |
on-line help system, other parts might be very outdated. The latest BitlBee |
11 |
on-line help system, other parts might be very outdated. |
10 |
release is always available from http://www.bitlbee.org/. Download the package |
12 |
|
11 |
with your favorite program and unpack it: tar xvfz bitlbee-<version>.tar.gz |
13 |
âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ |
12 |
where <version> is to be replaced by the version number of the BitlBee you |
14 |
|
13 |
downloaded (e.g. 0.91). BitlBee's build system has to be configured before |
15 |
Table of Contents |
14 |
compiling. The configure script will do this for you. Just run it, it'll set up |
16 |
|
15 |
with nice and hopefully well-working defaults. If you want to change some |
17 |
1. Installation |
16 |
settings, just try ./configure --help and see what you can do. Some variables |
18 |
|
17 |
that might be of interest to the normal user: prefix, bindir, etcdir, mandir, |
19 |
Downloading the package |
18 |
datadir - The place where all the BitlBee program files will be put. There's |
20 |
Compiling |
19 |
usually no reason to specify them all separately, just specifying prefix (or |
21 |
Configuration |
20 |
keeping the default /usr/local/) should be okay. config - The place where |
22 |
|
21 |
BitlBee will save all the per-user settings and buddy information. /var/lib/ |
23 |
2. Usage |
22 |
bitlbee/ is the default value. msn, jabber, oscar, yahoo - By default, support |
24 |
|
23 |
for all these IM-protocols (OSCAR is the protocol used by both ICQ and AIM) |
25 |
Connecting to the server |
24 |
will be compiled in. To make the binary a bit smaller, you can use these |
26 |
The &bitlbee control channel |
25 |
options to leave out support for protocols you're not planning to use. debug - |
27 |
Talking to people |
26 |
Generate an unoptimized binary with debugging symbols, mainly useful if you |
28 |
|
27 |
want to do some debugging or help us to track down a problem. strip - By |
29 |
3. Support |
28 |
default, unnecessary parts of the generated binary will be stripped out to make |
30 |
|
29 |
it as small as possible. If you don't want this (because it might cause |
31 |
BitlBee is beta software |
30 |
problems on some platforms), set this to 0. flood - To secure your BitlBee |
32 |
Support channels |
31 |
server against flooding attacks, you can use this option. It's not compiled in |
33 |
|
32 |
by default because it needs more testing first. ssl - The MSN and Jabber |
34 |
The World Wide Web |
33 |
modules require an SSL library for some of their tasks. BitlBee can use three |
35 |
IRC |
34 |
different SSL libraries: GnuTLS, mozilla-nss and OpenSSL. (OpenSSL is, however, |
36 |
Mailinglists |
35 |
a bit troublesome because of licensing issues, so don't forget to read the |
37 |
|
36 |
information configure will give you when you try to use OpenSSL!) By default, |
38 |
4. Quickstart |
37 |
configure will try to detect GnuTLS or mozilla-nss. If none of them can be |
39 |
|
38 |
found, it'll give up. If you want BitlBee to use OpenSSL, you have to |
40 |
Add and Connect To your IM Account(s) |
39 |
explicitly specify that. After running configure, you should run make. After |
41 |
Managing Contact Lists: Rename |
40 |
that, run make install as root. By default, BitlBee runs as the user nobody. |
42 |
Step Four: Managing Contact Lists: Add and Remove. |
41 |
You might want to run it as a seperate user (some computers run named or apache |
43 |
Chatting |
42 |
as nobody). Since BitlBee uses inetd, you should add the following line to /etc |
44 |
Further Resources |
43 |
/inetd.conf: 6667 stream tcp nowait nobody /usr/local/sbin/bitlbee bitlbee |
45 |
|
|
|
46 |
5. Bitlbee commands |
47 |
|
48 |
account - IM-account list maintenance |
49 |
|
50 |
account add |
51 |
account del |
52 |
account on |
53 |
account off |
54 |
account list |
55 |
account set |
56 |
|
57 |
add - Add a buddy to your contact list |
58 |
info - Request user information |
59 |
remove - Remove a buddy from your contact list |
60 |
block - Block someone |
61 |
allow - Unblock someone |
62 |
set - Miscellaneous settings |
63 |
help - BitlBee help system |
64 |
save - Save your account data |
65 |
auto_connect |
66 |
auto_reconnect |
67 |
auto_reconnect_delay |
68 |
away_devoice |
69 |
buddy_sendbuffer |
70 |
buddy_sendbuffer_delay |
71 |
charset |
72 |
debug |
73 |
default_target |
74 |
display_name |
75 |
display_namechanges |
76 |
handle_unknown |
77 |
lcnicks |
78 |
ops |
79 |
password |
80 |
port |
81 |
priority |
82 |
private |
83 |
query_order |
84 |
resource |
85 |
resource_select |
86 |
save_on_quit |
87 |
server |
88 |
simulate_netsplit |
89 |
ssl |
90 |
strip_html |
91 |
tls |
92 |
to_char |
93 |
typing_notice |
94 |
web_aware |
95 |
xmlconsole |
96 |
rename - Rename (renick) a buddy |
97 |
yes - Accept a request |
98 |
no - Deny a request |
99 |
qlist - List all the unanswered questions root asked |
100 |
register - Register yourself |
101 |
identify - Identify yourself with your password |
102 |
drop - Drop your account |
103 |
blist - List all the buddies in your contact list |
104 |
nick - Change friendly name, nick |
105 |
join_chat - Join a named groupchat/conference room |
106 |
|
107 |
6. Misc Stuff |
108 |
|
109 |
Smileys |
110 |
Groupchats |
111 |
Creating groupchats |
112 |
Groupchat channel names |
113 |
Away states |
114 |
|
115 |
Chapter 1. Installation |
116 |
|
117 |
Table of Contents |
118 |
|
119 |
Downloading the package |
120 |
Compiling |
121 |
Configuration |
122 |
|
123 |
Downloading the package |
124 |
|
125 |
The latest BitlBee release is always available from http://www.bitlbee.org/. |
126 |
Download the package with your favorite program and unpack it: tar xvfz |
127 |
bitlbee-<version>.tar.gz where <version> is to be replaced by the version |
128 |
number of the BitlBee you downloaded (e.g. 0.91). |
129 |
|
130 |
Compiling |
131 |
|
132 |
BitlBee's build system has to be configured before compiling. The configure |
133 |
script will do this for you. Just run it, it'll set up with nice and hopefully |
134 |
well-working defaults. If you want to change some settings, just try ./ |
135 |
configure --help and see what you can do. |
136 |
|
137 |
Some variables that might be of interest to the normal user: |
138 |
|
139 |
â prefix, bindir, etcdir, mandir, datadir - The place where all the BitlBee |
140 |
program files will be put. There's usually no reason to specify them all |
141 |
separately, just specifying prefix (or keeping the default /usr/local/) |
142 |
should be okay. |
143 |
|
144 |
â config - The place where BitlBee will save all the per-user settings and |
145 |
buddy information. /var/lib/bitlbee/ is the default value. |
146 |
|
147 |
â msn, jabber, oscar, yahoo - By default, support for all these IM-protocols |
148 |
(OSCAR is the protocol used by both ICQ and AIM) will be compiled in. To |
149 |
make the binary a bit smaller, you can use these options to leave out |
150 |
support for protocols you're not planning to use. |
151 |
|
152 |
â debug - Generate an unoptimized binary with debugging symbols, mainly |
153 |
useful if you want to do some debugging or help us to track down a problem. |
154 |
|
155 |
â strip - By default, unnecessary parts of the generated binary will be |
156 |
stripped out to make it as small as possible. If you don't want this |
157 |
(because it might cause problems on some platforms), set this to 0. |
158 |
|
159 |
â flood - To secure your BitlBee server against flooding attacks, you can use |
160 |
this option. It's not compiled in by default because it needs more testing |
161 |
first. |
162 |
|
163 |
â ssl - The MSN and Jabber modules require an SSL library for some of their |
164 |
tasks. BitlBee can use three different SSL libraries: GnuTLS, mozilla-nss |
165 |
and OpenSSL. (OpenSSL is, however, a bit troublesome because of licensing |
166 |
issues, so don't forget to read the information configure will give you |
167 |
when you try to use OpenSSL!) By default, configure will try to detect |
168 |
GnuTLS or mozilla-nss. If none of them can be found, it'll give up. If you |
169 |
want BitlBee to use OpenSSL, you have to explicitly specify that. |
170 |
|
171 |
After running configure, you should run make. After that, run make install as |
172 |
root. |
173 |
|
174 |
Configuration |
175 |
|
176 |
By default, BitlBee runs as the user nobody. You might want to run it as a |
177 |
seperate user (some computers run named or apache as nobody). |
178 |
|
179 |
Since BitlBee uses inetd, you should add the following line to /etc/inetd.conf: |
180 |
|
181 |
6667 stream tcp nowait nobody /usr/local/sbin/bitlbee bitlbee |
182 |
|
44 |
Inetd has to be restarted after changing the configuration. Either killall -HUP |
183 |
Inetd has to be restarted after changing the configuration. Either killall -HUP |
45 |
inetd or /etc/init.d/inetd restart should do the job on most systems. You might |
184 |
inetd or /etc/init.d/inetd restart should do the job on most systems. |
46 |
be one of the.. ehr, lucky people running an xinetd-powered distro. xinetd is |
185 |
|
47 |
quite different and they seem to be proud of that.. ;-) Anyway, if you want |
186 |
You might be one of the.. ehr, lucky people running an xinetd-powered distro. |
48 |
BitlBee to work with xinetd, just copy the bitlbee.xinetd file to your /etc/ |
187 |
xinetd is quite different and they seem to be proud of that.. ;-) Anyway, if |
49 |
xinetd.d/ directory (and probably edit it to suit your needs). You should |
188 |
you want BitlBee to work with xinetd, just copy the bitlbee.xinetd file to your |
50 |
create a directory where BitlBee can store it's data files. This should be the |
189 |
/etc/xinetd.d/ directory (and probably edit it to suit your needs). |
51 |
directory named after the value 'CONFIG' in Makefile.settings. The default is / |
190 |
|
52 |
var/lib/bitlbee, which can be created with the command mkdir -p /var/lib/ |
191 |
You should create a directory where BitlBee can store it's data files. This |
53 |
bitlbee. This directory has to be owned by the user that runs bitlbee. To make |
192 |
should be the directory named after the value 'CONFIG' in Makefile.settings. |
54 |
'nobody' owner of this directory, run chown nobody /var/lib/bitlbee. Because |
193 |
The default is /var/lib/bitlbee, which can be created with the command mkdir -p |
55 |
things like passwords are saved in this directory, it's probably a good idea to |
194 |
/var/lib/bitlbee. This directory has to be owned by the user that runs bitlbee. |
56 |
make this directory owner-read-/writable only. Since BitlBee acts just like any |
195 |
To make 'nobody' owner of this directory, run chown nobody /var/lib/bitlbee. |
57 |
other irc daemon, you can connect to it with your favorite irc client. Launch |
196 |
Because things like passwords are saved in this directory, it's probably a good |
58 |
it and connect to localhost port 6667 (or whatever host/port you are running |
197 |
idea to make this directory owner-read-/writable only. |
59 |
bitlbee on). Once you are connected to the BitlBee server, you are |
198 |
|
60 |
automatically joined to &bitlbee on that server. This channel acts like the |
199 |
Chapter 2. Usage |
61 |
'buddy list' you have on the various other chat networks. The user 'root' |
200 |
|
62 |
always hangs around in &bitlbee and acts as your interface to bitlbee. All |
201 |
Table of Contents |
63 |
commands you give on &bitlbee are 'answered' by root. You might be slightly |
202 |
|
64 |
confused by the & in the channel name. This is, however, completely allowed by |
203 |
Connecting to the server |
65 |
the IRC standards. Just try it on a regular IRC server, it should work. The |
204 |
The &bitlbee control channel |
66 |
difference between the standard #channels and &channels is that the #channels |
205 |
Talking to people |
67 |
are distributed over all the servers on the IRC network, while &channels are |
206 |
|
68 |
local to one server. Because the BitlBee control channel is local to one server |
207 |
Connecting to the server |
69 |
(and in fact, to one person), this name seems more suitable. Also, with this |
208 |
|
70 |
name, it's harder to confuse the control channel with the #bitlbee channel on |
209 |
Since BitlBee acts just like any other irc daemon, you can connect to it with |
71 |
OFTC. You can talk to by starting a query with them. In most irc clients, this |
210 |
your favorite irc client. Launch it and connect to localhost port 6667 (or |
72 |
can be done with either /msg <nick> <text> or /query <nick>. To keep the number |
211 |
whatever host/port you are running bitlbee on). |
73 |
of open query windows limited, you can also talk to people in the control |
212 |
|
74 |
channel, like <nick>: <text>. BitlBee doesn't come with a warranty and is still |
213 |
The &bitlbee control channel |
75 |
(and will probably always be) under development. That means it can crash at any |
214 |
|
76 |
time, corrupt your data or whatever. Don't use it in any production environment |
215 |
Once you are connected to the BitlBee server, you are automatically joined to & |
77 |
and don't rely on it, or at least don't blame us if things blow up. :-) http:// |
216 |
bitlbee on that server. This channel acts like the 'buddy list' you have on the |
78 |
www.bitlbee.org/ is the homepage of bitlbee and contains the most recent news |
217 |
various other chat networks. |
79 |
on bitlbee and the latest releases. BitlBee is discussed on #bitlbee on the |
218 |
|
80 |
OFTC IRC network (server: irc.oftc.net). BitlBee doesn't have any mailinglists. |
219 |
The user 'root' always hangs around in &bitlbee and acts as your interface to |
|
|
220 |
bitlbee. All commands you give on &bitlbee are 'answered' by root. |
221 |
|
222 |
You might be slightly confused by the & in the channel name. This is, however, |
223 |
completely allowed by the IRC standards. Just try it on a regular IRC server, |
224 |
it should work. The difference between the standard #channels and &channels is |
225 |
that the #channels are distributed over all the servers on the IRC network, |
226 |
while &channels are local to one server. Because the BitlBee control channel is |
227 |
local to one server (and in fact, to one person), this name seems more |
228 |
suitable. Also, with this name, it's harder to confuse the control channel with |
229 |
the #bitlbee channel on OFTC. |
230 |
|
231 |
Talking to people |
232 |
|
233 |
You can talk to by starting a query with them. In most irc clients, this can be |
234 |
done with either /msg <nick> <text> or /query <nick>. |
235 |
|
236 |
To keep the number of open query windows limited, you can also talk to people |
237 |
in the control channel, like <nick>: <text>. |
238 |
|
239 |
Chapter 3. Support |
240 |
|
241 |
Table of Contents |
242 |
|
243 |
BitlBee is beta software |
244 |
Support channels |
245 |
|
246 |
The World Wide Web |
247 |
IRC |
248 |
Mailinglists |
249 |
|
250 |
BitlBee is beta software |
251 |
|
252 |
Although BitlBee has quite some functionality it is still beta. That means it |
253 |
can crash at any time, corrupt your data or whatever. Don't use it in any |
254 |
production environment and don't rely on it. |
255 |
|
256 |
Support channels |
257 |
|
258 |
The World Wide Web |
259 |
|
260 |
http://www.bitlbee.org/ is the homepage of bitlbee and contains the most recent |
261 |
news on bitlbee and the latest releases. |
262 |
|
263 |
IRC |
264 |
|
265 |
BitlBee is discussed on #bitlbee on the OFTC IRC network (server: |
266 |
irc.oftc.net). |
267 |
|
268 |
Mailinglists |
269 |
|
270 |
BitlBee doesn't have any mailinglists. |
271 |
|
272 |
Chapter 4. Quickstart |
273 |
|
274 |
Table of Contents |
275 |
|
276 |
Add and Connect To your IM Account(s) |
277 |
Managing Contact Lists: Rename |
278 |
Step Four: Managing Contact Lists: Add and Remove. |
279 |
Chatting |
280 |
Further Resources |
281 |
|
81 |
Welcome to BitlBee, your IRC gateway to ICQ, MSN, AOL, Jabber and Yahoo Instant |
282 |
Welcome to BitlBee, your IRC gateway to ICQ, MSN, AOL, Jabber and Yahoo Instant |
82 |
Messaging Systems. The center of BitlBee is the control channel, &bitlbee. Two |
283 |
Messaging Systems. |
83 |
users will always be there, you (where "you" is the nickname you are using) and |
284 |
|
84 |
the system user, root. You need register so that all your IM settings |
285 |
The center of BitlBee is the control channel, &bitlbee. Two users will always |
85 |
(passwords, contacts, etc) can be saved on the BitlBee server. It's important |
286 |
be there, you (where "you" is the nickname you are using) and the system user, |
86 |
that you pick a good password so no one else can access your account. Register |
287 |
root. |
87 |
with this password using the register command: register <password> (without the |
288 |
|
88 |
brackets!). Be sure to remember your password. The next time you connect to the |
289 |
You need register so that all your IM settings (passwords, contacts, etc) can |
89 |
BitlBee server you will need to identify <password> so that you will be |
290 |
be saved on the BitlBee server. It's important that you pick a good password so |
90 |
recognised and logged in to all the IM services automatically. When finished, |
291 |
no one else can access your account. Register with this password using the |
91 |
type help quickstart2 to continue. Step Two: Add and Connect To your IM Account |
292 |
register command: register <password> (without the brackets!). |
92 |
(s). To add an account to the account list you will need to use the account add |
293 |
|
93 |
command: account add <protocol> <username> <password> [<server>]. For instance, |
294 |
Be sure to remember your password. The next time you connect to the BitlBee |
94 |
suppose you have a Jabber account at jabber.org with handle bitlbee@jabber.org |
295 |
server you will need to identify <password> so that you will be recognised and |
95 |
with password QuickStart, you would: < you> account add jabber |
296 |
logged in to all the IM services automatically. |
96 |
bitlbee@jabber.org QuickStart < root> Account successfully added Other |
297 |
|
97 |
available IM protocols are msn, oscar, and yahoo. OSCAR is the protocol used by |
298 |
When finished, type help quickstart2 to continue. |
98 |
ICQ and AOL. For more information about the account add command, see help |
299 |
|
99 |
account add. When you are finished adding your account(s) use the account on |
300 |
Add and Connect To your IM Account(s) |
100 |
command to enable all your accounts, type help quickstart3 to continue. Step |
301 |
|
101 |
Three: Managing Contact Lists: Rename Now BitlBee logs in and downloads the |
302 |
Step Two: Add and Connect To your IM Account(s). |
102 |
contact list from the IM server. In a few seconds, all your on-line buddies |
303 |
|
103 |
should show up in the control channel. BitlBee will convert names into |
304 |
To add an account to the account list you will need to use the account add |
104 |
IRC-friendly form (for instance: tux@example.com will be given the nickname |
305 |
command: account add <protocol> <username> <password> [<server>]. |
105 |
tux). If you have more than one person who would have the same name by this |
306 |
|
106 |
logic (for instance: tux@example.com and tux@bitlbee.org) the second one to log |
307 |
For instance, suppose you have an ICQ account with UIN 72696705 with password |
107 |
on will be tux_. The same is true if you have a tux log on to AOL and a tux log |
308 |
QuickStart, you would: |
108 |
on from Yahoo. It would be easy to get these two mixed up, so BitlBee has a |
309 |
|
109 |
rename command to change the nickname into something more suitable: rename |
310 |
< you> account add oscar 72696705 QuickStart login.icq.com |
110 |
<oldnick> <newnick> < you> rename tux_ bitlbeetux * tux_ is now known as |
311 |
< root> Account successfully added |
111 |
bitlbeetux < root> Nick successfully changed When finished, type help |
312 |
|
112 |
quickstart4 to continue. Step Four: Managing Contact Lists: Add and Remove. Now |
313 |
Other available IM protocols are jabber, msn, and yahoo. Oscar is the protocol |
113 |
you might want to add some contacts, to do this we will use the add command. It |
314 |
used by ICQ and AOL. For oscar, you need to specify the IM-server as a fourth |
114 |
needs two arguments: a connection ID (which can be a number (try account list), |
315 |
argument (for msn and yahoo there is no fourth argument). For AOL Instant |
115 |
protocol name or (part of) the screenname) and the user's handle. It is used in |
316 |
Messenger, the server name is login.oscar.aol.com. For ICQ, the server name is |
116 |
the following way: add <connection> <handle> < you> add 0 r2d2@example.com * |
317 |
login.icq.com. |
117 |
r2d2 has joined &bitlbee In this case r2d2 is online, since he/she joins the |
318 |
|
118 |
channel immediately. If the user is not online you will not see them join until |
319 |
When you are finished adding your account(s) use the account on command to |
119 |
they log on. Lets say you accidentally added r2d3@example.com rather than |
320 |
enable all your accounts, type help quickstart3 to continue. |
120 |
r2d2@example.com, or maybe you just want to remove a user from your list |
321 |
|
121 |
because you never talk to them. To remove a name you will want to use the |
322 |
Managing Contact Lists: Rename |
122 |
remove command: remove <nick> When finished, type help quickstart5 to continue. |
323 |
|
123 |
Step Five: Chatting. First of all, a person must be on your contact list for |
324 |
Step Three: Managing Contact Lists: Rename |
124 |
you to chat with them (unless it's a group chat, help groupchats for more). If |
325 |
|
125 |
someone not on your contact list sends you a message, simply add them to the |
326 |
For most protocols (currently MSN, Jabber, Yahoo and AOL) BitlBee can download |
126 |
proper account with the add command. Once they are on your list and online, you |
327 |
the contact list automatically from the IM server and all the on-line users |
127 |
can chat with them in &bitlbee: < you> tux: hey, how's the weather down there? |
328 |
should appear in the control channel when you log in. |
128 |
< tux> you: a bit chilly! Note that, although all contacts are in the &bitlbee |
329 |
|
129 |
channel, only tux will actually receive this message. The &bitlbee channel |
330 |
BitlBee will convert names into irc-friendly form (for instance: |
130 |
shouldn't be confused with a real IRC channel. If you prefer chatting in a |
331 |
tux@example.com will be given the nickname tux). If you have more than one |
131 |
separate window, use the /msg or /query command, just like on real IRC. BitlBee |
332 |
person who would have the same name by this logic (for instance: |
132 |
will remember how you talk to someone and show his/her responses the same way. |
333 |
tux@example.com and tux@bitlbee.org) the second one to log on will be tux_. The |
133 |
If you want to change the default behaviour (for people you haven't talked to |
334 |
same is true if you have a tux log on to AOL and a tux log on from Yahoo. |
134 |
yet), see help set private. You know the basics. If you want to get to know |
335 |
|
135 |
more about BitlBee, please type help quickstart6. So you want more than just |
336 |
It would be easy to get these two mixed up, so BitlBee has a rename command to |
136 |
chatting? Or maybe you're just looking for a feature? You can type help set to |
337 |
change the nickname into something more suitable: rename <oldnick> <newnick> |
137 |
learn more about the possible BitlBee user settings. Among these user settings |
338 |
|
138 |
you will find options for common issues, such as changing the charset, HTML |
339 |
< you> rename tux_ bitlbeetux |
139 |
stripping and automatic connecting (simply type set to see current user |
340 |
* tux_ is now known as bitlbeetux |
140 |
settings). For more subjects (like groupchats and away states), please type |
341 |
< root> Nick successfully changed |
141 |
help index. If you're still looking for something, please visit us in #bitlbee |
342 |
|
142 |
on the OFTC network (you can connect via irc.bitlbee.org), or mail us your |
343 |
When finished, type help quickstart4 to continue. |
143 |
problem/suggestion. Good luck and enjoy the Bee! account <action> [<arguments>] |
344 |
|
|
|
345 |
Step Four: Managing Contact Lists: Add and Remove. |
346 |
|
347 |
Step Four: Managing Contact Lists: Add and Remove. |
348 |
|
349 |
Now you might want to add some contacts, to do this we will use the add |
350 |
command. It needs two arguments: a connection ID (which can be a number (try |
351 |
account list), protocol name or (part of) the screenname) and the user's |
352 |
handle. It is used in the following way: add <connection> <handle> |
353 |
|
354 |
< you> add 0 r2d2@example.com |
355 |
* r2d2 has joined &bitlbee |
356 |
|
357 |
In this case r2d2 is online, since he/she joins the channel immediately. If the |
358 |
user is not online you will not see them join until they log on. |
359 |
|
360 |
Lets say you accidentally added r2d3@example.com rather than r2d2@example.com, |
361 |
or maybe you just want to remove a user from your list because you never talk |
362 |
to them. To remove a name you will want to use the remove command: remove |
363 |
<nick> |
364 |
|
365 |
When finished, type help quickstart5 to continue. |
366 |
|
367 |
Chatting |
368 |
|
369 |
Step Five: Chatting. |
370 |
|
371 |
First of all, a person must be on your contact list for you to chat with them |
372 |
(unless it's a group chat, help groupchats for more). If someone not on your |
373 |
contact list sends you a message, simply add them to the proper account with |
374 |
the add command. Once they are on your list and online, you can chat with them |
375 |
in &bitlbee: |
376 |
|
377 |
< you> tux: hey, how's the weather down there? |
378 |
< tux> you: a bit chilly! |
379 |
|
380 |
If you'd rather chat with them in a separate window use the /msg or /query |
381 |
command, just like you would for a private message in IRC. If you want to have |
382 |
messages automatically come up in private messages rather than in the &bitlbee |
383 |
channel, use the set private command: set private true (set private false to |
384 |
change back). |
385 |
|
386 |
You know the basics. If you want to get to know more about BitlBee, please type |
387 |
help quickstart6. |
388 |
|
389 |
Further Resources |
390 |
|
391 |
So you want more than just chatting? Or maybe you're just looking for a |
392 |
feature? |
393 |
|
394 |
You can type help set to learn more about the possible BitlBee user settings. |
395 |
Among these user settings you will find options for common issues, such as |
396 |
changing the charset, HTML stripping and automatic connecting (simply type set |
397 |
to see current user settings). |
398 |
|
399 |
For more subjects (like groupchats and away states), please type help index. |
400 |
|
401 |
If you're still looking for something, please visit us in #bitlbee on the OFTC |
402 |
network (you can connect via irc.bitlbee.org), or mail us your problem/ |
403 |
suggestion. Good luck and enjoy the Bee! |
404 |
|
405 |
Chapter 5. Bitlbee commands |
406 |
|
407 |
Table of Contents |
408 |
|
409 |
account - IM-account list maintenance |
410 |
|
411 |
account add |
412 |
account del |
413 |
account on |
414 |
account off |
415 |
account list |
416 |
account set |
417 |
|
418 |
add - Add a buddy to your contact list |
419 |
info - Request user information |
420 |
remove - Remove a buddy from your contact list |
421 |
block - Block someone |
422 |
allow - Unblock someone |
423 |
set - Miscellaneous settings |
424 |
help - BitlBee help system |
425 |
save - Save your account data |
426 |
auto_connect |
427 |
auto_reconnect |
428 |
auto_reconnect_delay |
429 |
away_devoice |
430 |
buddy_sendbuffer |
431 |
buddy_sendbuffer_delay |
432 |
charset |
433 |
debug |
434 |
default_target |
435 |
display_name |
436 |
display_namechanges |
437 |
handle_unknown |
438 |
lcnicks |
439 |
ops |
440 |
password |
441 |
port |
442 |
priority |
443 |
private |
444 |
query_order |
445 |
resource |
446 |
resource_select |
447 |
save_on_quit |
448 |
server |
449 |
simulate_netsplit |
450 |
ssl |
451 |
strip_html |
452 |
tls |
453 |
to_char |
454 |
typing_notice |
455 |
web_aware |
456 |
xmlconsole |
457 |
rename - Rename (renick) a buddy |
458 |
yes - Accept a request |
459 |
no - Deny a request |
460 |
qlist - List all the unanswered questions root asked |
461 |
register - Register yourself |
462 |
identify - Identify yourself with your password |
463 |
drop - Drop your account |
464 |
blist - List all the buddies in your contact list |
465 |
nick - Change friendly name, nick |
466 |
join_chat - Join a named groupchat/conference room |
467 |
|
468 |
account - IM-account list maintenance |
469 |
|
470 |
Syntax:Â |
471 |
|
472 |
account <action> [<arguments>] |
473 |
|
144 |
Available actions: add, del, list, on, off and set. See help account <action> |
474 |
Available actions: add, del, list, on, off and set. See help account <action> |
145 |
for more information. account add <protocol> <username> <password> Adds an |
475 |
for more information. |
146 |
account on the given server with the specified protocol, username and password |
476 |
|
147 |
to the account list. Supported protocols right now are: Jabber, MSN, OSCAR (AIM |
477 |
account add |
148 |
/ICQ) and Yahoo. For more information about adding an account, see help account |
478 |
|
149 |
add <protocol>. account add jabber <handle@server.tld> <password> The handle |
479 |
Syntax:Â |
150 |
should be a full handle, including the domain name. You can specify a |
480 |
|
151 |
servername if necessary. Normally BitlBee doesn't need this though, since it's |
481 |
account add <protocol> <username> <password> [<server>] |
152 |
able to find out the server by doing DNS SRV lookups. In previous versions it |
482 |
|
153 |
was also possible to specify port numbers and/or SSL in the server tag. This is |
483 |
Adds an account on the given server with the specified protocol, username and |
154 |
deprecated and should now be done using the account set command. This also |
484 |
password to the account list. Supported protocols right now are: Jabber, MSN, |
155 |
applies to specifying a resource in the handle (like wilmer@bitlbee.org/work). |
485 |
OSCAR (AIM/ICQ) and Yahoo. For more information about adding an account, see |
156 |
account add msn <handle@server.tld> <password> For MSN connections there are no |
486 |
help account add <protocol>. |
157 |
special arguments. account add oscar <handle> <password> OSCAR is the protocol |
487 |
|
158 |
used to connect to AIM and/or ICQ. The servers will automatically detect if |
488 |
account add jabber |
159 |
you're using a numeric or non-numeric username so there's no need to tell which |
489 |
|
160 |
network you want to connect to. < wilmer> account add oscar 72696705 |
490 |
Syntax:Â |
161 |
hobbelmeeuw < root> Account successfully added account add yahoo <handle> |
491 |
|
162 |
<password> For Yahoo! connections there are no special arguments. account del |
492 |
account add jabber <handle@server.tld> <password> [<servertag>] |
163 |
<account id> This commands deletes an account from your account list. You |
493 |
|
164 |
should signoff the account before deleting it. The account ID can be a number |
494 |
The handle should be a full handle, including the domain name. You can specify |
165 |
(see account list), the protocol name or (part of) the screenname, as long as |
495 |
a servername if necessary. Normally BitlBee doesn't need this though, since |
166 |
it matches only one connection. account on [<account id>] This command will try |
496 |
it's able to find out the server by doing DNS SRV lookups. |
167 |
to log into the specified account. If no account is specified, BitlBee will log |
497 |
|
168 |
into all the accounts that have the auto_connect flag set. The account ID can |
498 |
In previous versions it was also possible to specify port numbers and/or SSL in |
169 |
be a number (see account list), the protocol name or (part of) the screenname, |
499 |
the server tag. This is deprecated and should now be done using the account set |
170 |
as long as it matches only one connection. account off [<account id>] This |
500 |
command. This also applies to specifying a resource in the handle (like |
171 |
command disconnects the connection for the specified account. If no account is |
501 |
wilmer@bitlbee.org/work). |
172 |
specified, BitlBee will deactivate all active accounts and cancel all pending |
502 |
|
173 |
reconnects. The account ID can be a number (see account list), the protocol |
503 |
account add msn |
174 |
name or (part of) the screenname, as long as it matches only one connection. |
504 |
|
175 |
account list This command gives you a list of all the accounts known by |
505 |
Syntax:Â |
176 |
BitlBee, including the numbers you'll need for most account commands. account |
506 |
|
177 |
set <account id> account set <account id>/<setting> account set <account id>/ |
507 |
account add msn <handle@server.tld> <password> |
178 |
<setting> <value> account set -del <account id>/<setting> This account can be |
508 |
|
179 |
used to change various settings for IM accounts. For all protocols, this |
509 |
For MSN connections there are no special arguments. |
180 |
command can be used to change the handle or the password BitlBee uses to log in |
510 |
|
181 |
and if it should be logged in automatically. Some protocols have additional |
511 |
account add oscar |
182 |
settings. You can see the settings available for a connection by typing account |
512 |
|
183 |
set <account id>. For more infomation about a setting, see help set <setting>. |
513 |
Syntax:Â |
184 |
For details about the syntax of this command, see help set. The account ID can |
514 |
|
185 |
be a number (see account list), the protocol name or (part of) the screenname, |
515 |
account add oscar <handle> <password> [<servername>] |
186 |
as long as it matches only one connection. add <connection> <handle> [<nick>] |
516 |
|
187 |
add -tmp <connection> <handle> [<nick>] Adds the given buddy at the specified |
517 |
Specifying a server is required for OSCAR, since OSCAR can be used for both |
188 |
connection to your buddy list. The account ID can be a number (see account |
518 |
ICQ- and AIM-connections. Although these days it's supposed to be possible to |
189 |
list), the protocol name or (part of) the screenname, as long as it matches |
519 |
connect to ICQ via AIM-servers and vice versa, we like to stick with this |
190 |
only one connection. If you want, you can also tell BitlBee what nick to give |
520 |
separation for now. For ICQ connections, the servername is login.icq.com, for |
191 |
the new contact. The -tmp option adds the buddy to the internal BitlBee |
521 |
AIM connections it's login.oscar.aol.com. |
192 |
structures only, not to the real contact list (like done by set handle_unknown |
522 |
|
193 |
add). This allows you to talk to people who are not in your contact list. This |
523 |
< wilmer> account add oscar 72696705 hobbelmeeuw login.icq.com |
194 |
normally won't show you any presence notifications. < ctrlsoft> add 3 |
524 |
< root> Account successfully added |
195 |
gryp@jabber.org grijp * grijp has joined &bitlbee info <connection> <handle> |
525 |
|
196 |
info <nick> Requests IM-network-specific information about the specified user. |
526 |
account add yahoo |
197 |
The amount of information you'll get differs per protocol. For some protocols |
527 |
|
198 |
(ATM Yahoo! and MSN) it'll give you an URL which you can visit with a normal |
528 |
Syntax:Â |
199 |
web browser to get the information. < ctrlsoft> info 0 72696705 < root> User |
529 |
|
200 |
info - UIN: 72696705 Nick: Lintux First/Last name: Wilmer van der Gaast E-mail: |
530 |
account add yahoo <handle> <password> |
201 |
lintux@lintux.cx remove <nick> Removes the specified nick from your buddy list. |
531 |
|
202 |
< ctrlsoft> remove gryp * gryp has quit [Leaving...] block <nick> block |
532 |
For Yahoo! connections there are no special arguments. |
203 |
<connection> <handle> block <connection> Puts the specified user on your ignore |
533 |
|
204 |
list. Either specify the user's nick when you have him/her in your contact list |
534 |
account del |
205 |
or a connection number and a user handle. When called with only a connection |
535 |
|
206 |
specification as an argument, the command displays the current block list for |
536 |
Syntax:Â |
207 |
that connection. allow <nick> allow <connection> <handle> Reverse of block. |
537 |
|
208 |
Unignores the specified user or user handle on specified connection. When |
538 |
account del <account id> |
209 |
called with only a connection specification as an argument, the command |
539 |
|
210 |
displays the current allow list for that connection. set set <variable> set |
540 |
This commands deletes an account from your account list. You should signoff the |
211 |
<variable> <value> set -del <variable> Without any arguments, this command |
541 |
account before deleting it. |
212 |
lists all the set variables. You can also specify a single argument, a variable |
542 |
|
213 |
name, to get that variable's value. To change this value, specify the new value |
543 |
The account ID can be a number (see account list), the protocol name or (part |
214 |
as the second argument. With -del you can reset a setting to its default value. |
544 |
of) the screenname, as long as it matches only one connection. |
215 |
To get more help information about a setting, try: < ctrlsoft> help set private |
545 |
|
216 |
help [subject] This command gives you the help information you're reading right |
546 |
account on |
217 |
now. If you don't give any arguments, it'll give a short help index. save This |
547 |
|
218 |
command saves all your nicks and accounts immediately. Handy if you have the |
548 |
Syntax:Â |
219 |
autosave functionality disabled, or if you don't trust the program's |
549 |
|
220 |
stability... ;-) Type: boolean With this option enabled, when you identify |
550 |
account on [<account id>] |
221 |
BitlBee will automatically connect to your accounts, with this disabled it will |
551 |
|
222 |
not do this. This setting can also be changed for specific accounts using the |
552 |
This command will try to log into the specified account. If no account is |
223 |
account set command. (However, these values will be ignored if the global |
553 |
specified, BitlBee will log into all the accounts that have the auto_connect |
224 |
auto_connect setting is disabled!) Type: boolean If an IM-connections breaks, |
554 |
flag set. |
225 |
you're supposed to bring it back up yourself. Having BitlBee do this |
555 |
|
226 |
automatically might not always be a good idea, for several reasons. If you want |
556 |
The account ID can be a number (see account list), the protocol name or (part |
227 |
the connections to be restored automatically, you can enable this setting. See |
557 |
of) the screenname, as long as it matches only one connection. |
228 |
also the auto_reconnect_delay setting. This setting can also be changed for |
558 |
|
229 |
specific accounts using the account set command. (However, these values will be |
559 |
account off |
230 |
ignored if the global auto_reconnect setting is disabled!) Type: integer Tell |
560 |
|
231 |
BitlBee after how many seconds it should attempt to bring an IM-connection back |
561 |
Syntax:Â |
232 |
up after a crash. It's not a good idea to set this value very low, it will |
562 |
|
233 |
cause too much useless traffic when an IM-server is down for a few hours. See |
563 |
account off [<account id>] |
234 |
also the auto_reconnect setting. Type: boolean With this option enabled, the |
564 |
|
235 |
root user devoices people when they go away (just away, not offline) and gives |
565 |
This command disconnects the connection for the specified account. If no |
236 |
the voice back when they come back. You might dislike the voice-floods you'll |
566 |
account is specified, BitlBee will deactivate all active accounts and cancel |
237 |
get if your contact list is huge, so this option can be disabled. Type: boolean |
567 |
all pending reconnects. |
|
|
568 |
|
569 |
The account ID can be a number (see account list), the protocol name or (part |
570 |
of) the screenname, as long as it matches only one connection. |
571 |
|
572 |
account list |
573 |
|
574 |
Syntax:Â |
575 |
|
576 |
account list |
577 |
|
578 |
This command gives you a list of all the accounts known by BitlBee, including |
579 |
the numbers you'll need for most account commands. |
580 |
|
581 |
account set |
582 |
|
583 |
Syntax:Â |
584 |
|
585 |
account set <account id> |
586 |
account set <account id>/<setting> |
587 |
account set <account id>/<setting> <value> |
588 |
account set -del <account id>/<setting> |
589 |
|
590 |
This account can be used to change various settings for IM accounts. For all |
591 |
protocols, this command can be used to change the handle or the password |
592 |
BitlBee uses to log in and if it should be logged in automatically. Some |
593 |
protocols have additional settings. You can see the settings available for a |
594 |
connection by typing account set <account id>. |
595 |
|
596 |
For more infomation about a setting, see help set <setting>. For details about |
597 |
the syntax of this command, see help set. |
598 |
|
599 |
The account ID can be a number (see account list), the protocol name or (part |
600 |
of) the screenname, as long as it matches only one connection. |
601 |
|
602 |
add - Add a buddy to your contact list |
603 |
|
604 |
Syntax:Â |
605 |
|
606 |
add <connection> <handle> [<nick>] |
607 |
add -tmp <connection> <handle> [<nick>] |
608 |
|
609 |
Adds the given buddy at the specified connection to your buddy list. The |
610 |
account ID can be a number (see account list), the protocol name or (part of) |
611 |
the screenname, as long as it matches only one connection. |
612 |
|
613 |
If you want, you can also tell BitlBee what nick to give the new contact. Of |
614 |
course you can also use the rename command for that, but sometimes this might |
615 |
be more convenient. |
616 |
|
617 |
Adding -tmp adds the buddy to the internal BitlBee structures only, not to the |
618 |
real contact list (like done by set handle_unknown add). This allows you to |
619 |
talk to people who are not in your contact list. |
620 |
|
621 |
< ctrlsoft> add 3 gryp@jabber.org grijp |
622 |
* grijp has joined &bitlbee |
623 |
|
624 |
info - Request user information |
625 |
|
626 |
Syntax:Â |
627 |
|
628 |
info <connection> <handle> |
629 |
info <nick> |
630 |
|
631 |
Requests IM-network-specific information about the specified user. The amount |
632 |
of information you'll get differs per protocol. For some protocols (ATM Yahoo! |
633 |
and MSN) it'll give you an URL which you can visit with a normal web browser to |
634 |
get the information. |
635 |
|
636 |
< ctrlsoft> info 0 72696705 |
637 |
< root> User info - UIN: 72696705 Nick: Lintux First/Last name: Wilmer van der Gaast E-mail: lintux@lintux.cx |
638 |
|
639 |
remove - Remove a buddy from your contact list |
640 |
|
641 |
Syntax:Â |
642 |
|
643 |
remove <nick> |
644 |
|
645 |
Removes the specified nick from your buddy list. |
646 |
|
647 |
< ctrlsoft> remove gryp |
648 |
* gryp has quit [Leaving...] |
649 |
|
650 |
block - Block someone |
651 |
|
652 |
Syntax:Â |
653 |
|
654 |
block <nick> |
655 |
block <connection> <handle> |
656 |
block <connection> |
657 |
|
658 |
Puts the specified user on your ignore list. Either specify the user's nick |
659 |
when you have him/her in your contact list or a connection number and a user |
660 |
handle. |
661 |
|
662 |
When called with only a connection specification as an argument, the command |
663 |
displays the current block list for that connection. |
664 |
|
665 |
allow - Unblock someone |
666 |
|
667 |
Syntax:Â |
668 |
|
669 |
allow <nick> |
670 |
allow <connection> <handle> |
671 |
|
672 |
Reverse of block. Unignores the specified user or user handle on specified |
673 |
connection. |
674 |
|
675 |
When called with only a connection specification as an argument, the command |
676 |
displays the current allow list for that connection. |
677 |
|
678 |
set - Miscellaneous settings |
679 |
|
680 |
Syntax:Â |
681 |
|
682 |
set |
683 |
set <variable> |
684 |
set <variable> <value> |
685 |
set -del <variable> |
686 |
|
687 |
Without any arguments, this command lists all the set variables. You can also |
688 |
specify a single argument, a variable name, to get that variable's value. To |
689 |
change this value, specify the new value as the second argument. With -del you |
690 |
can reset a setting to its default value. |
691 |
|
692 |
To get more help information about a setting, try: |
693 |
|
694 |
< ctrlsoft> help set private |
695 |
|
696 |
help - BitlBee help system |
697 |
|
698 |
Syntax:Â |
699 |
|
700 |
help [subject] |
701 |
|
702 |
This command gives you the help information you're reading right now. If you |
703 |
don't give any arguments, it'll give a short help index. |
704 |
|
705 |
save - Save your account data |
706 |
|
707 |
Syntax:Â |
708 |
|
709 |
save |
710 |
|
711 |
This command saves all your nicks and accounts immediately. Handy if you have |
712 |
the autosave functionality disabled, or if you don't trust the program's |
713 |
stability... ;-) |
714 |
|
715 |
auto_connect |
716 |
|
717 |
Type: boolean |
718 |
|
719 |
With this option enabled, when you identify BitlBee will automatically connect |
720 |
to your accounts, with this disabled it will not do this. |
721 |
|
722 |
This setting can also be changed for specific accounts using the account set |
723 |
command. (However, these values will be ignored if the global auto_connect |
724 |
setting is disabled!) |
725 |
|
726 |
auto_reconnect |
727 |
|
728 |
Type: boolean |
729 |
|
730 |
If an IM-connections breaks, you're supposed to bring it back up yourself. |
731 |
Having BitlBee do this automatically might not always be a good idea, for |
732 |
several reasons. If you want the connections to be restored automatically, you |
733 |
can enable this setting. |
734 |
|
735 |
See also the auto_reconnect_delay setting. |
736 |
|
737 |
This setting can also be changed for specific accounts using the account set |
738 |
command. (However, these values will be ignored if the global auto_reconnect |
739 |
setting is disabled!) |
740 |
|
741 |
auto_reconnect_delay |
742 |
|
743 |
Type: integer |
744 |
|
745 |
Tell BitlBee after how many seconds it should attempt to bring an IM-connection |
746 |
back up after a crash. It's not a good idea to set this value very low, it will |
747 |
cause too much useless traffic when an IM-server is down for a few hours. |
748 |
|
749 |
See also the auto_reconnect setting. |
750 |
|
751 |
away_devoice |
752 |
|
753 |
Type: boolean |
754 |
|
755 |
With this option enabled, the root user devoices people when they go away (just |
756 |
away, not offline) and gives the voice back when they come back. You might |
757 |
dislike the voice-floods you'll get if your contact list is huge, so this |
758 |
option can be disabled. |
759 |
|
760 |
buddy_sendbuffer |
761 |
|
762 |
Type: boolean |
763 |
|
238 |
By default, when you send a message to someone, BitlBee forwards this message |
764 |
By default, when you send a message to someone, BitlBee forwards this message |
239 |
to the user immediately. When you paste a large number of lines, the lines will |
765 |
to the user immediately. When you paste a large number of lines, the lines will |
240 |
be sent in separate messages, which might not be very nice to read. If you |
766 |
be sent in separate messages, which might not be very nice to read. If you |
241 |
enable this setting, BitlBee will buffer your messages and wait for more data. |
767 |
enable this setting, BitlBee will buffer your messages and wait for more data. |
|
|
768 |
|
242 |
Using the buddy_sendbuffer_delay setting you can specify the number of seconds |
769 |
Using the buddy_sendbuffer_delay setting you can specify the number of seconds |
243 |
BitlBee should wait for more data before the complete message is sent. Please |
770 |
BitlBee should wait for more data before the complete message is sent. |
244 |
note that if you remove a buddy from your list (or if the connection to that |
771 |
|
245 |
user drops) and there's still data in the buffer, this data will be lost. |
772 |
Please note that if you remove a buddy from your list (or if the connection to |
246 |
BitlBee will not try to send the message to the user in those cases. Type: |
773 |
that user drops) and there's still data in the buffer, this data will be lost. |
247 |
integer Tell BitlBee after how many (mili)seconds a buffered message should be |
774 |
BitlBee will not try to send the message to the user in those cases. |
248 |
sent. Values greater than 5 will be interpreted as miliseconds, 5 and lower as |
775 |
|
249 |
seconds. See also the buddy_sendbuffer setting. Type: string This setting tells |
776 |
buddy_sendbuffer_delay |
250 |
BitlBee what your IRC client sends and expects. It should be equal to the |
777 |
|
251 |
charset setting of your IRC client if you want to be able to send and receive |
778 |
Type: integer |
252 |
non-ASCII text properly. Most systems use UTF-8 these days. On older systems, |
779 |
|
253 |
an iso8859 charset may work better. For example, iso8859-1 is the best choice |
780 |
Tell BitlBee after how many (mili)seconds a buffered message should be sent. |
254 |
for most Western countries. You can try to find what works best for you on |
781 |
Values greater than 5 will be interpreted as miliseconds, 5 and lower as |
255 |
http://www.unicodecharacter.com/charsets/iso8859.html Type: boolean Some |
782 |
seconds. |
256 |
debugging messages can be sent to the control channel if you wish. They're |
783 |
|
|
|
784 |
See also the buddy_sendbuffer setting. |
785 |
|
786 |
charset |
787 |
|
788 |
Type: string |
789 |
|
790 |
The charset setting enables you to use different character sets in BitlBee. |
791 |
These get converted to UTF-8 before sending and from UTF-8 when receiving. |
792 |
|
793 |
If you don't know what's the best value for this, at least iso8859-1 is the |
794 |
best choice for most Western countries. You can try to find what works best for |
795 |
you on http://czyborra.com/charsets/iso8859.html |
796 |
|
797 |
debug |
798 |
|
799 |
Type: boolean |
800 |
|
801 |
Some debugging messages can be sent to the control channel if you wish. They're |
257 |
probably not really useful for you, unless you're doing some development on |
802 |
probably not really useful for you, unless you're doing some development on |
258 |
BitlBee. Type: string With this value set to root, lines written in the control |
803 |
BitlBee. |
259 |
channel without any nickname in front of them will be interpreted as commands. |
804 |
|
260 |
If you want BitlBee to send those lines to the last person you addressed in the |
805 |
default_target |
261 |
control channel, set this to last. Type: string Currently only available for |
806 |
|
262 |
MSN connections. This setting allows you to read and change your "friendly |
807 |
Type: string |
263 |
name" for this connection. Since this is a server-side setting, it can't be |
808 |
|
264 |
changed when the account is off-line. Type: boolean With this option enabled, |
809 |
With this value set to root, lines written in the control channel without any |
265 |
root will inform you when someone in your buddy list changes his/her "friendly |
810 |
nickname in front of them will be interpreted as commands. If you want BitlBee |
266 |
name". Type: string Messages from unknown users are echoed like this by |
811 |
to send those lines to the last person you addressed in the control channel, |
267 |
default: If you want this lame user to be added automatically, you can set this |
812 |
set this to last. |
268 |
setting to "add". If you prefer to ignore messages from people you don't know, |
813 |
|
269 |
you can set this one to "ignore". "add_private" and "add_channel" are like add, |
814 |
display_name |
270 |
but you can use them to make messages from unknown buddies appear in the |
815 |
|
271 |
channel instead of a query window. Type: boolean Hereby you can change whether |
816 |
Type: string |
272 |
you want all lower case nick names or leave the case as it intended by your |
817 |
|
273 |
peer. Type: boolean Some protocols (MSN, Yahoo!) can notify via IM about new |
818 |
Currently only available for MSN connections. This setting allows you to read |
274 |
e-mail. Since most people use their Hotmail/Yahoo! addresses as a spam-box, |
819 |
and change your "friendly name" for this connection. Since this is a |
275 |
this is disabled default. If you want these notifications, you can enable this |
820 |
server-side setting, it can't be changed when the account is off-line. |
276 |
setting. Type: string Some people prefer themself and root to have operator |
821 |
|
277 |
status in &bitlbee, other people don't. You can change these states using this |
822 |
display_namechanges |
278 |
setting. The value "both" means both user and root get ops. "root" means, well, |
823 |
|
279 |
just root. "user" means just the user. "none" means nobody will get operator |
824 |
Type: boolean |
280 |
status. Type: string Use this global setting to change your "NickServ" |
825 |
|
281 |
password. This setting is also available for all IM accounts to change the |
826 |
With this option enabled, root will inform you when someone in your buddy list |
282 |
password BitlBee uses to connect to the service. Note that BitlBee will always |
827 |
changes his/her "friendly name". |
283 |
say this setting is empty. This doesn't mean there is no password, it just |
828 |
|
284 |
means that, for security reasons, BitlBee stores passwords somewhere else so |
829 |
handle_unknown |
285 |
they can't just be retrieved in plain text. Type: integer Currently only |
830 |
|
286 |
available for Jabber connections. Specifies the port number to connect to. |
831 |
Type: string |
287 |
Usually this should be set to 5222, or 5223 for SSL-connections. Type: integer |
832 |
|
|
|
833 |
Messages from unknown users are echoed like this by default: |
834 |
|
835 |
If you want this lame user to be added automatically, you can set this setting |
836 |
to "add". If you prefer to ignore messages from people you don't know, you can |
837 |
set this one to "ignore". "add_private" and "add_channel" are like add, but you |
838 |
can use them to make messages from unknown buddies appear in the channel |
839 |
instead of a query window. |
840 |
|
841 |
lcnicks |
842 |
|
843 |
Type: boolean |
844 |
|
845 |
Hereby you can change whether you want all lower case nick names or leave the |
846 |
case as it intended by your peer. |
847 |
|
848 |
ops |
849 |
|
850 |
Type: string |
851 |
|
852 |
Some people prefer themself and root to have operator status in &bitlbee, other |
853 |
people don't. You can change these states using this setting. |
854 |
|
855 |
The value "both" means both user and root get ops. "root" means, well, just |
856 |
root. "user" means just the user. "none" means nobody will get operator status. |
857 |
|
858 |
password |
859 |
|
860 |
Type: string |
861 |
|
862 |
Use this global setting to change your "NickServ" password. |
863 |
|
864 |
This setting is also available for all IM accounts to change the password |
865 |
BitlBee uses to connect to the service. |
866 |
|
867 |
Note that BitlBee will always say this setting is empty. This doesn't mean |
868 |
there is no password, it just means that, for security reasons, BitlBee stores |
869 |
passwords somewhere else so they can't just be retrieved in plain text. |
870 |
|
871 |
port |
872 |
|
873 |
Type: integer |
874 |
|
875 |
Currently only available for Jabber connections. Specifies the port number to |
876 |
connect to. Usually this should be set to 5222, or 5223 for SSL-connections. |
877 |
|
878 |
priority |
879 |
|
880 |
Type: integer |
881 |
|
288 |
Can be set for Jabber connections. When connecting to one account from multiple |
882 |
Can be set for Jabber connections. When connecting to one account from multiple |
289 |
places, this priority value will help the server to determine where to deliver |
883 |
places, this priority value will help the server to determine where to deliver |
290 |
incoming messages (that aren't addressed to a specific resource already). |
884 |
incoming messages (that aren't addressed to a specific resource already). |
|
|
885 |
|
291 |
According to RFC 3921 servers will always deliver messages to the server with |
886 |
According to RFC 3921 servers will always deliver messages to the server with |
292 |
the highest priority value. Mmessages will not be delivered to resources with a |
887 |
the highest priority value. Mmessages will not be delivered to resources with a |
293 |
negative priority setting (and should be saved as an off-line message if all |
888 |
negative priority setting (and should be saved as an off-line message if all |
294 |
available resources have a negative priority value). Type: boolean If value is |
889 |
available resources have a negative priority value). |
295 |
true, messages from users will appear in separate query windows. If false, |
890 |
|
296 |
messages from users will appear in the control channel. This setting is |
891 |
private |
297 |
remembered (during one session) per-user, this setting only changes the default |
892 |
|
298 |
state. This option takes effect as soon as you reconnect. Type: string This |
893 |
Type: boolean |
299 |
changes the order in which the questions from root (usually authorization |
894 |
|
|
|
895 |
If value is true, messages from users will appear in separate query windows. If |
896 |
false, messages from users will appear in the control channel. |
897 |
|
898 |
This setting is remembered (during one session) per-user, this setting only |
899 |
changes the default state. This option takes effect as soon as you reconnect. |
900 |
|
901 |
query_order |
902 |
|
903 |
Type: string |
904 |
|
905 |
This changes the order in which the questions from root (usually authorization |
300 |
requests from buddies) should be answered. When set to lifo, BitlBee |
906 |
requests from buddies) should be answered. When set to lifo, BitlBee |
301 |
immediately displays all new questions and they should be answered in reverse |
907 |
immediately displays all new questions and they should be answered in reverse |
302 |
order. When this is set to fifo, BitlBee displays the first question which |
908 |
order. When this is set to fifo, BitlBee displays the first question which |
303 |
comes in and caches all the others until you answer the first one. Although the |
909 |
comes in and caches all the others until you answer the first one. |
304 |
fifo setting might sound more logical (and used to be the default behaviour in |
910 |
|
305 |
older BitlBee versions), it turned out not to be very convenient for many users |
911 |
Although the fifo setting might sound more logical (and used to be the default |
306 |
when they missed the first question (and never received the next ones). Type: |
912 |
behaviour in older BitlBee versions), it turned out not to be very convenient |
307 |
string Can be set for Jabber connections. You can use this to connect to your |
913 |
for many users when they missed the first question (and never received the next |
308 |
Jabber account from multiple clients at once, with every client using a |
914 |
ones). |
309 |
different resource string. Type: string Because the IRC interface makes it |
915 |
|
310 |
pretty hard to specify the resource to talk to (when a buddy is online through |
916 |
resource |
311 |
different resources), this setting was added. Normally it's set to priority |
917 |
|
312 |
which means messages will always be delivered to the buddy's resource with the |
918 |
Type: string |
313 |
highest priority. If the setting is set to time, messages will be delivered to |
919 |
|
314 |
the resource that was last used to send you a message (or the resource that |
920 |
Can be set for Jabber connections. You can use this to connect to your Jabber |
315 |
most recently connected). Type: boolean If enabled causes BitlBee to save all |
921 |
account from multiple clients at once, with every client using a different |
316 |
current settings and account details when user disconnects. This is enabled by |
922 |
resource string. |
317 |
default, and these days there's not really a reason to have it disabled |
923 |
|
318 |
anymore. Type: string Can be set for Jabber- and OSCAR-connections. For Jabber, |
924 |
resource_select |
319 |
you might have to set this if the servername isn't equal to the part after the |
925 |
|
320 |
@ in the Jabber handle. For OSCAR this shouldn't be necessary anymore in recent |
926 |
Type: string |
321 |
BitlBee versions. Type: boolean Some IRC clients parse quit messages sent by |
927 |
|
322 |
the IRC server to see if someone really left or just disappeared because of a |
928 |
Because the IRC interface makes it pretty hard to specify the resource to talk |
323 |
netsplit. By default, BitlBee tries to simulate netsplit-like quit messages to |
929 |
to (when a buddy is online through different resources), this setting was |
324 |
keep the control channel window clean. If you don't like this (or if your IRC |
930 |
added. |
325 |
client doesn't support this) you can disable this setting. Type: boolean |
931 |
|
|
|
932 |
Normally it's set to priority which means messages will always be delivered to |
933 |
the buddy's resource with the highest priority. If the setting is set to time, |
934 |
messages will be delivered to the resource that was last used to send you a |
935 |
message (or the resource that most recently connected). |
936 |
|
937 |
save_on_quit |
938 |
|
939 |
Type: boolean |
940 |
|
941 |
If enabled causes BitlBee to save all current settings and account details when |
942 |
user disconnects. This is enabled by default, and these days there's not really |
943 |
a reason to have it disabled anymore. |
944 |
|
945 |
server |
946 |
|
947 |
Type: string |
948 |
|
949 |
Can be set for Jabber- and OSCAR-connections. For OSCAR, this must be set to |
950 |
login.icq.com if it's an ICQ connection, or login.oscar.aol.com if it's an AIM |
951 |
connection. For Jabber, you have to set this if the servername isn't equal to |
952 |
the part after the @ in the Jabber handle. |
953 |
|
954 |
simulate_netsplit |
955 |
|
956 |
Type: boolean |
957 |
|
958 |
Some IRC clients parse quit messages sent by the IRC server to see if someone |
959 |
really left or just disappeared because of a netsplit. By default, BitlBee |
960 |
tries to simulate netsplit-like quit messages to keep the control channel |
961 |
window clean. If you don't like this (or if your IRC client doesn't support |
962 |
this) you can disable this setting. |
963 |
|
964 |
ssl |
965 |
|
966 |
Type: boolean |
967 |
|
326 |
Currently only available for Jabber connections. Set this to true if the server |
968 |
Currently only available for Jabber connections. Set this to true if the server |
327 |
accepts SSL connections. Type: boolean Determines what BitlBee should do with |
969 |
accepts SSL connections. |
328 |
HTML in messages. Normally this is turned on and HTML will be stripped from |
970 |
|
329 |
messages, if BitlBee thinks there is HTML. If BitlBee fails to detect this |
971 |
strip_html |
330 |
sometimes (most likely in AIM messages over an ICQ connection), you can set |
972 |
|
331 |
this setting to always, but this might sometimes accidentally strip non-HTML |
973 |
Type: boolean |
332 |
things too. Type: boolean Newer Jabber servers allow clients to convert a |
974 |
|
333 |
plain-text session to a TLS/SSL-encrypted session. Normally (with this setting |
975 |
Determines what BitlBee should do with HTML in messages. Normally this is |
334 |
set to try) BitlBee will do this, if possible. If you want to force BitlBee to |
976 |
turned on and HTML will be stripped from messages, if BitlBee thinks there is |
335 |
use TLS sessions only (and to give up if that doesn't seem to be possible) you |
977 |
HTML. |
336 |
can set this setting to true. Set it to false if you want the session to remain |
978 |
|
337 |
plain-text. Type: string It's customary that messages meant for one specific |
979 |
If BitlBee fails to detect this sometimes (most likely in AIM messages over an |
338 |
person on an IRC channel are prepended by his/her alias followed by a colon |
980 |
ICQ connection), you can set this setting to always, but this might sometimes |
339 |
':'. BitlBee does this by default. If you prefer a different character, you can |
981 |
accidentally strip non-HTML things too. |
340 |
set it using set to_char. Please note that this setting is only used for |
982 |
|
341 |
incoming messages. For outgoing messages you can use ':' (colon) or ',' to |
983 |
tls |
342 |
separate the destination nick from the message, and this is not configurable. |
984 |
|
343 |
Type: boolean Sends you a /notice when a user starts typing a message (if |
985 |
Type: boolean |
344 |
supported by the IM protocol and the user's client). To use this, you most |
986 |
|
345 |
likely want to use a script in your IRC client to show this information in a |
987 |
Newer Jabber servers allow clients to convert a plain-text session to a TLS/ |
346 |
more sensible way. Type: string ICQ allows people to see if you're on-line via |
988 |
SSL-encrypted session. Normally (with this setting set to try) BitlBee will do |
347 |
a CGI-script. (http://status.icq.com/online.gif?icq=UIN) This can be nice to |
989 |
this, if possible. |
348 |
put on your website, but it seems that spammers also use it to see if you're |
990 |
|
349 |
online without having to add you to their contact list. So to prevent ICQ |
991 |
If you want to force BitlBee to use TLS sessions only (and to give up if that |
350 |
spamming, recent versions of BitlBee disable this feature by default. Unless |
992 |
doesn't seem to be possible) you can set this setting to true. Set it to false |
351 |
you really intend to use this feature somewhere (on forums or maybe a website), |
993 |
if you want the session to remain plain-text. |
352 |
it's probably better to keep this setting disabled. Type: boolean The Jabber |
994 |
|
353 |
module allows you to add a buddy xmlconsole to your contact list, which will |
995 |
to_char |
354 |
then show you the raw XMPP stream between you and the server. You can also send |
996 |
|
355 |
XMPP packets to this buddy, which will then be sent to the server. If you want |
997 |
Type: string |
356 |
to enable this XML console permanently (and at login time already), you can set |
998 |
|
357 |
this setting. rename <oldnick> <newnick> Renick a user in your buddy list. Very |
999 |
It's customary that messages meant for one specific person on an IRC channel |
358 |
useful, in fact just very important, if you got a lot of people with stupid |
1000 |
are prepended by his/her alias followed by a colon ':'. BitlBee does this by |
359 |
account names (or hard ICQ numbers). < itsme> rename itsme_ you * itsme_ is now |
1001 |
default. If you prefer a different character, you can set it using set to_char. |
360 |
known as you yes [<number>] Sometimes an IM-module might want to ask you a |
1002 |
|
361 |
question. (Accept this user as your buddy or not?) To accept a question, use |
1003 |
Please note that this setting is only used for incoming messages. For outgoing |
362 |
the yes command. By default, this answers the first unanswered question. You |
1004 |
messages you can use ':' (colon) or ',' to separate the destination nick from |
363 |
can also specify a different question as an argument. You can use the qlist |
1005 |
the message, and this is not configurable. |
364 |
command for a list of questions. no [<number>] Sometimes an IM-module might |
1006 |
|
365 |
want to ask you a question. (Accept this user as your buddy or not?) To reject |
1007 |
typing_notice |
366 |
a question, use the no command. By default, this answers the first unanswered |
1008 |
|
367 |
question. You can also specify a different question as an argument. You can use |
1009 |
Type: boolean |
368 |
the qlist command for a list of questions. qlist This gives you a list of all |
1010 |
|
369 |
the unanswered questions from root. register <password> BitlBee can save your |
1011 |
Sends you a /notice when a user starts typing a message (if the protocol |
370 |
settings so you won't have to enter all your IM passwords every time you log |
1012 |
supports it, MSN for example). This is a bug, not a feature. (But please don't |
371 |
in. If you want the Bee to save your settings, use the register command. Please |
1013 |
report it.. ;-) You don't want to use it. Really. In fact the |
372 |
do pick a secure password, don't just use your nick as your password. Please |
1014 |
typing-notification is just one of the least useful 'innovations' ever. It's |
373 |
note that IRC is not an encrypted protocol, so the passwords still go over the |
1015 |
just there because some guy will probably ask me about it anyway. ;-) |
374 |
network in plaintext. Evil people with evil sniffers will read it all. (So |
1016 |
|
375 |
don't use your root password.. ;-) To identify yourself in later sessions, you |
1017 |
web_aware |
376 |
can use the identify command. To change your password later, you can use the |
1018 |
|
377 |
set password command. identify <password> BitlBee saves all your settings |
1019 |
Type: string |
378 |
(contacts, accounts, passwords) on-server. To prevent other users from just |
1020 |
|
379 |
logging in as you and getting this information, you'll have to identify |
1021 |
ICQ allows people to see if you're on-line via a CGI-script. (http:// |
380 |
yourself with your password. You can register this password using the register |
1022 |
status.icq.com/online.gif?icq=UIN) This can be nice to put on your website, but |
381 |
command. Once you're registered, you can change your password using set |
1023 |
it seems that spammers also use it to see if you're online without having to |
382 |
password <password>. drop <password> Drop your BitlBee registration. Your |
1024 |
add you to their contact list. So to prevent ICQ spamming, recent versions of |
383 |
account files will be removed and your password will be forgotten. For obvious |
1025 |
BitlBee disable this feature by default. |
384 |
security reasons, you have to specify your NickServ password to make this |
1026 |
|
385 |
command work. blist [all|online|offline|away] You can get a better readable |
1027 |
Unless you really intend to use this feature somewhere (on forums or maybe a |
386 |
buddy list using the blist command. If you want a complete list (including the |
1028 |
website), it's probably better to keep this setting disabled. |
387 |
offline users) you can use the all argument. nick <connection> [<new nick>] |
1029 |
|
388 |
nick <connection> Deprecated: Use the per-account display_name setting to read |
1030 |
xmlconsole |
389 |
and change this information. < wouter> account set 1/display_name "The majestik |
1031 |
|
390 |
møøse" < root> display_name = `The majestik møøse' join_chat <connection> <room |
1032 |
Type: boolean |
391 |
name> [<channel name>] [<room nickname>] [<password>] On most IM-networks |
1033 |
|
392 |
groupchats can be started using the /join command. (/join #foo to start a |
1034 |
The Jabber module allows you to add a buddy xmlconsole to your contact list, |
393 |
chatroom with you and foo) This doesn't work with names groupchats though |
1035 |
which will then show you the raw XMPP stream between you and the server. You |
394 |
(which exist on Jabber networks and AIM, for example), instead you can use this |
1036 |
can also send XMPP packets to this buddy, which will then be sent to the |
395 |
command. The first two arguments are required. room name is the name of the |
1037 |
server. |
396 |
chatroom on the IM-network. channel name is the IRC channel name BitlBee should |
1038 |
|
397 |
map this to. room nickname is the nickname you want to have in this channel. If |
1039 |
If you want to enable this XML console permanently (and at login time already), |
398 |
you don't give these options, BitlBee will do the right guesses. The following |
1040 |
you can set this setting. |
399 |
command will join you to the chatroom called bitlbee@conference.bitlbee.org. |
1041 |
|
400 |
The channel will be called &bitlbee-help because &bitlbee will already be in |
1042 |
rename - Rename (renick) a buddy |
401 |
use. Your nickname will be help-me. < wilmer> join_chat jabber |
1043 |
|
402 |
bitlbee@conference.bitlbee.org &bitlbee-help help-me All MSN smileys (except |
1044 |
Syntax:Â |
403 |
one) are case insensitive and work without the nose too. (Y) Thumbs up (N) |
1045 |
|
404 |
Thumbs down (B) Beer mug (D) Martini glass (X) Girl (Z) Boy (6) Devil smiley :- |
1046 |
rename <oldnick> <newnick> |
405 |
[ Vampire bat (}) Right hug ({) Left hug (M) MSN Messenger or Windows Messenger |
1047 |
|
406 |
icon (think a BitlBee logo here ;) :-S Crooked smiley (Confused smiley) :-$ |
1048 |
Renick a user in your buddy list. Very useful, in fact just very important, if |
407 |
Embarrassed smiley (H) Smiley with sunglasses :-@ Angry smiley (A) Angel smiley |
1049 |
you got a lot of people with stupid account names (or hard ICQ numbers). |
408 |
(L) Red heart (Love) (U) Broken heart (K) Red lips (Kiss) (G) Gift with bow (F) |
1050 |
|
409 |
Red rose (W) Wilted rose (P) Camera (~) Film strip (T) Telephone receiver (@) |
1051 |
< itsme> rename itsme_ you |
410 |
Cat face (&) Dog's head (C) Coffee cup (I) Light bulb (S) Half-moon (Case |
1052 |
* itsme_ is now known as you |
411 |
sensitive!) (*) Star (8) Musical eighth note (E) Envelope (^) Birthday cake (O) |
1053 |
|
412 |
Clock BitlBee now supports groupchats on all IM networks. This text will try to |
1054 |
yes - Accept a request |
413 |
explain you how they work. As soon as someone invites you into a groupchat, you |
1055 |
|
414 |
will be force-joined or invited (depending on the protocol) into a new virtual |
1056 |
Syntax:Â |
415 |
channel with all the people in there. You can leave the channel at any time, |
1057 |
|
416 |
just like you would close the window in regular IM clients. Please note that |
1058 |
yes [<number>] |
417 |
root-commands don't work in groupchat channels, they only work in the control |
1059 |
|
418 |
channel (or to root directly). Of course you can also create your own |
1060 |
Sometimes an IM-module might want to ask you a question. (Accept this user as |
419 |
groupchats. Type help groupchats2 to see how. If you want to start a groupchat |
1061 |
your buddy or not?) To accept a question, use the yes command. |
420 |
with the person lisa_msn in it, just join the channel #lisa_msn. BitlBee will |
1062 |
|
421 |
refuse to join you to the channel with that name, but it will create a new |
1063 |
By default, this answers the first unanswered question. You can also specify a |
422 |
virtual channel with root, you and lisa_msn in it. Of course a channel with |
1064 |
different question as an argument. You can use the qlist command for a list of |
423 |
only two people isn't really exciting yet. So the next step is to invite some |
1065 |
questions. |
424 |
other people to the channel. For this, you can use the /invite command of your |
1066 |
|
425 |
IRC client. Please do keep in mind that all the people have to be on the same |
1067 |
no - Deny a request |
426 |
network and contact list! You can't invite Yahoo! buddies into an MSN |
1068 |
|
427 |
groupchat. Some protocols (like Jabber) also support named groupchats. BitlBee |
1069 |
Syntax:Â |
428 |
now supports these too. You can use the join_chat command to join them. See |
1070 |
|
429 |
help join_chat for more information. As you might've expected, you can just use |
1071 |
no [<number>] |
430 |
the /away command in your IRC client to set an away-state. BitlBee supports |
1072 |
|
431 |
most away-states supported by the protocols. Not all away states are supported |
1073 |
Sometimes an IM-module might want to ask you a question. (Accept this user as |
432 |
by all protocols, and some protocols have different names for them. BitlBee |
1074 |
your buddy or not?) To reject a question, use the no command. |
433 |
will try to pick the best available alias from this list for every connection: |
1075 |
|
434 |
Away from computer, Away, Extended away NA, N/A, Not available Busy, Do not |
1076 |
By default, this answers the first unanswered question. You can also specify a |
435 |
disturb, DND, Occupied Be right back, BRB On the phone, Phone, On phone Out to |
1077 |
different question as an argument. You can use the qlist command for a list of |
436 |
lunch, Lunch, Food Invisible, Hidden So /away Food will set your state to "Out |
1078 |
questions. |
437 |
to lunch" on your MSN connection, and for most other connections the default, |
1079 |
|
438 |
"Away" or "Away from computer" will be chosen. You can also add more |
1080 |
qlist - List all the unanswered questions root asked |
439 |
information to your away message. Setting it to "Busy - Fixing BitlBee bugs" |
1081 |
|
440 |
will set your IM-away-states to Busy, but your away message will be more |
1082 |
Syntax:Â |
441 |
descriptive for people on IRC. Most IM-protocols can also show this additional |
1083 |
|
442 |
information to your buddies. |
1084 |
qlist |
|
|
1085 |
|
1086 |
This gives you a list of all the unanswered questions from root. |
1087 |
|
1088 |
register - Register yourself |
1089 |
|
1090 |
Syntax:Â |
1091 |
|
1092 |
register <password> |
1093 |
|
1094 |
BitlBee can save your settings so you won't have to enter all your IM passwords |
1095 |
every time you log in. If you want the Bee to save your settings, use the |
1096 |
register command. |
1097 |
|
1098 |
Please do pick a secure password, don't just use your nick as your password. |
1099 |
Please note that IRC is not an encrypted protocol, so the passwords still go |
1100 |
over the network in plaintext. Evil people with evil sniffers will read it all. |
1101 |
(So don't use your root password.. ;-) |
1102 |
|
1103 |
To identify yourself in later sessions, you can use the identify command. To |
1104 |
change your password later, you can use the set password command. |
1105 |
|
1106 |
identify - Identify yourself with your password |
1107 |
|
1108 |
Syntax:Â |
1109 |
|
1110 |
identify <password> |
1111 |
|
1112 |
BitlBee saves all your settings (contacts, accounts, passwords) on-server. To |
1113 |
prevent other users from just logging in as you and getting this information, |
1114 |
you'll have to identify yourself with your password. You can register this |
1115 |
password using the register command. |
1116 |
|
1117 |
Once you're registered, you can change your password using set password |
1118 |
<password>. |
1119 |
|
1120 |
drop - Drop your account |
1121 |
|
1122 |
Syntax:Â |
1123 |
|
1124 |
drop <password> |
1125 |
|
1126 |
Drop your BitlBee registration. Your account files will be removed and your |
1127 |
password will be forgotten. For obvious security reasons, you have to specify |
1128 |
your NickServ password to make this command work. |
1129 |
|
1130 |
blist - List all the buddies in your contact list |
1131 |
|
1132 |
Syntax:Â |
1133 |
|
1134 |
blist [all|online|offline|away] |
1135 |
|
1136 |
You can get a better readable buddy list using the blist command. If you want a |
1137 |
complete list (including the offline users) you can use the all argument. |
1138 |
|
1139 |
nick - Change friendly name, nick |
1140 |
|
1141 |
Syntax:Â |
1142 |
|
1143 |
nick <connection> [<new nick>] |
1144 |
nick |
1145 |
|
1146 |
This command allows to set the friendly name of an im account. If no new name |
1147 |
is specified the command will report the current name. When the name contains |
1148 |
spaces, don't forget to quote the whole nick in double quotes. Currently this |
1149 |
command is only supported by the MSN protocol. |
1150 |
|
1151 |
It is recommended to use the per-account display_name setting to read and |
1152 |
change this information. The nick command is deprecated. |
1153 |
|
1154 |
< wouter> nick 1 "Wouter Paesen" |
1155 |
< root> Setting your name on connection 1 to `Wouter Paesen' |
1156 |
|
1157 |
join_chat - Join a named groupchat/conference room |
1158 |
|
1159 |
Syntax:Â |
1160 |
|
1161 |
join_chat <connection> <room name> [<channel name>] [<room nickname>] [<password>] |
1162 |
|
1163 |
On most IM-networks groupchats can be started using the /join command. (/join # |
1164 |
foo to start a chatroom with you and foo) This doesn't work with names |
1165 |
groupchats though (which exist on Jabber networks and AIM, for example), |
1166 |
instead you can use this command. |
1167 |
|
1168 |
The first two arguments are required. room name is the name of the chatroom on |
1169 |
the IM-network. channel name is the IRC channel name BitlBee should map this |
1170 |
to. room nickname is the nickname you want to have in this channel. If you |
1171 |
don't give these options, BitlBee will do the right guesses. |
1172 |
|
1173 |
The following command will join you to the chatroom called |
1174 |
bitlbee@conference.bitlbee.org. The channel will be called &bitlbee-help |
1175 |
because &bitlbee will already be in use. Your nickname will be help-me. |
1176 |
|
1177 |
< wilmer> join_chat jabber bitlbee@conference.bitlbee.org &bitlbee-help help-me |
1178 |
|
1179 |
Chapter 6. Misc Stuff |
1180 |
|
1181 |
Table of Contents |
1182 |
|
1183 |
Smileys |
1184 |
Groupchats |
1185 |
Creating groupchats |
1186 |
Groupchat channel names |
1187 |
Away states |
1188 |
|
1189 |
Smileys |
1190 |
|
1191 |
All MSN smileys (except one) are case insensitive and work without the nose |
1192 |
too. |
1193 |
|
1194 |
(Y) |
1195 |
|
1196 |
Thumbs up |
1197 |
|
1198 |
(N) |
1199 |
|
1200 |
Thumbs down |
1201 |
|
1202 |
(B) |
1203 |
|
1204 |
Beer mug |
1205 |
|
1206 |
(D) |
1207 |
|
1208 |
Martini glass |
1209 |
|
1210 |
(X) |
1211 |
|
1212 |
Girl |
1213 |
|
1214 |
(Z) |
1215 |
|
1216 |
Boy |
1217 |
|
1218 |
(6) |
1219 |
|
1220 |
Devil smiley |
1221 |
|
1222 |
:-[ |
1223 |
|
1224 |
Vampire bat |
1225 |
|
1226 |
(}) |
1227 |
|
1228 |
Right hug |
1229 |
|
1230 |
({) |
1231 |
|
1232 |
Left hug |
1233 |
|
1234 |
(M) |
1235 |
|
1236 |
MSN Messenger or Windows Messenger icon (think a BitlBee logo here ;) |
1237 |
|
1238 |
:-S |
1239 |
|
1240 |
Crooked smiley (Confused smiley) |
1241 |
|
1242 |
:-$ |
1243 |
|
1244 |
Embarrassed smiley |
1245 |
|
1246 |
(H) |
1247 |
|
1248 |
Smiley with sunglasses |
1249 |
|
1250 |
:-@ |
1251 |
|
1252 |
Angry smiley |
1253 |
|
1254 |
(A) |
1255 |
|
1256 |
Angel smiley |
1257 |
|
1258 |
(L) |
1259 |
|
1260 |
Red heart (Love) |
1261 |
|
1262 |
(U) |
1263 |
|
1264 |
Broken heart |
1265 |
|
1266 |
(K) |
1267 |
|
1268 |
Red lips (Kiss) |
1269 |
|
1270 |
(G) |
1271 |
|
1272 |
Gift with bow |
1273 |
|
1274 |
(F) |
1275 |
|
1276 |
Red rose |
1277 |
|
1278 |
(W) |
1279 |
|
1280 |
Wilted rose |
1281 |
|
1282 |
(P) |
1283 |
|
1284 |
Camera |
1285 |
|
1286 |
(~) |
1287 |
|
1288 |
Film strip |
1289 |
|
1290 |
(T) |
1291 |
|
1292 |
Telephone receiver |
1293 |
|
1294 |
(@) |
1295 |
|
1296 |
Cat face |
1297 |
|
1298 |
(&) |
1299 |
|
1300 |
Dog's head |
1301 |
|
1302 |
(C) |
1303 |
|
1304 |
Coffee cup |
1305 |
|
1306 |
(I) |
1307 |
|
1308 |
Light bulb |
1309 |
|
1310 |
(S) |
1311 |
|
1312 |
Half-moon (Case sensitive!) |
1313 |
|
1314 |
(*) |
1315 |
|
1316 |
Star |
1317 |
|
1318 |
(8) |
1319 |
|
1320 |
Musical eighth note |
1321 |
|
1322 |
(E) |
1323 |
|
1324 |
Envelope |
1325 |
|
1326 |
(^) |
1327 |
|
1328 |
Birthday cake |
1329 |
|
1330 |
(O) |
1331 |
|
1332 |
Clock |
1333 |
|
1334 |
This list was extracted from http://help.msn.com/!data/en_us/data/ |
1335 |
messengerv50.its51/$content$/EMOTICONS.HTM?H_APP=. |
1336 |
|
1337 |
Groupchats |
1338 |
|
1339 |
Since version 0.8x, BitlBee supports groupchats on the MSN and Yahoo! networks. |
1340 |
This text will try to explain you how they work. |
1341 |
|
1342 |
As soon as someone invites you into a groupchat, you will be force-joined or |
1343 |
invited (depending on the protocol) into a new virtual channel with all the |
1344 |
people in there. You can leave the channel at any time, just like you would |
1345 |
close the window in regular IM clients. Please note that root-commands don't |
1346 |
work in groupchat channels, they only work in the control channel (or to root |
1347 |
directly). |
1348 |
|
1349 |
Of course you can also create your own groupchats. Type help groupchats2 to see |
1350 |
how. |
1351 |
|
1352 |
Creating groupchats |
1353 |
|
1354 |
If you want to start a groupchat with the person jim_msn in it, just join the |
1355 |
channel #jim_msn. BitlBee will refuse to join you to the channel with that |
1356 |
name, but it will create a new virtual channel with root, you and jim_msn in |
1357 |
it. |
1358 |
|
1359 |
Of course a channel with only two people isn't really exciting yet. So the next |
1360 |
step is to invite some other people to the channel. For this, you can use the / |
1361 |
invite command of your IRC client. Please do keep in mind that all the people |
1362 |
have to be on the same network and contact list! You can't invite Yahoo! |
1363 |
buddies into an MSN groupchat. |
1364 |
|
1365 |
Some protocols (like Jabber) also support named groupchats. BitlBee now |
1366 |
supports these too. You can use the join_chat command to join them. See help |
1367 |
join_chat for more information. |
1368 |
|
1369 |
This is all you'll probably need to know. If you have any problems, please read |
1370 |
help groupchats3. |
1371 |
|
1372 |
Groupchat channel names |
1373 |
|
1374 |
Obviously the (numbered) channel names don't make a lot of sense. Problem is |
1375 |
that groupchats usually don't have names at all in the IM-world, while IRC |
1376 |
insists on a name. So BitlBee just generates something random, just don't pay |
1377 |
attention to it. :-) |
1378 |
|
1379 |
Please also note that BitlBee doesn't support groupchats for all protocols yet. |
1380 |
BitlBee will tell you so. Support for other protocols will hopefully come |
1381 |
later. |
1382 |
|
1383 |
Away states |
1384 |
|
1385 |
As you might've expected, you can just use the /away command in your IRC client |
1386 |
to set an away-state. BitlBee supports most away-states supported by the |
1387 |
protocols. |
1388 |
|
1389 |
Not all away states are supported by all protocols, and some protocols have |
1390 |
different names for them. BitlBee will try to pick the best available alias |
1391 |
from this list for every connection: |
1392 |
|
1393 |
Away from computer, Away, Extended away |
1394 |
NA, N/A, Not available |
1395 |
Busy, Do not disturb, DND, Occupied |
1396 |
Be right back, BRB |
1397 |
On the phone, Phone, On phone |
1398 |
Out to lunch, Lunch, Food |
1399 |
|
1400 |
So /away Food will set your state to "Out to lunch" on your MSN connection, and |
1401 |
for most other connections the default, "Away" or "Away from computer" will be |
1402 |
chosen. |
1403 |
|
1404 |
You can also add more information to your away message. Setting it to "Busy - |
1405 |
Fixing BitlBee bugs" will set your IM-away-states to Busy, but your away |
1406 |
message will be more descriptive for people on IRC. Protocols like Yahoo! and |
1407 |
Jabber will also show this complete away message to your buddies. |
1408 |
|