Tweet archiving

I’ve just noticed that Twitter allows you to export your tweets, under your account settings. They come in both human and machine-readable form. Not sure how long ago they added this, but it partially addresses one of my chief concerns about the service: that users stick many years of their lives into it without necessarily knowing that they’ll ever be able to extract the information in future.

This is not easy to automate, though, so I’m still going to keep using Archive My Tweets for my own archive.

Enjoyed this post? Why not sign up to receive Status-Q in your inbox?

2 Comments

An alternative way of dealing with this is to own your content from the beginning and syndicate it out to other services. Still using the api but to push content in rather than extract it afterwards. Downside is setting up new workflows and eschewing the 3rd-party’s apps (e.g the twitter iPhone app etc).

    Hi Amir –

    Yes, that’s probably a good idea. I sort of do that at present – most of my posts are to app.net (because I knew I could always extract from there) and then cross-posted, but increasingly I’m just doing blog posts and sending notifications to Twitter…

Got Something To Say:

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax

*

© Copyright Quentin Stafford-Fraser