BitlBee

BitlBee 3.4.2 is available for download now. This time with 128 commits from 10 contributors. Full changelog. Highlights: irc: Self-messages (messages sent by yourself from other IM clients). IRCv3.1 support and part of 3.2. Many important ... [More] groupchat related bugfixes. jabber: Carbons, see help set carbons. Removed facebook XMPP, use bitlbee-facebook instead. SASL ANONYMOUS login, see help set anonymous. hipchat: Channels can now be added with chat add hipchat "channel name" which tries to guess the channel JID. Read more skype: Show all messages as groupchats since we can't tell which ones are private. This plugin is mostly-deprecated and mostly-broken, use the skypeweb purple plugin or msn instead. purple: Fix problems remembering SSL certificates as trusted. Groupchat related fixes. Better error reporting. Fixed setting jabber away states. And lots of bugfixes / stability improvements. See the full changelog for details! As stated above, Facebook's XMPP has ceased to be, throwing auth errors for (almost?) everyone. Use bitlbee-facebook, which, btw, improved significantly after jgeboski's partipation in the pidgin GSoC. MSN and gtalk are still fine, you just have to appreciate the beauty of things that are imperfect, impermanent and incomplete. [Less]

BitlBee 3.4.1 is available for download now. This time with 86 commits from 6 contributors. Full changelog. Highlights: Upgraded MSN protocol to MSNP21, works again. Added hipchat protocol, for smoother login. Read more Gmail mail ... [More] 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 And more! Update about dying protocols: Facebook: OAuth login doesn't work anymore, password login still works, sometimes. There is now a wiki page about bitlbee-facebook, the replacement to XMPP MSN: Undead. May ask you for brains. Update to this release and use it. Google talk: Same as before. Not dying. Update: Forgot to mention: user-guide.{txt,html} are not included in the default build anymore, as part of the documentation changes. They were a 'flattened' version of the built-in help, and very few users were aware of their existence, so they are gone. The html version is now available here. Note that some parts (such as the installation section) are very outdated. This will be fixed soon™. [Less]

BitlBee 3.4 is available for download now. It's a big release, with 123 commits from 11 contributors. Full changelog. Highlights: Twitter Filter channels - Search by keyword/hashtag or a list of users. See the wiki page for more details! ... [More] Twitter: Add rawreply command, like reply but bitlbee won't add @mention. Also add favorite / fav command aliases. Twitter: Avoid showing duplicate tweets on reconnect Jabber: Fixed crashes with file transfers (they still fail at bypassing NATs, but at least they fail without crashing) Purple: Improved support for gadugadu, whatsapp and telegram. Add a 'pattern' parameter to the blist command, to filter it. The utf8_nicks setting should be more reliable now. And many more! Important: Recompiling third party plugins such as bitlbee-steam or bitlbee-facebook is required after you install this new version! And on that topic, a brief note about dying protocols: Facebook: May die on 2015-04-30. jgeboski made bitlbee-facebook in response to this. It connects through MQTT, and also supports group chats. It's not 100% stable yet, but it's usable. Google talk: Not dying. It mostly works, just no groupchats. Consider using hangups if you need those. MSN: Dead in this release. Two years after they announced it would shut down, microsoft actually retired MSNP18. See also ismsndeadyet.com. There's a work in progress branch (soon to be merged into develop) that fixes it by using MSNP21 instead. Also, the main development repository moved to github, because all the cool kids use git now. (well, actually because dx took over as a core developer) The BZR repo is still getting synced for convenience purposes The nightly APT repo still works The bug tracker and wiki will not be migrated to github However, pull requests are preferred to patches [Less]

BitlBee 3.4 is available for download now. It's a big release, with 123 commits from 11 contributors. Full changelog. Highlights: Twitter Filter channels - Search by keyword/hashtag or a list of users. See the wiki page for more details! ... [More] Twitter: Add rawreply command, like reply but bitlbee won't add @mention. Also add favorite / fav command aliases. Twitter: Avoid showing duplicate tweets on reconnect Jabber: Fixed crashes with file transfers (they still fail at bypassing NATs, but at least they fail without crashing) Purple: Improved support for gadugadu, whatsapp and telegram. Add a 'pattern' parameter to the blist command, to filter it. The utf8_nicks setting should be more reliable now. And many more! Important: Recompiling third party plugins such as bitlbee-steam or bitlbee-facebook is required after you install this new version! And on that topic, a brief note about dying protocols: Facebook: May die on 2015-04-30. jgeboski made bitlbee-facebook in response to this. It connects through MQTT, and also supports group chats. It's not 100% stable yet, but it's usable. Google talk: Not dying. It mostly works, just no groupchats. Consider using hangups if you need those. MSN: Dead in this release. Two years after they announced it would shut down, microsoft actually retired MSNP18. See also ismsndeadyet.com. There's a work in progress branch (soon to be merged into develop) that fixes it by using MSNP21 instead. Also, the main development repository moved to github, because all the cool kids use git now. (well, actually because dx took over as a core developer) The BZR repo is still getting synced for convenience purposes The nightly APT repo still works The bug tracker and wiki will not be migrated to github However, pull requests are preferred to patches [Less]

BitlBee 3.2.2 is available for download now. If you want to know what's new, just read the changelog. tl;dr: If you care about OTR, you do want this version. From now on, new versions will only be announced via the Twitter account, because really ... [More] these news posts were just a third rehashing of the changelog. dx edit: disregard that, writing announcements is fun. [Less]

BitlBee 3.2.2 is available for download now. If you want to know what's new, just read the changelog. tl;dr: If you care about OTR, you do want this version. From now on, new versions will only be announced via the Twitter account, because really ... [More] these news posts were just a third rehashing of the changelog. dx edit: disregard that, writing announcements is fun. [Less]

BitlBee 3.2.2 is available for download now. If you want to know what's new, just read the changelog. tl;dr: If you care about OTR, you do want this version. From now on, new versions will only be announced via the Twitter account, because really these news posts were just a third rehashing of the changelog.

BitlBee 3.2.1 was just released, which should fix compatibility issues with Twitter introduced by HTTP/1.0 deprecation. If you're using im.bitlbee.org or testing.bitlbee.org you shouldn't have to do anything, they're already updated.

BitlBee 3.2.1 was just released, which should fix compatibility issues with Twitter introduced by HTTP/1.0 deprecation. If you're using im.bitlbee.org or testing.bitlbee.org you shouldn't have to do anything, they're already updated.

If you're having troubles using Facebook chat with BitlBee, that's a known issue. Facebook have revoked BitlBee's API keys last night without giving any reason. All I received is two mysterious e-mails. Also, my Facebook account was disabled. But ... [More] that might have been for different reasons since I don't remember the last time I used it. TBH I'm impressed I recognised enough pictures of my contacts to be able to restore it. :> To make matters worse, in their communication to users connected to their chat from BitlBee, they say "You can contact the app admin for more information". I can assure you, I know as much as you do. I've heard rumours that a whole bunch of chat apps were disabled, not just BitlBee. No clue what's going on, but in the meantime you can switch back to password-based authentication. No clue whether it will come back. I've clicked the Appeal button so let's find out whether anyone reads what ends up there other than character device 1:3. We'll see, I'm not going to waste too much effort on it myself. Update: As always, pay attention to the date on posts like this. This problem got resolved within a day or so IIRC. [Less]