-
Website
http://bradkellett.com/ -
Original page
http://bradkellett.com/p/released-twitter-timeline-export-tweetdumpr/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Paul Irish
1 comment · 2 points
-
Armand
1 comment · 1 points
-
snipergirl
1 comment · 2 points
-
phrenologist
1 comment · 1 points
-
tamaracks
2 comments · 1 points
-
-
Popular Threads
Thom: Are you serious? For a start, basically every Twitter application asks for your password. Most of them store it, TweetDumpr does not. Not only that, TweetDumpr does not actually use your password for anything locally - it just sends it to Twitter, and Twitter sends back if it is correct or not. Ever used Twitter Karma, Twhirl, or any other app built on Twitter?
Authenticating against some random site specified in a users stream is of limited use, and more likely to cause more security concerns the current approach.
If you really don't want to hand your password over to third party sites - just use wget or a similar tool to mirror your Twitter account.
@Will, I know they don't have open id, I was suggesting that the site linked from their profile may have open id and could be used to prove that users authority over that twitter stream. Not a random site from their stream. The other option I suggested was that TweetDumpr generates a unique code that the person tweets, and it can then be verified and tie that twitter account to a TweetDumper account, this is the method used by technorati to prove ownership of a blog (also similar to google webmaster tools and many more).
I appreciate it's a load of work and I don't honestly expect you to implement it, but I felt I needed to draw yours and your readers attention to the problem.
* freudian slip : i mean, a word.
Unfortunately, I was hoping it would go back in time further than 10 pages (200 tweets), but it looks like that's all twitter makes available. I wonder why they would make such a frivolous decision, but that's for another forum.
Thanks!
If someone using Twitter doesn't want his/hers tweets to be public, he/she has the option to make his/hers account private and prevent public access to his/hers timeline. This need not really be of any concern to a tool like this.
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.
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_c...
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?
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.