Is it possible to import my entire Twitter history from an archive? I’m ok with multiple-step conversions (convert Twitter archive to Wordpress then import to micro.blog?) if someone knows what procedure will work.
Thanks!
JP2
If you can find a Twitter → WordPress migration, and then import that into Micro.blog, that is probably the best way to go. Early versions of Micro.blog did have direct Twitter import, but we ended up removing the feature because so many people who used it decided later that they didn’t want their tweets in Micro.blog after all, especially if they had 10s of thousands of tweets. Perhaps it’s something we can revisit later, such as hosting a separate archive that exists apart from the blog posts.
I have 168,199 tweets (no, I don’t know how that happened either) and I do want to import the entire kit.
Feature idea to address the user need you mentioned: Possibly tag them on import and have the ability to delete all posts under a given tag?
That is a lot of tweets. 
I would recommend waiting until there’s a way to tag them (batch delete is a good idea too). In the old import, we had a setting to filter out retweets which also helps. Having that many tweets won’t play nicely with our default Archive page, although that can be customized.
I’m looking again at options to import the tweets.zip file and store it separately so that it doesn’t mix with other blog posts. I think that will be useful to the most people since you can have an archive of your tweets without the overhead of managing them.
2 Likes
(I’ve been buying your stuff since Wii Transfer; keep up the good work!)
1 Like
I’m currently attempting to import my (43,000 
) tweets via this nice-looking wordpress plugin. If it works, I’ll write up a quick guide in the next few days.
I definitely think tagging and such could be an issue. Is there a good way to test it somewhere other than my real blog? (e.g. does micro.blog’s wordpress importer use something open-source under the hood, where I could spin up a local hugo site and test it out?)
You can create a test blog under Design → Edit Custom Themes. I strongly recommend importing tweets into a test blog in case you change your mind, then you can just delete the whole test blog and recreate it.
Based on our experience when we used to have a full Twitter import, I still don’t think most people will want tweets and microblog posts together. I want to build a separate feature for storing a Twitter archive. Adding tens of thousands of posts will make managing the “real” blog posts more difficult if everything is together.
Thanks! I think you’re right about the UX issues. For the “separate archive” idea, something like this project looks like interesting prior art (here’s what it looks like running live).
I wasn’t ultimately able to get my hacky Twitter->Wordpress->micro.blog import working because of the limitation on images in WXR, since I didn’t want to put my local Wordpress instance online. I’m still interested in trying to crack this as a technical challenge though. Do any of the currently-supported imports handle images without needing a live url for the image? I’m thinking I could write a script to generate a medium/tumblr/.bar export and try to work with that
If you have Micro.blog for macOS, that has the best .bar importer right now. It can also preview a .bar file if you double-click on it. Tumblr import is broken right now because Tumblr changed their format… Hoping to get that updated very soon.
I like the Tweetback approach too. That is along the same lines as what I’m thinking.
1 Like
Is reinstating the tweet importer still on the to-do (priority?) list? I’m all in on owning my internet content and consolidating it here. I’d love to get my tweets (but probably not retweets) into the fold!
Twitter import is still on the to-do list. I remain a bit conflicted about the best way to implement it, because I think tweets are best as an archive that sits alongside the blog but not as blog posts. I’ve been thinking about storing the tweets in Micro.blog and loading them dynamically into your blog with a plug-in.
Hmm, that would be an interesting solution. I think I’d personally like the option to import them as blog posts for future-proofing and archival sake — even though I might have to manually scan through them to remove old posts I didn’t want to keep. But I’d be open to other possibilities.
Glad to hear it’s still up for discussion!