-
Notifications
You must be signed in to change notification settings - Fork 21
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
Archive import appears to be broken on recent exports #54
Comments
Correction: the failure is on |
See dogsheep#54 for discussion. This also ignores files in the new "assets" directory, which appear to be some stuff for a browser interface Twitter's created.
I was able to fix this, at least enough to get my archive to import. Not sure if there's more work to be done here or not. |
My import got much further with the applied fixes than 0.21.3, but not 100%. I do appear to have all of the tweets imported at least. Here's my output:
|
* Find data files in subdirectories in archives See #54 for discussion. This also ignores files in the new "assets" directory, which appear to be some stuff for a browser interface Twitter's created. * Fix list-member importer It appears in list data that some rows contain a `urls` key with a list of URLs, while others contain a `url` key with just a single one. This change supports either way. * Fix tweet import This was working, sorta, but wasn't properly unpacking the tweet data into columns. This commit fixes that in what I think should be a backwards-compatible way.
Similar trouble with ageinfo using 0.22. Here's what my ageinfo.js file looks like:
Commenting out the registration for ageinfo in archive.py gets my archive to import. |
as of 2023 it appears that this seems an impossible task with twitter liable to switch this around every other day |
I requested a Twitter export yesterday, and unfortunately they seem to have changed it such that
twitter-to-sqlite import
can't handle it anymore 😢So far I've ran into two issues. The first was easy to work around, but the second will take more investigation. If I can find the time I'll keep working on it and update this issue accordingly.
The issues (so far):
1. Data seems to have moved to a
data/
subdirectoryRunning
twitter-to-sqlite import
on the raw zip file reports a bunch of "not yet implemented" errors, and then exits without actually importing anything:(
tarchive.db
now exists, but is empty)Workaround: unpack the zip file, and run
twitter-to-sqlite import tarchive.db path/to/archive/data
That gets further, but:
2. Some schema(s?) have changed
At least, the
blocks
schema seems different now:That's as far as I got before I needed to work on something else. I'll report back if I get further!
The text was updated successfully, but these errors were encountered: