Importing tweets to Micro.blog: manton.org
@manton awesome, thanks! Since it is separate from the main micro.blog I’m assuming there is no issues with those that have been cross-posting from here to Twitter for years, right?
@bbohling Yep, that’s fine. It doesn’t attempt to figure out which tweets started as blog posts either.
@manton Splendid, Manton. Just Splendid.
@manton Fantastic. Trying it now. Does it matter if I don’t have the original zip file but rather the unzipped folder? My Twitter account no longer exists so I can’t redownload the archive.
@pratik That’s fine as long as the format for the archive matches the new archives from Twitter. If it’s years old, Twitter may have changed the format, so I’m not sure.
@manton Ok. I just zipped it back up and tried the import. It didn’t throw any errors but don’t see anything yet 🤞🏽
@manton While I have no use for this new feature, I marvel at what you have created. Incredible!
@manton Oh well, it didn’t work. It did not throw up an error, but it created the other blog as it should, but it shows zero posts.
@pratik Must be a different format. I’ll add some checks for that. Do you want to send me a screenshot or description of what the files/folders inside the .zip look like?
@crossingthethreshold @manton share the sentiment. Clever workaround. Zero interest in any of it. Can’t complain, we got AI transcripts for podcasts and the archive link feature (which is excellent).
I am due a what I’d like to see in Micro.blog type post…(spoiler: more Twitter features won’t feature in this).
@manton I have Twitter archives circa 2021, 2019, 2017, 2014, and maybe earlier and the format definitely changed a few times over that period. The bulk of my tweets (2007-2014) are in one of these older formats, and that’s what I’d love to import. Thanks anyway & always.
@manton This is awesome! I’ve been holding out, hoping I’d be able to bring across my archive at some point. Thanks for making it so easy!
@supremus No, I decided to make all of this work together that the tweets will need to be public. Even if you don’t share a link to them, they are technically accessible via the API, so if there is private stuff in the tweets I recommend deleting the -tweets blog completely. (Private posts is something we will revisit later, but not this year.)
@manton waiting for my archive to be downloadable, really curious about this so I took a paid plan!
By the way micro.blog evolved so much since last I checked, it’s amazing work!
@manton how does it work if in the future I import another archive, same user, will it just do incremental and add up the the archive provided it’s the same user?
@manton how does it work if in the future I import another archive, same user, will it just do incremental and add up the the archive provided it’s the same user?
@rmdes When importing again it clears the previous tweets first. There’s probably some room for improvement here to make it more efficient.
@manton Interesting, thanks! yeah maybe taking some ideas from here github.com/tweetback… would allow the setup to be connected to a twitter app and then periodically just index new ones, like tweetback is doing :)
@rmdes What Tweetback is doing there is going to stop working this month with the Twitter API changes. There will no longer be free read access to Twitter. 🙁
@manton I’m importing my zip file since yesterday.. It’s like 99% loaded but it seems to be stalled, anything that could be done server side to execute the import? Or should I try the upload again?
@rmdes I’ve seen a case of the import just stalling and never finishing. If it looks like that happened (check the Account → View logs) I recommend just uploading again. It will clear the tweets and start again, but it won’t have to copy the photos again, so should be much faster.
@rmdes I think I misunderstood, is this the progress bar during upload, or are you guessing the 99% because of how many tweets have loaded? If you don’t mind, follow up with an email to me at help@micro.blog and I’ll investigate in more detail.
@manton not seeing anything related to this in the log but there is some token error, maybe from a mobile app (I’m trying different mobile microblog clients)
@manton progress bar, I can see that it’s all loaded up less a very tiny small white space, OK I’ll drop an email!
Good news, even with an untouched 1.7GB Twitter archive!!!
Apparently it’s processing, see your email for log :))
@manton Good news, upload worked even with an untouched 1.7GB Twitter archive!!!
Apparently it’s processing, see your email for log :))
edit:
I’v let it do it’s thing the entire night but nothing appears in the tweet blog, so now I’m uploading again let’s see if it manages to crunch the archive
@manton just an update on this, I cleaned my Twitter archive from duplicates and deleted tweets media, went from 1.7GB to 1.2GB uploaded, now it’s importing and I can see it’s working on the log just fine !! waiting to complete to check the results !! big thanks for this feature !
Hi, @manton! Hope you’ve had a great day! I’m wondering if you could help with this (or if anyone else who’s followed this thread has seen it): after importing all of my tweets into a new tweet-specific Micro.blog, I can see that my site’s archive now shows all posts whenever you click on a specific category, which it didn’t before. I successfully imported all tweets and thought that this would resolve itself, but it hasn’t. Did I do something wrong or is there some way that I can fix it, so that each category only shows its specific posts? Thanks! 😀
@martinfeld Has anything else changed with your blog settings or theme? The tweets really shouldn’t have any affect on categories on your blog. I feel like it must be coincidence. Might be worth trying to change to a different theme plug-in temporarily to see if that fixes it.
@manton Thanks for the quick response, although I didn’t expect it! I just saw that you had a tweet plugin update, and so I did that and now only one archive category seems to be affected—looks good! It’s actually a good excuse to go and fix up the silliness that is my categories, so thanks again!