Difference between revisions of "Bitlbee"

From ArchWiki
Jump to: navigation, search
(Fix typo and correct a few grammar issues)
m (Installation: rm broken pkg link)
 
(66 intermediate revisions by 31 users not shown)
Line 1: Line 1:
[[Category:Internet and Email (English)]]
+
[[Category:Internet Relay Chat]]
[[Category:HOWTOs (English)]]
+
[[de:Bitlbee]]
 
+
[[es:Bitlbee]]
{{i18n_links_start}}
+
[[ja:Bitlbee]]
{{i18n_entry|English|Bitlbee}}
+
[https://www.bitlbee.org/main.php/news.r.html Bitlbee] is a "console-based IRC to IM chatting gateway". It allows the user to interact with popular chat networks XMPP/Jabber, Yahoo! Messenger and ICQ, the Twitter microblogging network (plus all other Twitter API compatible services like identi.ca and status.net), and social networking chat networks like Facebook and StudiVZ within their IRC client.
{{i18n_entry|Türkçe|Bitlbee (Türkçe)}}
 
{{i18n_links_end}}
 
 
 
= About =
 
 
 
[http://www.bitlbee.org/main.php/news.r.html Bitlbee] is a "console-based IRC to IM chatting gateway, including ICQ/MSN/Jabber". Basically, it allows the user to interact with popular chat networks (ICQ, MSN, Jabber, AIM, YIM) within their IRC client.
 
  
 
The users' buddies appear as normal IRC users in a channel and conversations use the private message facility of IRC.
 
The users' buddies appear as normal IRC users in a channel and conversations use the private message facility of IRC.
  
 +
== Installation ==
 +
[[Install]] the {{Pkg|bitlbee}} package.
  
= Setup =
+
== Configuration ==
 +
Various settings can be set using the {{ic|/etc/bitlbee/bitlbee.conf}} configuration file.
  
First, download and install the package using pacman:
+
=== Daemon ===
 +
It is recommended to run the Bitlbee daemon without root permission. Uncomment the following line so Bitlbee can run as the "bitlbee" user, which was created when the package was installed.
 +
User = bitlbee
  
  # pacman -S bitlbee
+
For daemon mode uncomment the following lines.
 +
  DaemonInterface = 0.0.0.0
 +
DaemonPort = 6667
  
Bitlbee can now run as a daemon of its own!  Open up {{Filename|/etc/bitlbee/bitlbee.conf}} to browse through the settings. Uncomment the Runmode line and change it to the following.
+
Ensure that the configuration directory is writeable with the user you configured:
 +
{{bc|# chown -R bitlbee:bitlbee /var/lib/bitlbee}}
  
RunMode = ForkDaemon
+
Then [[start]] the {{ic|bitlbee}} daemon. You can also [[enable]] the {{ic|bitlbee}} daemon to start on boot.
 
 
There is no need to run the bitlbee daemon as root so we should uncomment the following line so it can run as the "bitlbee" user created when the package was installed.
 
 
 
User = bitlbee
 
  
Now run
+
Note that just starting the server does not log you into any of your chat accounts.
  
/etc/rc.d/bitlbee start
+
== Basic Usage (Jabber/XMPP) ==
  
to start the Bitlbee server. Of course, add bitlbee to your DAEMONS array in {{Filename|/etc/rc.conf}} to start the server on boot.  Note that just starting the server does not log you in to any of your messenger accounts!  You must join a channel and issue commands.
+
Once Bitlbee is running connect to {{ic|localhost}} using an IRC client. The control channel, {{ic|&bitlbee}}, should already show you some basic information (if not, join it now). You can always type {{ic|help}} to get help.
  
You may also start bitlbee every time Arch Linux boots. To do so, just add the bitlbee entry in the file rc.conf as follows:
+
While in the control channel, enter
 +
help quickstart
 +
and follow the instructions
  
DAEMONS=(... alsa cups '''bitlbee''' ...)
+
Your friend might be requesting authorization to add you back, so just reply according to the control channel prompts.
  
(The three dots mean other daemons that run during bootup)
+
To initiate a chat, simply open a new IRC private window:
  
= Configuration =
+
/msg friend hello!
You are now able to connect to this in an IRC client. To connect, just connect to localhost using your favorite IRC client.
 
  
Hopefully this will connect and you should immediately join a channel called '&bitlbee'. When you join this channel it will tell to type 'Help' if you're new... type 'Help' ;)
+
=== OTR ===
  
Read through the help offered by Bitlbee to get started. There are some great guides online too:
+
For OTR support you must have {{Pkg|libotr}} installed. Upon account registration, bitlbee will generate your OTR keys, and it will use them transparently whenever you are negotiating with an OTR-capable contact.
  
http://quark.humbug.org.au/publications/internet/bitlbee.pdf
+
==External Services==
  
http://princessleia.com/bitlbee.php
+
===Telegram===
 +
To make Telegram work with bitlbee you need version compiled with libpurple support enabled - {{AUR|bitlbee-libpurple}} for example, although there are patched or development versions also available.
  
= How to connect to Jabber using your Gmail account =
+
Next, install {{AUR|telegram-purple}} and restart bitlbee via systemd.
In your control channel, do the following:
 
account add jabber username@gmail.com mypasswd
 
  
After root responds with "Account successfully added", you can check your accounts with "account list".
+
In the control channel, {{Ic|&bitlbee}}, type the following commands:
  
  <@user> account list
+
  11:45:03 <@user> account add telegram <phone_number_with_region_prefix> <anything>
  <@root> 0. JABBER, username@gmail.com (connected)
+
  11:45:03 <@root> Account successfully added
  <@root> End of account list
+
  11:45:06 <@user> account telegram on
  
Set the server value of your gmail account:
+
After connecting a separate chat window will open, asking for the SMS code - enter it and Telegram will work with your setup.
account 0 set server talk.google.com
 
  
After you have added the account, type "account 0 on" and it should log in:
+
===Twitter===
  
<@user> account 0 on
+
In the control channel, {{Ic|&bitlbee}}, type the following commands:
<@root> JABBER(username@gmail.com) - Logging in: Connecting
 
<@root> JABBER(username@gmail.com) - Logging in: Connected
 
<@root> JABBER(username@gmail.com) - Logging in: Requesting Authentication Method
 
<@root> JABBER(username@gmail.com) - Logging in: Authenticating
 
<@root> JABBER(username@gmail.com) - Logged in
 
  
If you get errors like the following:
+
11:45:03 <@user> account add twitter <handle>
 +
11:45:03 <@root> Account successfully added
 +
11:45:06 <@user> account on
 +
11:45:06 <@root> Trying to get all accounts connected...
 +
11:45:06 <@root> twitter - Logging in: Requesting OAuth request token
  
<@user> account 0 on
+
In a private channel, {{Ic|twitter_handle}}, you'll receive:
<@root> JABBER(username@gmail.com) - Logging in: Connecting
 
<@root> JABBER(username@gmail.com) - Logging in: Connected
 
<@root> JABBER(username@gmail.com) - Logging in: Requesting Authentication Method
 
<@root> JABBER(username@gmail.com) - Logging in: Authenticating
 
<@root> JABBER(username@gmail.com) - Login error: Error 403: Unknown error
 
<@root> JABBER(username@gmail.com) - Signing off...
 
  
Switching the domain from "gmail.com" to "googlemail.com" may help.
+
11:45:07 <twitter_handle> To finish OAuth authentication, please visit http://api.twitter.com/oauth/authorize?oauth_token=xxxxxxxxx and respond with the resulting PIN code.
This seems to be the case for some European countries, especially Germany where Google doesn't own the trademark for the name ''Gmail'' [http://www.theregister.co.uk/2007/01/31/google_looses_trademark_battle/].
 
  
The easiest way to change your account settings is to simply delete the account you created  and add it again.
+
Click the link and authorize the BitlBee app on Twitter. You should now see:
account 0 del
 
account add jabber username@googlemail.com mypasswd
 
  
If you are still unable to connect, try switching the port to 5222. For some reason some people must connect on 5223 while others have to connect on 5222. There appears to be no way to know which one to use other than trial and error.
+
11:59:54 <@root> twitter - Logging in: Connecting to Twitter
 +
  11:59:55 <@root> twitter - Logging in: Logged in
  
= See Also =
+
== See Also ==
[[Screen Irssi Bitlbee]]
+
* [[Screen Irssi Bitlbee]]
 +
* [http://wiki.bitlbee.org/ Bitlbee Wiki]
 +
* [http://quark.humbug.org.au/publications/internet/bitlbee.pdf Introduction to Bitlbee] by Bradley Marshall
 +
* [http://princessleia.com/bitlbee.php Quickstart Guide] by Elizabeth Krumbach
 +
* [http://wiki.bitlbee.org/HowtoTwitter HOWTO: Connect to Twitter] on the BitlBee wiki
 +
* [https://wiki.bitlbee.org/HowtoFacebookMQTT HOWTO: Connect to Facebook] on the Bitlbee Wiki

Latest revision as of 18:12, 23 February 2018

Bitlbee is a "console-based IRC to IM chatting gateway". It allows the user to interact with popular chat networks XMPP/Jabber, Yahoo! Messenger and ICQ, the Twitter microblogging network (plus all other Twitter API compatible services like identi.ca and status.net), and social networking chat networks like Facebook and StudiVZ within their IRC client.

The users' buddies appear as normal IRC users in a channel and conversations use the private message facility of IRC.

Installation

Install the bitlbee package.

Configuration

Various settings can be set using the /etc/bitlbee/bitlbee.conf configuration file.

Daemon

It is recommended to run the Bitlbee daemon without root permission. Uncomment the following line so Bitlbee can run as the "bitlbee" user, which was created when the package was installed.

User = bitlbee

For daemon mode uncomment the following lines.

DaemonInterface = 0.0.0.0
DaemonPort = 6667

Ensure that the configuration directory is writeable with the user you configured:

# chown -R bitlbee:bitlbee /var/lib/bitlbee

Then start the bitlbee daemon. You can also enable the bitlbee daemon to start on boot.

Note that just starting the server does not log you into any of your chat accounts.

Basic Usage (Jabber/XMPP)

Once Bitlbee is running connect to localhost using an IRC client. The control channel, &bitlbee, should already show you some basic information (if not, join it now). You can always type help to get help.

While in the control channel, enter

help quickstart

and follow the instructions

Your friend might be requesting authorization to add you back, so just reply according to the control channel prompts.

To initiate a chat, simply open a new IRC private window:

/msg friend hello!

OTR

For OTR support you must have libotr installed. Upon account registration, bitlbee will generate your OTR keys, and it will use them transparently whenever you are negotiating with an OTR-capable contact.

External Services

Telegram

To make Telegram work with bitlbee you need version compiled with libpurple support enabled - bitlbee-libpurpleAUR for example, although there are patched or development versions also available.

Next, install telegram-purpleAUR and restart bitlbee via systemd.

In the control channel, &bitlbee, type the following commands:

11:45:03 <@user> account add telegram <phone_number_with_region_prefix> <anything>
11:45:03 <@root> Account successfully added
11:45:06 <@user> account telegram on

After connecting a separate chat window will open, asking for the SMS code - enter it and Telegram will work with your setup.

Twitter

In the control channel, &bitlbee, type the following commands:

11:45:03 <@user> account add twitter <handle>
11:45:03 <@root> Account successfully added
11:45:06 <@user> account on
11:45:06 <@root> Trying to get all accounts connected...
11:45:06 <@root> twitter - Logging in: Requesting OAuth request token

In a private channel, twitter_handle, you'll receive:

11:45:07 <twitter_handle> To finish OAuth authentication, please visit http://api.twitter.com/oauth/authorize?oauth_token=xxxxxxxxx and respond with the resulting PIN code.

Click the link and authorize the BitlBee app on Twitter. You should now see:

11:59:54 <@root> twitter - Logging in: Connecting to Twitter
11:59:55 <@root> twitter - Logging in: Logged in

See Also