<?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: Released: Twitter Timeline Export (TweetDumpr)</title>
	<atom:link href="http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/feed/" rel="self" type="application/rss+xml" />
	<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/</link>
	<description>Brad Kellett Blogs the Web, Mobile Tech, and...</description>
	<pubDate>Thu, 20 Nov 2008 11:29:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Adam Franco</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-104714</link>
		<dc:creator>Adam Franco</dc:creator>
		<pubDate>Mon, 13 Oct 2008 16:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-104714</guid>
		<description>Using the script I mentioned I was able to retrieve all 34 pages of my Tweets. Maybe HTML scraping the twitter site is the only place where the page limitation exists...</description>
		<content:encoded><![CDATA[<p>Using the script I mentioned I was able to retrieve all 34 pages of my Tweets. Maybe HTML scraping the twitter site is the only place where the page limitation exists&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Franco</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-104713</link>
		<dc:creator>Adam Franco</dc:creator>
		<pubDate>Mon, 13 Oct 2008 16:11:14 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-104713</guid>
		<description>Oops, I guess you are already doing this. My bad. :-)</description>
		<content:encoded><![CDATA[<p>Oops, I guess you are already doing this. My bad. <img src='http://pantsland.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Franco</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-104712</link>
		<dc:creator>Adam Franco</dc:creator>
		<pubDate>Mon, 13 Oct 2008 16:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-104712</guid>
		<description>Hi Brad,

Just wanted to let you know that you can access more than 200 Tweets if you load them by page. I've posted a small export script here that shows how to do this:
http://www.adamfranco.com/archives/88

For now this script just dumps the raw XML and is not set up as an end-user service, but it can be copied and run by anyone who wants to back up all of their time-line.</description>
		<content:encoded><![CDATA[<p>Hi Brad,</p>
<p>Just wanted to let you know that you can access more than 200 Tweets if you load them by page. I&#8217;ve posted a small export script here that shows how to do this:<br />
<a href="http://www.adamfranco.com/archives/88" rel="nofollow">http://www.adamfranco.com/archives/88</a></p>
<p>For now this script just dumps the raw XML and is not set up as an end-user service, but it can be copied and run by anyone who wants to back up all of their time-line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Franco.com &#187; Blog Archive &#187; Twitter Export Script</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-104710</link>
		<dc:creator>Adam Franco.com &#187; Blog Archive &#187; Twitter Export Script</dc:creator>
		<pubDate>Mon, 13 Oct 2008 15:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-104710</guid>
		<description>[...] doings and wished to export my time-line for reformatting into a calender format. Unfortunately TweetDumpr just retrieves the list of Tweets using a single fetch request which is limited by the Twitter API [...]</description>
		<content:encoded><![CDATA[<p>[...] doings and wished to export my time-line for reformatting into a calender format. Unfortunately TweetDumpr just retrieves the list of Tweets using a single fetch request which is limited by the Twitter API [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morten Blaabjerg</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-97528</link>
		<dc:creator>Morten Blaabjerg</dc:creator>
		<pubDate>Fri, 05 Sep 2008 20:05:49 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-97528</guid>
		<description>I think I've now waited about 30 mins at least for an email to arrive, especially since the TweetDumpr page says it ought to take just 10 mins to dump a five figure timeline. My timeline is not nearly as big, and yet still no response after half an hour or more. How long should I expect to wait to get an email response?</description>
		<content:encoded><![CDATA[<p>I think I&#8217;ve now waited about 30 mins at least for an email to arrive, especially since the TweetDumpr page says it ought to take just 10 mins to dump a five figure timeline. My timeline is not nearly as big, and yet still no response after half an hour or more. How long should I expect to wait to get an email response?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morten Blaabjerg</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-97522</link>
		<dc:creator>Morten Blaabjerg</dc:creator>
		<pubDate>Fri, 05 Sep 2008 19:51:56 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-97522</guid>
		<description>Well, now you have the sentiments of another (perhaps former) member of the Twitter user base ;-)</description>
		<content:encoded><![CDATA[<p>Well, now you have the sentiments of another (perhaps former) member of the Twitter user base <img src='http://pantsland.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Kellett</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-97521</link>
		<dc:creator>Brad Kellett</dc:creator>
		<pubDate>Fri, 05 Sep 2008 19:48:31 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-97521</guid>
		<description>To be clear, I have no privacy concerns. To me, what is public is public. I put in the password requirement based on feedback from many other Twitter users. I am trying to respect the Twitter user base and respond to their concerns.</description>
		<content:encoded><![CDATA[<p>To be clear, I have no privacy concerns. To me, what is public is public. I put in the password requirement based on feedback from many other Twitter users. I am trying to respect the Twitter user base and respond to their concerns.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morten Blaabjerg</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-97520</link>
		<dc:creator>Morten Blaabjerg</dc:creator>
		<pubDate>Fri, 05 Sep 2008 19:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-97520</guid>
		<description>Well, for one thing it raises my suspicions when a web tool such as yours asks for my account details as well as my email adress for something which is basically public data. There's no real reason for this.

What people use Twitter for or would or would not like others to do with their data does not concern me. If you don't like someone accessing something you post in public, it's really easy not to post it in public, if it means a lot to you.

What concerns me is the usability of the tools I have at hand - what they can do for me. And when you superimpose privacy concerns into what is basically mining public data, you get in my way, even if you want to help me. Great, your tool helps me export my own stuff, which is of high priority to myself right now. I'm happy you put your tool out here, and I found it.

But it makes your own tool less useful, because you think people shouldn't use it in ways you think violates your privacy concerns. Twitter is, in fact, a great way to analyze markets, if you can access all that data buried in it's archives. I wonder if you can see what kind of value your tool may have, if you can develop and make it accessible in ways which makes it easy for users to use your tool for such purposes. But right now you're blinded (as I see it) by privacy concerns for something which is completely publically accessible. And if you don't create a tool which allows for versatile mining of this data, others will. In fact, I am surprised that Twitter do not seem to see this very clearly. If they do, why would they impose obscure, randomly picked hard limits on our accessibility to the gold in our own archives?</description>
		<content:encoded><![CDATA[<p>Well, for one thing it raises my suspicions when a web tool such as yours asks for my account details as well as my email adress for something which is basically public data. There&#8217;s no real reason for this.</p>
<p>What people use Twitter for or would or would not like others to do with their data does not concern me. If you don&#8217;t like someone accessing something you post in public, it&#8217;s really easy not to post it in public, if it means a lot to you.</p>
<p>What concerns me is the usability of the tools I have at hand - what they can do for me. And when you superimpose privacy concerns into what is basically mining public data, you get in my way, even if you want to help me. Great, your tool helps me export my own stuff, which is of high priority to myself right now. I&#8217;m happy you put your tool out here, and I found it.</p>
<p>But it makes your own tool less useful, because you think people shouldn&#8217;t use it in ways you think violates your privacy concerns. Twitter is, in fact, a great way to analyze markets, if you can access all that data buried in it&#8217;s archives. I wonder if you can see what kind of value your tool may have, if you can develop and make it accessible in ways which makes it easy for users to use your tool for such purposes. But right now you&#8217;re blinded (as I see it) by privacy concerns for something which is completely publically accessible. And if you don&#8217;t create a tool which allows for versatile mining of this data, others will. In fact, I am surprised that Twitter do not seem to see this very clearly. If they do, why would they impose obscure, randomly picked hard limits on our accessibility to the gold in our own archives?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morten Blaabjerg</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-97516</link>
		<dc:creator>Morten Blaabjerg</dc:creator>
		<pubDate>Fri, 05 Sep 2008 19:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-97516</guid>
		<description>Btw, the 200-tweet archive limit is no longer enforced by Twitter (apparently). My personal archive of Tweets have been released from it's unwilling hostage status on Twitter's servers, and I am grateful of a tool such as yours which allow me to retrieve ALL my data from Twitter, in whatever form possible, to prevent this from happening again.

See this thread on more about the archives inaccessibility problems many users have experienced and on Biz Stone's "lifting" of this severe limitation of Twitter : http://getsatisfaction.com/twitter/topics/why_cant_i_view_all_of_my_updates?</description>
		<content:encoded><![CDATA[<p>Btw, the 200-tweet archive limit is no longer enforced by Twitter (apparently). My personal archive of Tweets have been released from it&#8217;s unwilling hostage status on Twitter&#8217;s servers, and I am grateful of a tool such as yours which allow me to retrieve ALL my data from Twitter, in whatever form possible, to prevent this from happening again.</p>
<p>See this thread on more about the archives inaccessibility problems many users have experienced and on Biz Stone&#8217;s &#8220;lifting&#8221; of this severe limitation of Twitter : <a href="http://getsatisfaction.com/twitter/topics/why_cant_i_view_all_of_my_updates?" rel="nofollow">http://getsatisfaction.com/twitter/topics/why_cant_i_view_all_of_my_updates?</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Kellett</title>
		<link>http://pantsland.com/2008/04/14/released-twitter-timeline-export-tweetdumpr/#comment-97515</link>
		<dc:creator>Brad Kellett</dc:creator>
		<pubDate>Fri, 05 Sep 2008 19:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://pantsland.com/?p=271#comment-97515</guid>
		<description>I don't personally have concerns over it, but the Twitter users I talked to had an issue with making it so easy to mine that data. I think there is a difference to people between posting something publicly and making it really easy to get a full archive to use however.

To me, they are the same thing, but people don't necessarily see posting to Twitter in public as the same as posting downloadable text.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t personally have concerns over it, but the Twitter users I talked to had an issue with making it so easy to mine that data. I think there is a difference to people between posting something publicly and making it really easy to get a full archive to use however.</p>
<p>To me, they are the same thing, but people don&#8217;t necessarily see posting to Twitter in public as the same as posting downloadable text.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
