_________          ________ ______ _______ _____  _    _ __  __ _____  
|__   __\ \        / /  ____|  ____|__   __|  __ \| |  | |  \/  |  __ \ 
   | |   \ \  /\  / /| |__  | |__     | |  | |  | | |  | | \  / | |__) |
   | |    \ \/  \/ / |  __| |  __|    | |  | |  | | |  | | |\/| |  ___/ 
   | |     \  /\  /  | |____| |____   | |  | |__| | |__| | |  | | |     
   |_|      \/  \/   |______|______|  |_|  |_____/ \____/|_|  |_|_|     
                                                                        
                                                                                                                        
This Tweetdump is a proof of concept experiment.
It shows you don't have to let Twitter swallow up all your Tweets once they reach the incremental 3200 API limit.
If you're not backing up your Tweets, and then deleting them, you really should be doing so.

Doing so, means your fellow Tweeps can 'see' all your recent Tweets, and your Tweets are not swallowed up by the 3200 plug-hole

I scraped this data from allmytweets.net (By copying and pasting the raw Tweet data from the page)
I then escaped the Unicode with Rishida's conversion tool:

http://rishida.net/tools/conversion/

Then it was just a case of putting each tweet on a new line, delimited with ▶ (Right Arrow)
Other possible solutions to preserving your Tweet data is using a tool called Tweetnest:

http://pongsocket.com/tweetnest/