Skip to content
This repository has been archived by the owner on Feb 28, 2023. It is now read-only.

Request: csv output #39

Open
victor-50 opened this issue Oct 13, 2017 · 2 comments
Open

Request: csv output #39

victor-50 opened this issue Oct 13, 2017 · 2 comments

Comments

@victor-50
Copy link

Hi, I just used your DMArchiver and now have 143 txt files with no indication of order or tweep. It would be of great help if you could send the output to one file in csv format: Date (ANSI) tweep name text, each conversation separated by an empty line or something like "======" .
For your information:
I got mails from Twitter that someone logged into my account. Which is fine of course.
It didn't work well in W10 outside a command prompt. But also could be the fact that it was then run from a network share.

@Mincka
Copy link
Owner

Mincka commented Oct 13, 2017

Hi,

I understand it can be a bit painful when you have a lot of conversations. If you are looking for a specific conversation, you can check this section: https://github.com/Mincka/DMArchiver#how-to-get-a-conversation_id

I used to plan to name the conversations files based on the group name or handle of the other person, but it is not always possible and it would cause issues for the incremental update with handle or group name modifications.

Still, I could make a CSV output, without incremental update support, and put the conversation (group or handle name) in one of the columns. I am not sure of the CSV parsing and display for multi-lines tweets.

Could you explained the issues you encountered? Missing tweets? Errors?

@victor-50
Copy link
Author

I don't think there were any missing tweets or errors, but of course I couldn't check thoroughly, nor do I wish to :-). This is why I presented it as a request. I guess the simplest way to tackle multiple line issues is to replace CR/LF with a semicolon or maybe the separator "|" or some other handy character.

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

No branches or pull requests

2 participants