<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using BitlBee to consolidate instant messaging into one client</title>
	<atom:link href="http://linsec.ca/blog/2009/11/08/using-bitlbee-to-consolidate-instant-messaging-into-one-client/feed/" rel="self" type="application/rss+xml" />
	<link>http://linsec.ca/blog/2009/11/08/using-bitlbee-to-consolidate-instant-messaging-into-one-client/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=using-bitlbee-to-consolidate-instant-messaging-into-one-client</link>
	<description>You can have it right, or you can have it now.  But you can&#039;t have it right now.</description>
	<lastBuildDate>Tue, 22 May 2012 12:03:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Wilmer</title>
		<link>http://linsec.ca/blog/2009/11/08/using-bitlbee-to-consolidate-instant-messaging-into-one-client/comment-page-1/#comment-4510</link>
		<dc:creator>Wilmer</dc:creator>
		<pubDate>Thu, 19 Nov 2009 10:32:20 +0000</pubDate>
		<guid isPermaLink="false">http://linsec.ca/blog/?p=621#comment-4510</guid>
		<description>Michael, what you&#039;re saying was true back in 2004 but not anymore, except for OSCAR all IM modules in BitlBee were replaced/rewritten years ago. Having said that, features that have no purpose in a text-based client *are* missing (like usericons). But the XMPP module supports everything required by RFC3920/3921 and the most important XEPs.

vdanen, feel free to report your minor issues in #bitlbee or on the bug tracker.</description>
		<content:encoded><![CDATA[<p>Michael, what you&#8217;re saying was true back in 2004 but not anymore, except for OSCAR all IM modules in BitlBee were replaced/rewritten years ago. Having said that, features that have no purpose in a text-based client *are* missing (like usericons). But the XMPP module supports everything required by RFC3920/3921 and the most important XEPs.</p>
<p>vdanen, feel free to report your minor issues in #bitlbee or on the bug tracker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vdanen</title>
		<link>http://linsec.ca/blog/2009/11/08/using-bitlbee-to-consolidate-instant-messaging-into-one-client/comment-page-1/#comment-4480</link>
		<dc:creator>vdanen</dc:creator>
		<pubDate>Mon, 09 Nov 2009 04:13:43 +0000</pubDate>
		<guid isPermaLink="false">http://linsec.ca/blog/?p=621#comment-4480</guid>
		<description>Very cool, thanks!  I&#039;m going to have to check that out and see if that solves some of the (relatively minor) issues I&#039;ve had with BitlBee.</description>
		<content:encoded><![CDATA[<p>Very cool, thanks!  I&#8217;m going to have to check that out and see if that solves some of the (relatively minor) issues I&#8217;ve had with BitlBee.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://linsec.ca/blog/2009/11/08/using-bitlbee-to-consolidate-instant-messaging-into-one-client/comment-page-1/#comment-4477</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 09 Nov 2009 00:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://linsec.ca/blog/?p=621#comment-4477</guid>
		<description>You should take a look at minbif ( http://symlink.me/wiki/minbif ), based on libpurple. Bitlbee is quite nice but it is based on old version of the pidgin library, and it forked years ago. So you end up without new jabber features, among others.</description>
		<content:encoded><![CDATA[<p>You should take a look at minbif ( <a href="http://symlink.me/wiki/minbif" rel="nofollow">http://symlink.me/wiki/minbif</a> ), based on libpurple. Bitlbee is quite nice but it is based on old version of the pidgin library, and it forked years ago. So you end up without new jabber features, among others.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

