Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Output in CSV format #20

Closed
sw17ch opened this issue Apr 25, 2012 · 7 comments
Closed

Feature Request: Output in CSV format #20

sw17ch opened this issue Apr 25, 2012 · 7 comments

Comments

@sw17ch
Copy link

sw17ch commented Apr 25, 2012

Download as much history as possible. Save someplace locally.

@sferik
Copy link
Owner

sferik commented Apr 25, 2012

I don't think t should be responsible for the "save someplace locally" part. You can just direct the output to a file using >.

However, it might be interesting to create a flag that generates output in CSV or TSV format.

Currently, the command that comes closes to what you're trying to do is:

t timeline -l -n 200 > tweets.txt

Conceivably, I could modify the command to get up to 800 statuses instead of 200 (this is the limitation imposed by Twitter), so you could do something like:

t timeline --csv -n 800 > tweets.csv

Would that solve your problem?

@sw17ch
Copy link
Author

sw17ch commented Apr 25, 2012

this would be great. i think that a raw dump of the json formatted data
from twitter would be more useful than CSV though.

On Wed, Apr 25, 2012 at 11:56 AM, Erik Michaels-Ober <
reply@reply.github.com

wrote:

I don't think t should be responsible for the "save someplace locally"
part. You can just direct the output to a file using >.

However, it might be interesting to create a flag that generates output in
CSV or TSV format.

Currently, the command that comes closes to what you're trying to do is:

t timeline -l -n 200 > tweets.txt

Conceivably, I could modify the command to get up to 800 statuses instead
of 200 (this is the limitation imposed by Twitter), so you
could do something like:

t timeline --csv -n 800 > tweets.csv

Would that solve your problem?


Reply to this email directly or view it on GitHub:
#20 (comment)

@sferik
Copy link
Owner

sferik commented Apr 25, 2012

If the raw JSON response if what you seek, you may want to try twurl: https://github.com/marcel/twurl

@sw17ch
Copy link
Author

sw17ch commented Apr 25, 2012

indeed it is. thanks! a CSV export would still be interesting though. :)

On Wed, Apr 25, 2012 at 1:34 PM, Erik Michaels-Ober <
reply@reply.github.com

wrote:

If the raw JSON response if what you seek, you may want to try twurl,
which I also work on: https://github.com/marcel/twurl


Reply to this email directly or view it on GitHub:
#20 (comment)

@sferik sferik closed this as completed Apr 26, 2012
@sw17ch
Copy link
Author

sw17ch commented May 9, 2012

Thank you.

@sferik
Copy link
Owner

sferik commented May 9, 2012

@sw17ch You may be interested in this blog post as well: http://blog.jphpsf.com/2012/05/07/backing-up-your-twitter-account-with-t/

@sw17ch
Copy link
Author

sw17ch commented May 9, 2012

yep, this is great. thank you!

On Wed, May 9, 2012 at 11:44 AM, Erik Michaels-Ober <
reply@reply.github.com

wrote:

@sw17ch You may be interested in this blog post as well:
http://blog.jphpsf.com/2012/05/07/backing-up-your-twitter-account-with-t/


Reply to this email directly or view it on GitHub:
#20 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants