Seeing the Full Conversation: Fetching Replies on Mastodon

One of Mastodon’s biggest shortcomings is how it handles fetching replies to posts. This isn’t unique to Mastodon (it’s a limitation shared across much of the fediverse) but since I access the fediverse through Mastodon, that’s what I’ll focus on here.

The issue arises when I come across a post from a user on a different instance than my own. Since I run a single-user instance, every post I see is from another instance - and without taking extra steps, I can’t see the replies.

This happens because Mastodon primarily fetches content from users (and hashtags) that you - or someone else on your server - already follow. (This is a simplification, but it captures the core idea.)

This limitation has a few negative side effects:

• It kills the flow of conversations.
• It leads to reply duplication - I might unknowingly post the same reply as someone else, which can be frustrating for the original poster.
• It makes Mastodon feel more fragmented than it needs to be.

In this post, I’ll outline a few ways you can work around this and see more replies to posts on your Mastodon instance.

1. Viewing Posts on Their Original Instance

This is the most straightforward and reliable method. Mastodon’s web interface has an “Open original page” option for any post, which opens the post on the author’s own instance. You’ll then be able to see all the replies there.

Most third-party apps offer similar functionality.

Pros:

• Always works
• Requires no setup

Cons:

• Cumbersome to constantly open external links
• Breaks the “stay in one app” experience

Still, if you just want to catch up on a conversation, this method is the only bulletproof one.

2. Using FediFetcher

I wrote this tool myself, so take this with a grain of salt - but I genuinely find it invaluable.

FediFetcher scans your home feed and proactively pulls in missing replies, injecting them into your instance. That way, when you open posts in your own timeline, the replies are already there. (FediFetcher can do a lot more, but that’s for another time.)

Pros:

• Makes conversations more complete
• Keeps you within your own Mastodon instance

Cons:

• Doesn’t work with all remote servers (e.g., GoToSocial, Threads)
• Requires setting up and running external software
• Increases load on your server and others, as it scans many posts regularly

If you’re technically inclined and willing to run a small background service, this is a powerful option.

3. Using a Browser Extension

Substitoot is a browser extension (for Chrome, Firefox, and compatible browsers) that fetches remote replies when you open a post.

Pros:

• Easy to install and use
• Works in real time as you browse

Cons:

• Only works in supported browsers
• Doesn’t help if you use mobile apps or unsupported browsers (like Safari)

If you primarily use Mastodon through a desktop browser, this can be a simple, no-fuss solution.

4. Letting Mastodon Handle It

As of version 4.4, Mastodon includes an experimental option to fetch replies automatically. Admins can enable this in the instance’s configuration (via the .env.production file - see Fetch All Replies Documentation for details).

Unfortunately, this feature is opt-in, and there’s no way for end users to tell if their instance has it enabled, aside from asking their admin.

Maybe most importantly it really isn’t something that users can control: Their instance either has it enabled or not.

Pros:

• Built-in, efficient, and seamless for users
• No third-party tools required

Cons:

• Not enabled by default
• Some admins may worry about performance or storage overhead
• Lack of visibility or control for end users

Long-term, I think this is the most sustainable and user-friendly solution. But awareness and adoption are currently lacking.

In Summary

Until Mastodon adopts a more unified and user-centric approach to fetching replies, these workarounds can help fill the gap. Hopefully, as more users and admins understand the issue, we’ll see better adoption and wider availability of replies.