Rob Shearer wrote a detailed and fairly scathing critique of Mastodon. I don’t agree with everything in the post, but I do think he’s right about migration:
One of the big selling points of Mastodon was that you can pick which instance your account lives on, but it is easy to change your mind and switch to a different instance later on. This feature was wildly oversold.
Mastodon allows you to post the equivalent of a web redirect: your followers are informed of your new instance and seamlessly migrated over. Your posts, however, do not move with you. Which is kind of a theme: the system simply doesn’t think posts are terribly important.
Some of what Rob says might be difficult for Mastodon users and developers to hear. But migration is such an important part of the federation model that moving posts should be a priority. Micro.blog can import an archive of Mastodon posts. Why can’t Mastodon import its own posts?
I assume the answer is that the Mastodon team has prioritized social features over microblogging features. It’s a trade-off, but it means that Mastodon is not suitable as a blog replacement anymore than Twitter / X is. Anyone who cares about their writing or photos should be publishing them at their own domain name.
I’m proud of Micro.blog’s comprehensive post import. As of 2025, I’ve coded custom importers for a dozen systems, all built-in: WordPress, Medium, Tumblr, Mastodon, Ghost, Markdown, Substack, Write.as, Pika, Foursquare, Instagram, and Twitter / X.
The other side of Rob’s point about migration is not being able to recover if a Mastodon server suddenly goes down without warning. I’m not sure this is realistic to solve without major changes. My approach has mostly been to encourage users to preemptively think about backups, so at least they’re not left with nothing.
Ryan Mikulovsky Mastodon just needs a way to backdate and silence those posts, then the rest is easy for MarsEdit.
Samuel Lison Well thought out post. I felt exactly the same way about Mastodon.
I have my own instance, and I also use micro.blog and was “Syndicating” to my Mastodon instance.
But then, what is the point, when I can just use my own domain name and my fediverse identity created through Micro.blog? @samuel.
So I used the Migration tool on my Mastodon instance to let people know which account they should be following.
Yes, I lose my posts on the instance - but thankfully I’ve been using micro.blog for a while now and was cross-posting. Which means I have all the original posts still on my website and backed up to github and able to move where I wish, should I ever need to.
Owning your own content has never been more important than now.
Alexander Kucera concerning backups. I do have the automatic GitHub mirror enabled. Can I use that to restore my blog again? Or would I best export a .bar file every now and again? Or would a theme and markdown zip be best to restore my micro.blog fully including theme?
Michael Mitchell I’ve been thinking about this since reading your post. I didn’t realize all these issues existed with Mastodon, which has me wondering—should I abandon it or try something like Sharkey, which seems to address many of these problems? That said, Sharkey doesn’t appear to have widespread adoption yet.
I’m also not convinced that Bluesky is the answer. It doesn’t feel like the Twitter replacement we hoped for—at least, not like the pre-Musk Twitter that I really do miss.
Another thing I’ve been considering is whether Micro.blog would even support something like Sharkey if I made the switch. So, I’ve been doing a lot of pondering. Have I been wasting money running a single-user Mastodon instance that could be silenced without me even knowing it?
I still really like the core idea behind Mastodon. That’s what makes this all so frustrating.
Manton Reece @AlexKucera We don’t have an easy way to import the GitHub mirroring. I recommend doing an occasional .bar export and Markdown .zip too. The more you have, the more options you’ll have. I’d really like to add an automatic .bar export in the future.
Manton Reece @mlm361 In your position, I would stick with Mastodon for now. I don’t think all the compatibility issues with Micro.blog and Sharkey have been worked out. Bluesky has a lot of promise too and we’ll be doing more with it.
Manton Reece @slison I agree! Long term, I hope more people just have their own blog and ActivityPub tied together. Just more integrated and permanent that way.
Samuel Lison indeed. I haven’t been able to find any open source solutions available that allows that though and allows for self-hosting. Micro.blog is the closest thing. It would not be easy to just export out of Micro.blog and keep my fediverse identity going at the same time with all the backend work Micro.blog does on ActivityPub I think. Easy to keep the content, but not the fediverse side, timeline, follows etc.