<?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"
	>
<channel>
	<title>Comments on: Privacy Conundrum: Twitter Timeline Export</title>
	<atom:link href="http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/feed/" rel="self" type="application/rss+xml" />
	<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/</link>
	<description>Brad Kellett Blogs the Web, Mobile Tech, and...</description>
	<pubDate>Sun, 07 Sep 2008 16:47:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Doug</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-85730</link>
		<dc:creator>Doug</dc:creator>
		<pubDate>Sun, 03 Aug 2008 02:36:02 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-85730</guid>
		<description>Tweets are public -- I wouldn't worry. Please dump all my tweets to a CSV for me!  :)</description>
		<content:encoded><![CDATA[<p>Tweets are public &#8212; I wouldn&#8217;t worry. Please dump all my tweets to a CSV for me!  <img src='http://pantsland.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pantsland &#187; Released: Twitter Timeline Export (TweetDumpr)</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-34455</link>
		<dc:creator>Pantsland &#187; Released: Twitter Timeline Export (TweetDumpr)</dc:creator>
		<pubDate>Mon, 14 Apr 2008 06:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-34455</guid>
		<description>[...] general response to my hesitation on the release of my Twitter timeline export tool was that I should, indeed, release it. So I [...]</description>
		<content:encoded><![CDATA[<p>[...] general response to my hesitation on the release of my Twitter timeline export tool was that I should, indeed, release it. So I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-34419</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Mon, 14 Apr 2008 04:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-34419</guid>
		<description>Sweet, thanks for this!  It seems almost impossible to get your full Twitter stream exported in any useful way.

I'm actually looking to switch back to WordPress from Twitter, and was wondering...is it at all possible to have this export to RSS instead of CSV?  If that were the case, a WP install would be able to import the Twitter entries.

Am poking around with the XML/JSON exports Twitter allows as per the API, but this is way out of my league. :-/</description>
		<content:encoded><![CDATA[<p>Sweet, thanks for this!  It seems almost impossible to get your full Twitter stream exported in any useful way.</p>
<p>I&#8217;m actually looking to switch back to WordPress from Twitter, and was wondering&#8230;is it at all possible to have this export to RSS instead of CSV?  If that were the case, a WP install would be able to import the Twitter entries.</p>
<p>Am poking around with the XML/JSON exports Twitter allows as per the API, but this is way out of my league. :-/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Kellett</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-33940</link>
		<dc:creator>Brad Kellett</dc:creator>
		<pubDate>Sun, 13 Apr 2008 01:42:38 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-33940</guid>
		<description>Thanks for the opinions guys, I really appreciate them. I will be releasing a web version of the tool later today that will authenticate to Twitter before doing it's thing to only let you export your own timeline.

Those that I have spoken to believe that this is a good compromise.</description>
		<content:encoded><![CDATA[<p>Thanks for the opinions guys, I really appreciate them. I will be releasing a web version of the tool later today that will authenticate to Twitter before doing it&#8217;s thing to only let you export your own timeline.</p>
<p>Those that I have spoken to believe that this is a good compromise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-33257</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 11 Apr 2008 12:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-33257</guid>
		<description>If anything, I think it's worth publishing to highlight the lack of privacy. If anyone has any illusions of their public feed being in some vague way protected, it's important to correct that notion.</description>
		<content:encoded><![CDATA[<p>If anything, I think it&#8217;s worth publishing to highlight the lack of privacy. If anyone has any illusions of their public feed being in some vague way protected, it&#8217;s important to correct that notion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mat</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-32235</link>
		<dc:creator>Mat</dc:creator>
		<pubDate>Wed, 09 Apr 2008 12:32:08 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-32235</guid>
		<description>Anyone with privacy concerns obviously doesn't understand how the inter-tubes work - it's like getting upset because people can see your face while you walk down a street.

As already mentioned, if somebodies timeline is public already, then their timeline &lt;em&gt;has&lt;/em&gt; no privacy, nor can they have any expectation that their timeline can have any privacy.

What about their followers who receive tweets via IM, who have IM clients which log every conversation?

I say release the script if you want to, and tell anyone who complains not to publish things to the internets if they want it to be private. Personally I don't care if somebody chooses to read my tweets via the web interface, via IM, via SMS, or via a CSV on their hard drive.</description>
		<content:encoded><![CDATA[<p>Anyone with privacy concerns obviously doesn&#8217;t understand how the inter-tubes work - it&#8217;s like getting upset because people can see your face while you walk down a street.</p>
<p>As already mentioned, if somebodies timeline is public already, then their timeline <em>has</em> no privacy, nor can they have any expectation that their timeline can have any privacy.</p>
<p>What about their followers who receive tweets via IM, who have IM clients which log every conversation?</p>
<p>I say release the script if you want to, and tell anyone who complains not to publish things to the internets if they want it to be private. Personally I don&#8217;t care if somebody chooses to read my tweets via the web interface, via IM, via SMS, or via a CSV on their hard drive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Serdar Kilic</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-32143</link>
		<dc:creator>Serdar Kilic</dc:creator>
		<pubDate>Wed, 09 Apr 2008 08:16:28 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-32143</guid>
		<description>Brad, if it's already publicly available then I don't think anyone can cry foul about any privacy issues.</description>
		<content:encoded><![CDATA[<p>Brad, if it&#8217;s already publicly available then I don&#8217;t think anyone can cry foul about any privacy issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-32134</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Wed, 09 Apr 2008 08:01:11 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-32134</guid>
		<description>I understand the concerns, however a user's entire history is already cached at Google if they're public. 

In addition, a python(?) script is only going to be usable by those who already have the skill to write something like this anyway.  You're saving someone, what 20-30 minutes?  There's plenty of other things out there which will do this for you anyway, with a little prodding (wget, anyone?), but just not as cleanly.</description>
		<content:encoded><![CDATA[<p>I understand the concerns, however a user&#8217;s entire history is already cached at Google if they&#8217;re public. </p>
<p>In addition, a python(?) script is only going to be usable by those who already have the skill to write something like this anyway.  You&#8217;re saving someone, what 20-30 minutes?  There&#8217;s plenty of other things out there which will do this for you anyway, with a little prodding (wget, anyone?), but just not as cleanly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Kellett</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-32086</link>
		<dc:creator>Brad Kellett</dc:creator>
		<pubDate>Wed, 09 Apr 2008 06:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-32086</guid>
		<description>m1k3y: That's true, I could do it that way. It is a command line script at the moment, but I could make it work like that.</description>
		<content:encoded><![CDATA[<p>m1k3y: That&#8217;s true, I could do it that way. It is a command line script at the moment, but I could make it work like that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: m1k3y</title>
		<link>http://pantsland.com/2008/04/09/privacy-conundrum-twitter-timeline-export/#comment-32084</link>
		<dc:creator>m1k3y</dc:creator>
		<pubDate>Wed, 09 Apr 2008 05:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=269#comment-32084</guid>
		<description>only if you publish the script, rather than just host it with your own front-end</description>
		<content:encoded><![CDATA[<p>only if you publish the script, rather than just host it with your own front-end</p>
]]></content:encoded>
	</item>
</channel>
</rss>
