<?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: twibble mobile 0.9.8</title>
	<atom:link href="http://www.twibble.de/2009/04/18/twibble-mobile-096/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/</link>
	<description>a location aware twitter client for Mac OS, Windows, Mobile</description>
	<lastBuildDate>Sat, 31 Jul 2010 07:12:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Bjoern</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-2/#comment-7385</link>
		<dc:creator>Bjoern</dc:creator>
		<pubDate>Wed, 04 Nov 2009 20:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-7385</guid>
		<description>hi,
ich bin im Besitz eines se w850i. Allerneueste Firmware, Java etc.
Wenn ich einen tweet senden möchte, bekomme ich dir Meldung:
&quot;ooops, couldnt read from socket&quot;. Das steht dann natürlich auch im Log vom updateworker. mit https bekomme ich ein &quot;not authorized&quot;.
Was kann ich tun, was mache ich falsch?! Damit ich von meinem javaenabelden phone twittern kann.</description>
		<content:encoded><![CDATA[<p>hi,<br />
ich bin im Besitz eines se w850i. Allerneueste Firmware, Java etc.<br />
Wenn ich einen tweet senden möchte, bekomme ich dir Meldung:<br />
&#8220;ooops, couldnt read from socket&#8221;. Das steht dann natürlich auch im Log vom updateworker. mit https bekomme ich ein &#8220;not authorized&#8221;.<br />
Was kann ich tun, was mache ich falsch?! Damit ich von meinem javaenabelden phone twittern kann.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: meep</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-1/#comment-6046</link>
		<dc:creator>meep</dc:creator>
		<pubDate>Fri, 19 Jun 2009 09:51:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-6046</guid>
		<description>while loading twibble there is an response error, while sending a tweet there comes the message &quot;Ooops...response empty&quot;....where is the failure?</description>
		<content:encoded><![CDATA[<p>while loading twibble there is an response error, while sending a tweet there comes the message &#8220;Ooops&#8230;response empty&#8221;&#8230;.where is the failure?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thilo</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-1/#comment-4888</link>
		<dc:creator>thilo</dc:creator>
		<pubDate>Sun, 26 Apr 2009 20:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-4888</guid>
		<description>@Martin Campbell thx again! Will be in the next version! In tweet lists &#039;down&#039; will fetch older tweets. menus will cycle. And twitpic will be back in addition to moby.</description>
		<content:encoded><![CDATA[<p>@Martin Campbell thx again! Will be in the next version! In tweet lists &#8216;down&#8217; will fetch older tweets. menus will cycle. And twitpic will be back in addition to moby.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Campbell</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-1/#comment-4848</link>
		<dc:creator>Martin Campbell</dc:creator>
		<pubDate>Sat, 25 Apr 2009 14:44:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-4848</guid>
		<description>Been using 0.9.8 on my SE w910i and SE W595 for a week now. Very stable. The new twibble mobile rocks!

Feature request - wraparound scrolling everywhere. Up from top jumps to bottom. Down from bottom jumps to top. Can you implement this in tweets, replies, dms and menus?</description>
		<content:encoded><![CDATA[<p>Been using 0.9.8 on my SE w910i and SE W595 for a week now. Very stable. The new twibble mobile rocks!</p>
<p>Feature request &#8211; wraparound scrolling everywhere. Up from top jumps to bottom. Down from bottom jumps to top. Can you implement this in tweets, replies, dms and menus?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @roomaroo</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-1/#comment-4836</link>
		<dc:creator>@roomaroo</dc:creator>
		<pubDate>Sat, 25 Apr 2009 07:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-4836</guid>
		<description>I&#039;m getting the same issue as @lox333 on my Nokia N78. Tweets load when twibble starts, but there&#039;s no way to refresh without restarting the program.

Looks nice though!</description>
		<content:encoded><![CDATA[<p>I&#8217;m getting the same issue as @lox333 on my Nokia N78. Tweets load when twibble starts, but there&#8217;s no way to refresh without restarting the program.</p>
<p>Looks nice though!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CLU883R</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-1/#comment-4818</link>
		<dc:creator>CLU883R</dc:creator>
		<pubDate>Fri, 24 Apr 2009 09:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-4818</guid>
		<description>why the hell my pics are on mobypicture instead of twitpic since the upgrade ? why the left and right arrows are giving the replies and DMS ? where can I donwnload the older version ?</description>
		<content:encoded><![CDATA[<p>why the hell my pics are on mobypicture instead of twitpic since the upgrade ? why the left and right arrows are giving the replies and DMS ? where can I donwnload the older version ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fernando</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-1/#comment-4804</link>
		<dc:creator>Fernando</dc:creator>
		<pubDate>Thu, 23 Apr 2009 22:50:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-4804</guid>
		<description>If there is a link on a tweet, it should be easier to access it. Right now, you must click on the tweet, scroll all the way down to &quot;open in browser&quot;, open yet another menu, and the option you want (to open the link) is the last one. This should be simpler.</description>
		<content:encoded><![CDATA[<p>If there is a link on a tweet, it should be easier to access it. Right now, you must click on the tweet, scroll all the way down to &#8220;open in browser&#8221;, open yet another menu, and the option you want (to open the link) is the last one. This should be simpler.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 182fans</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-1/#comment-4799</link>
		<dc:creator>182fans</dc:creator>
		<pubDate>Thu, 23 Apr 2009 18:40:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-4799</guid>
		<description>Hey, nice new version of twibble! I often use it, very good programm. But I was wondering why the pictures now get uploaded on mobypicture instead of twitpic? is there any way to change this?

Cheers,

182fans</description>
		<content:encoded><![CDATA[<p>Hey, nice new version of twibble! I often use it, very good programm. But I was wondering why the pictures now get uploaded on mobypicture instead of twitpic? is there any way to change this?</p>
<p>Cheers,</p>
<p>182fans</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alister</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-1/#comment-4770</link>
		<dc:creator>Alister</dc:creator>
		<pubDate>Wed, 22 Apr 2009 23:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-4770</guid>
		<description>Twibble now seems to be broken since the update.  Since installing the latest update, I can now only open it once.  If I close twibble, it will not open again until I reinstall the app.  I have tried restarting the phone several times with no success.

I have reinstalled twibble from the website 3 times now, and still cannot use it reliably.  I should mention that when twibble is working (and this is the only issue I have had with it) it is my favourite twitter client.  Cheers, Alister</description>
		<content:encoded><![CDATA[<p>Twibble now seems to be broken since the update.  Since installing the latest update, I can now only open it once.  If I close twibble, it will not open again until I reinstall the app.  I have tried restarting the phone several times with no success.</p>
<p>I have reinstalled twibble from the website 3 times now, and still cannot use it reliably.  I should mention that when twibble is working (and this is the only issue I have had with it) it is my favourite twitter client.  Cheers, Alister</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AJ</title>
		<link>http://www.twibble.de/2009/04/18/twibble-mobile-096/comment-page-1/#comment-4769</link>
		<dc:creator>AJ</dc:creator>
		<pubDate>Wed, 22 Apr 2009 22:30:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.twibble.de/?p=326#comment-4769</guid>
		<description>Is there anyway to have twibble NOT use a BES connection? When attempting with SSL turned off, I get an &quot;invalid uname/pwd&quot; error.  The log says it was unable to connect.  With SSL on, I get &quot;Rate limit exceeded&quot; with a matching error in the log.  It seems like the app is trying to use my BES connection (which blocks access to Twitter) instead of the carrier TCP/IP connection (which is wide open).  TwitterBerry had an option to select what connection to use, and I was wondering if there was any way to get a similar option in twibble.</description>
		<content:encoded><![CDATA[<p>Is there anyway to have twibble NOT use a BES connection? When attempting with SSL turned off, I get an &#8220;invalid uname/pwd&#8221; error.  The log says it was unable to connect.  With SSL on, I get &#8220;Rate limit exceeded&#8221; with a matching error in the log.  It seems like the app is trying to use my BES connection (which blocks access to Twitter) instead of the carrier TCP/IP connection (which is wide open).  TwitterBerry had an option to select what connection to use, and I was wondering if there was any way to get a similar option in twibble.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
