You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2023. It is now read-only.
The README.md file currently says, "You may have found suggestions to use the Twitter's archive feature to do the same but Direct Messages are not included in the generated archive."
That appears to no longer be accurate. Today I downloaded my Twitter archive, and the Direct Messages are included in the following file, within the .zip archive:
data/direct-messages.js
(Note: despite the ".js" [Javascript] extension, it's actually a JSON file.)
I don't know whether or not it is always complete. I only have about 140 Direct Messages, and only a few in any one conversation. So if they're only including the most recent 200 within a conversation I would not know it.
The text was updated successfully, but these errors were encountered:
Is there a way to read the messages from direct-messages.js? In the file it has a bunch of numbers after conversation id, sender id, etc. it’s all in numbers and doesn’t show the actual messages from the direct messages and if I want to view these conversations, how do I do so? Is there somewhere I type in these conversation ids at?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The README.md file currently says, "You may have found suggestions to use the Twitter's archive feature to do the same but Direct Messages are not included in the generated archive."
That appears to no longer be accurate. Today I downloaded my Twitter archive, and the Direct Messages are included in the following file, within the .zip archive:
data/direct-messages.js
(Note: despite the ".js" [Javascript] extension, it's actually a JSON file.)
I don't know whether or not it is always complete. I only have about 140 Direct Messages, and only a few in any one conversation. So if they're only including the most recent 200 within a conversation I would not know it.
The text was updated successfully, but these errors were encountered: