This is a tricky one, because even if the users 'own' the content, it is stored on servers owned by Twitter. I doubt they are under any obligation to allow a third party tool to scrape a users posts from their servers.
On the other hand, Twitter should make all of a users content available as a single download. A simple css file would be sufficient, and then GETTER could just write a script to import it from the file.
This is a tricky one, because even if the users 'own' the content, it is stored on servers owned by Twitter. I doubt they are under any obligation to allow a third party tool to scrape a users posts from their servers.
On the other hand, Twitter should make all of a users content available as a single download. A simple css file would be sufficient, and then GETTER could just write a script to import it from the file.