Difference between revisions of "Bitlbee"

From ArchWiki
Jump to: navigation, search
(Correct link: http:// twice)
(update Pkg/AUR templates)
(Tag: wiki-scripts)
 
(35 intermediate revisions by 16 users not shown)
Line 2: Line 2:
 
[[de:Bitlbee]]
 
[[de:Bitlbee]]
 
[[es:Bitlbee]]
 
[[es:Bitlbee]]
 +
[[ja:Bitlbee]]
 
[[tr:Bitlbee]]
 
[[tr:Bitlbee]]
[http://www.bitlbee.org/main.php/news.r.html Bitlbee] is a "console-based IRC to IM chatting gateway, including ICQ/MSN/Jabber". It allows the user to interact with popular chat networks XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM 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.
+
[http://www.bitlbee.org/main.php/news.r.html Bitlbee] is a "console-based IRC to IM chatting gateway, including ICQ/MSN/Jabber". It allows the user to interact with popular chat networks XMPP/Jabber, MSN Messenger, Yahoo! Messenger, AIM 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.
 
The users' buddies appear as normal IRC users in a channel and conversations use the private message facility of IRC.
  
 
== Installation ==
 
== Installation ==
[[pacman|Install]] {{Pkg|bitlbee}}, available in the [[Official Repositories]]. Alternatively, install the development version, {{AUR|bitlbee-bzr}}, available in the [[Arch User Repository]].
+
[[Install]] the {{Pkg|bitlbee}} package. Alternatively, install the development version, {{AUR|bitlbee-git}}.
  
 
== Configuration ==
 
== Configuration ==
Line 14: Line 15:
  
 
=== Daemon ===
 
=== Daemon ===
To run Bitlbee as a daemon uncomment the Runmode line and change it to the following.
 
RunMode = ForkDaemon
 
 
 
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.
 
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
 
  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:
 
Ensure that the configuration directory is writeable with the user you configured:
 
{{bc|# chown -R bitlbee:bitlbee /var/lib/bitlbee}}
 
{{bc|# chown -R bitlbee:bitlbee /var/lib/bitlbee}}
  
Then start the {{ic|bitlbee}} daemon.
+
Then [[start]] the {{ic|bitlbee}} daemon. You can also [[enable]] the {{ic|bitlbee}} daemon to start on boot.
  systemctl start bitlbee
+
 
 +
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 {{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.
 +
 
 +
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 {{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.
 +
 
 +
==External Services==
  
You can also enable the {{ic|bitlbee}} daemon to run on startup like so:
+
===Telegram===
systemctl enable bitlbee
+
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.
  
(Note: just starting the server does not log you into any of your chat accounts)
+
Next, install {{AUR|telegram-purple}} and restart bitlbee via systemd.
  
== Connect to channel ==
+
In the control channel, {{Ic|&bitlbee}}, type the following commands:
Once Bitlbee is running connect to {{ic|localhost}} using a IRC client. Then join the channel named {{ic|&bitlbee}}. After joining the channel type {{ic|Help}} and then {{Keypress|Enter}} for further information.
+
  
== Google Chat ==
+
  11:45:03 <@user> account add telegram <phone_number_with_region_prefix> <anything>
In the control channel, {{Ic|&bitlbee}}, issue the following command after replacing {{Ic|<username>}} and {{Ic|<password>}} with your information:
+
11:45:03 <@root> Account successfully added
  <@user> account add jabber <username>@gmail.com <password> talk.google.com:5223:ssl
+
11:45:06 <@user> account telegram on
Appending the command with {{Ic|talk.google.com:5223:ssl}} is not strictly necessary, but it is recommended to enable extra security.
+
  
If you have enabled [http://code.google.com/p/google-authenticator/ Google Authenticator] make sure to create an application specific password (see: [http://www.google.com/support/accounts/bin/static.py?page=guide.cs&guide=1056283&topic=1056286 Google Accounts Help]).
+
After connecting a separate chat window will open, asking for the SMS code - enter it and Telegram will work with your setup.
  
To verify that the account was added check the account list:
+
===Twitter===
<@user> account list
+
<@root> 0. JABBER, username@gmail.com (connected)
+
<@root> End of account list
+
  
You can change the server value of your gmail account with the following command:
+
In the control channel, {{Ic|&bitlbee}}, type the following commands:
account 0 set server talk.google.com
+
  
To log into your Google account issue the following:
+
11:45:03 <@user> account add twitter <handle>
<@user> account 0 on
+
  11:45:03 <@root> Account successfully added
  <@root> JABBER(username@gmail.com) - Logging in: Connecting
+
  11:45:06 <@user> account on
  <@root> JABBER(username@gmail.com) - Logging in: Connected
+
  11:45:06 <@root> Trying to get all accounts connected...
  <@root> JABBER(username@gmail.com) - Logging in: Requesting Authentication Method
+
  11:45:06 <@root> twitter - Logging in: Requesting OAuth request token
  <@root> JABBER(username@gmail.com) - Logging in: Authenticating
+
<@root> JABBER(username@gmail.com) - Logged in
+
  
=== Troubleshooting ===
+
In a private channel, {{Ic|twitter_handle}}, you'll receive:
  
If you get errors like the following:
+
  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.
  <@user> account 0 on
+
<@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. 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/].
+
Click the link and authorize the BitlBee app on Twitter. You should now see:
  
The easiest way to change your account settings is to simply delete the account you created  and add it again.
+
  11:59:54 <@root> twitter - Logging in: Connecting to Twitter
account 0 del
+
  11:59:55 <@root> twitter - Logging in: Logged in
  account add jabber username@googlemail.com mypasswd
+
or just use the `set` switch for the `account` command
+
account list  # find the id for your gtalk account, in this case I'll use '0'
+
  account 0 set  # list all the possible settings for this account
+
account 0 set username foo@gmail.com        # change your username
+
account 0 set password somethingverysecret  # change your passphrase
+
  
 
== See Also ==
 
== See Also ==
Line 84: Line 86:
 
* [http://quark.humbug.org.au/publications/internet/bitlbee.pdf Introduction to Bitlbee] by Bradley Marshall
 
* [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://princessleia.com/bitlbee.php Quickstart Guide] by Elizabeth Krumbach
* [http://thinkhole.org/wp/2006/09/20/howto-connect-to-google-talk-with-bitlbee/ HOWTO: Connect to Google Talk with Bitlbee] at Thinkhole Labs
+
* [http://wiki.bitlbee.org/HowtoTwitter HOWTO: Connect to Twitter] on the BitlBee wiki
* [http://wiki.bitlbee.org/HowtoFacebook HOWTO: Connect to Facebook chat with Bitlee] on the Bitlbee Wiki
+
* [https://wiki.bitlbee.org/HowtoFacebookMQTT HOWTO: Connect to Facebook] on the Bitlbee Wiki

Latest revision as of 14:50, 14 October 2016

Bitlbee is a "console-based IRC to IM chatting gateway, including ICQ/MSN/Jabber". It allows the user to interact with popular chat networks XMPP/Jabber, MSN Messenger, Yahoo! Messenger, AIM 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. Alternatively, install the development version, bitlbee-gitAUR.

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