BitlBee, The only buzzword your manager doesn't know about

Latest Releases

Stable: 3.6
Download now

Git logs

Main dev tree

Replace libgcrypt-configure with pkg-config
- matt
Adjust sha1_random_uuid usage in jabber/conference.c
- Petr Vaněk
Bump GitHub actions/checkout from 3 to 4
- Robert Scheck

Public BitlBee servers

If you don't feel like installing BitlBee (for example, if it's too much work on your operating system), you can also use a public BitlBee server. There are more and more available these days. Some of them are maintained by us, some are not.

So, we're not responsible for these servers. If anybody steals your password, please don't blame us. But of course, we do trust the server owners to handle the passwords with care. After all, what's the use of stealing someone else's chat passwords ... to chat with people you don't know anyway? Also, please do not contact us if you got questions about your account or server downtime. (Unless your account is on our server, of course) We can't answer such questions, only the server owner can.

The server owners may have special rules or restrictions on their servers. We can't put them all here, so please don't forget to read the MOTDs if you want to be sure.
 The NetherlandsWilmer van der Gaast3.5.1+20170130+master+0-g262a82b-git
SSL via port 6697.
 BelgiumWilmer van der Gaast, Tom Laermans3.5.1+20170130+master+0-g262a82b-git
Usually runs experimental (but reasonably stable) code. SSL via port 6697.
 Pittsburgh, USADoug Luce3.4.2+20161018+master+75-gc94e208-git
SSL via port 6697
 The NetherlandsArnie3.4.2+20161231+master+113-g2e8523b-git
 BelgiumTom Laermans3.5.1+20170130+master+0-g262a82b-git
SSL via port 6697