<?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: New Twitter Client: Twidge</title>
	<atom:link href="http://changelog.complete.org/archives/752-new-twitter-client-twidge/feed" rel="self" type="application/rss+xml" />
	<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge</link>
	<description>Viewpoints on technology, society, and government</description>
	<lastBuildDate>Wed, 08 Sep 2010 10:34:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Ershad</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-7136</link>
		<dc:creator>Ershad</dc:creator>
		<pubDate>Thu, 02 Sep 2010 15:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-7136</guid>
		<description>Sorry for the previous comment, i would try the new twidge. Thank you.</description>
		<content:encoded><![CDATA[<p>Sorry for the previous comment, i would try the new twidge. Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Goerzen</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-7134</link>
		<dc:creator>John Goerzen</dc:creator>
		<pubDate>Thu, 02 Sep 2010 14:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-7134</guid>
		<description>Not true.  Twidge has supported OAuth since version 1.0.1, which was released back in June already.  The current version is 1.0.5 and there are instructions on the FAQ page on the wiki of how to switch.</description>
		<content:encoded><![CDATA[<p>Not true.  Twidge has supported OAuth since version 1.0.1, which was released back in June already.  The current version is 1.0.5 and there are instructions on the FAQ page on the wiki of how to switch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ershad</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-7133</link>
		<dc:creator>Ershad</dc:creator>
		<pubDate>Thu, 02 Sep 2010 14:55:47 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-7133</guid>
		<description>Twidge is no longer supporting twitter, is it because of the changed authorization method in twitter API? Could you please give support for OAuth in twidg ?</description>
		<content:encoded><![CDATA[<p>Twidge is no longer supporting twitter, is it because of the changed authorization method in twitter API? Could you please give support for OAuth in twidg ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: allyn</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-6242</link>
		<dc:creator>allyn</dc:creator>
		<pubDate>Thu, 29 Apr 2010 19:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-6242</guid>
		<description>This is a great tool! I just wanted to post to Twitter without leaving the command line while working. This suits my needs perfectly! Thank you.</description>
		<content:encoded><![CDATA[<p>This is a great tool! I just wanted to post to Twitter without leaving the command line while working. This suits my needs perfectly! Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schneider</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-5094</link>
		<dc:creator>Schneider</dc:creator>
		<pubDate>Mon, 11 Jan 2010 22:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-5094</guid>
		<description>Actually, I&#039;m looking forward to create a ruby twitter client, strongly based on twidge. But it will have fewer funcionality :(</description>
		<content:encoded><![CDATA[<p>Actually, I&#8217;m looking forward to create a ruby twitter client, strongly based on twidge. But it will have fewer funcionality :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schneider</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-4206</link>
		<dc:creator>Schneider</dc:creator>
		<pubDate>Wed, 29 Jul 2009 06:12:40 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-4206</guid>
		<description>I&#039;m already using it! :)
http://twitter.com/dudektria</description>
		<content:encoded><![CDATA[<p>I&#8217;m already using it! :)<br />
<a href="http://twitter.com/dudektria" rel="nofollow">http://twitter.com/dudektria</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Goerzen</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-2491</link>
		<dc:creator>John Goerzen</dc:creator>
		<pubDate>Sun, 14 Sep 2008 14:03:34 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-2491</guid>
		<description>Weird.  I haven&#039;t seen that.

Anyhow, there are a few things you could do.

You could edit your ~/.twidgerc and make Twidge use non-SSL communication with Twitter.  Just set urlbase = http://twitter.com.

Or, you could add the line insecure to ~/.curlrc, though that will impact more than just Twidge.

I&#039;ll add a curlrc option to the Twidge config file so you can set your own options for Twidge only.</description>
		<content:encoded><![CDATA[<p>Weird.  I haven&#8217;t seen that.</p>
<p>Anyhow, there are a few things you could do.</p>
<p>You could edit your ~/.twidgerc and make Twidge use non-SSL communication with Twitter.  Just set urlbase = <a href="http://twitter.com" rel="nofollow">http://twitter.com</a>.</p>
<p>Or, you could add the line insecure to ~/.curlrc, though that will impact more than just Twidge.</p>
<p>I&#8217;ll add a curlrc option to the Twidge config file so you can set your own options for Twidge only.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Bartlett</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-2489</link>
		<dc:creator>Neil Bartlett</dc:creator>
		<pubDate>Sun, 14 Sep 2008 11:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-2489</guid>
		<description>It doesn&#039;t work for me because curl complains about the server certificate. It looks like Twitter&#039;s SSL certificate is invalid... is there any way to pass the -k flag through to curl?</description>
		<content:encoded><![CDATA[<p>It doesn&#8217;t work for me because curl complains about the server certificate. It looks like Twitter&#8217;s SSL certificate is invalid&#8230; is there any way to pass the -k flag through to curl?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roman Lagunov</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-2478</link>
		<dc:creator>Roman Lagunov</dc:creator>
		<pubDate>Sat, 13 Sep 2008 15:37:29 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-2478</guid>
		<description>Yes! Thanks. Now twidge display cyrillic post as it should.</description>
		<content:encoded><![CDATA[<p>Yes! Thanks. Now twidge display cyrillic post as it should.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Goerzen</title>
		<link>http://changelog.complete.org/archives/752-new-twitter-client-twidge/comment-page-1#comment-2477</link>
		<dc:creator>John Goerzen</dc:creator>
		<pubDate>Sat, 13 Sep 2008 15:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/752-new-twitter-client-twidge.html#comment-2477</guid>
		<description>I&#039;ve posted 0.99.2 that I think will fix your problem.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve posted 0.99.2 that I think will fix your problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
