Press Rouch

I started looking at this before I knew about this project. Unfortunately likes are significantly harder to process than your own tweets as they have much less metadata - here's...

@grayside That's a good idea. I don't have time to make the issue/PR at the moment but [here's a gist](https://gist.github.com/press-rouch/9bdfa006d81335d47dbe2d2cd144c460 ) with the redirect script if anyone would like to...

Progress report - I've added a get_likes script to my fork: https://github.com/press-rouch/twitter-archive-parser Note that this does not yet produce final output. However it does download all the metadata and media...

Following the coding guidelines discussed in issue #79, here's a minimal implementation to get all metadata (including the alt-text for issue #20) for a set of tweets. On my 50Mbit...

@komic The archive contains a minimal amount of data: the tweet id, the text, and a URL. I don't know what the archive contains for protected accounts. I would expect...

@komic I think that parsing likes with lookups will work fine if _your_ account is protected, but if you have liked tweets from someone else's protected account, then we won't...

@lenaschimmel I think there's a reasonable chance you might have liked a tweet that you have retweeted, quoted, or replied to, so we probably want some de-duplication between the two...

I've just made a note about getting full user data from the API (without a key!) on the followers issue: https://github.com/timhutton/twitter-archive-parser/issues/70#issuecomment-1320721365

The remote lookup is of course much slower than any local operations, therefore I would suggest that it happens as an optional preprocessing step. My suggestion is a separate remote...

twitter_guest_api is my heavily adapted version of [twitter-video-dl](https://github.com/inteoryx/twitter-video-dl) (kudos to @inteoryx) - I stuck it in a module so it wouldn't clutter the root. I believe it is reverse engineered...