BitlBee 3.4.1 freeware
BitlBee brings IM (instant messaging) to IRC clients. It's a great solution for people who have an IRC client running all the time and don't want to run an additional MSN/AIM/whatever client.
BitlBee currently supports the following IM networks/protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.
Author | Wilmer van der Gaast |
Released | 2015-06-16 |
Filesize | 686 kB |
Downloads | 1264 |
OS | Windows 2000, Windows 2003, Windows XP, Windows Vista, Windows 7, Linux, Mac OS X |
Installation | Instal And Uninstall |
Keywords | irc chat, irc client, irc gateway, irc, chat, client, Bitl Bee |
Users' rating (25 rating) |
BitlBee Free Download - we do not host any BitlBee torrent files or links of BitlBee on rapidshare.com, depositfiles.com, megaupload.com etc. All BitlBee download links are direct BitlBee download from publisher site or their selected mirrors.
3.4.1 | Jun 16, 2015 | New Release | Upgraded MSN protocol to MSNP21, works again. Added hipchat protocol, for smoother login. Gmail mail notifications support Twitter: Support for quoted tweets (shows them inline). Added url command, can be used to quote tweets Building documentation is now done with a python script (both 2.x/3.x work). Asciidoc/xsltproc/xmlto are no longer build dependencies |
3.2 | Jan 6, 2013 | New Release | * Updated Twitter module. Support for Twitter API 1.1, streaming API, direct messages and some other improvements. * Fixed potential connection issue to Google Talk, OpenFire, possibly other Jabber services. * A bunch of other things. |
3.0.5 | Feb 18, 2012 | New Release | SSL certificate verification (edit your bitlbee.conf to enable it). Works only with GnuTLS! OAuth2 support in Jabber module (works with Google Talk, Facebook and MSN Messenger). Support for ad-hoc Jabber groupchats. Just create a channel and start inviting people, similar to how this works on other IM networks. Works fine with GTalk, depends on a conference server being set up on other networks. Allow old-style Jabber login (non-SASL), this solves problems with some old/buggy Jabber servers. (acc jabber set sasl off) Use HTTPS for OAuth1 authentication traffic. Awareness of Twitter's t.co URL lengt^Wshortening when checking message length. Fixed identi.ca OAuth support. OAuth will now always be used for both Twitter and identi.ca accounts. Fix nick_format=%full_name with libpurple. Instead of "protocol(handle)", use the account tags introduced in 3.0 |