<?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: Mixero: The Tweetdeck Killer?</title>
	<atom:link href="http://www.geektechnica.com/2009/06/mixero-the-tweetdeck-killer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.geektechnica.com/2009/06/mixero-the-tweetdeck-killer/</link>
	<description>Geek Technica</description>
	<lastBuildDate>Sun, 07 Mar 2010 16:42:44 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Roman</title>
		<link>http://www.geektechnica.com/2009/06/mixero-the-tweetdeck-killer/comment-page-1/#comment-643</link>
		<dc:creator>Roman</dc:creator>
		<pubDate>Mon, 08 Jun 2009 20:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.geektechnica.com/?p=377#comment-643</guid>
		<description>I had one problem with mixero. Even after closing it (under windows) it was working on the background so when I open tweetdeck I was loosing API calls faster because they were both using it. I understand it is a beta app, thought I should point it out so that they can fix it for future versions.</description>
		<content:encoded><![CDATA[<p>I had one problem with mixero. Even after closing it (under windows) it was working on the background so when I open tweetdeck I was loosing API calls faster because they were both using it. I understand it is a beta app, thought I should point it out so that they can fix it for future versions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pavs</title>
		<link>http://www.geektechnica.com/2009/06/mixero-the-tweetdeck-killer/comment-page-1/#comment-641</link>
		<dc:creator>Pavs</dc:creator>
		<pubDate>Mon, 08 Jun 2009 16:17:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.geektechnica.com/?p=377#comment-641</guid>
		<description>Jim,
Its very light in memory for me.

When I load up tweetdeck it uses up 120+ MB from start, with Mixero it was around 70+ MB. But I think it also depend on how many windows/panels you have open at one time.</description>
		<content:encoded><![CDATA[<p>Jim,<br />
Its very light in memory for me.</p>
<p>When I load up tweetdeck it uses up 120+ MB from start, with Mixero it was around 70+ MB. But I think it also depend on how many windows/panels you have open at one time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://www.geektechnica.com/2009/06/mixero-the-tweetdeck-killer/comment-page-1/#comment-638</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Mon, 08 Jun 2009 04:13:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.geektechnica.com/?p=377#comment-638</guid>
		<description>Looks interesting. Is it a memory hog like tweetdeck? I remember tweetdeck used to have serious memory issues, I have since moved to using the web interface only. But now that I am following a lot of users I am thinking about getting a desktop client again. I will ask for a beta invite soon.</description>
		<content:encoded><![CDATA[<p>Looks interesting. Is it a memory hog like tweetdeck? I remember tweetdeck used to have serious memory issues, I have since moved to using the web interface only. But now that I am following a lot of users I am thinking about getting a desktop client again. I will ask for a beta invite soon.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
