Can any instance operators offer an explanation as to why federating with Mastodon from an instance not running their software tends to be more difficult

Can any instance operators offer an explanation as to why federating with Mastodon from an instance not running their software tends to be more difficult?

I've noticed lately that when viewing a profile from a Mastodon instance, their post history tends to be incomplete or otherwise missing. Any posts that are made recently tend to have a significant delay or don't show up on their profile at all.

I know that you can view the content from the remote instance in question for a complete profile, that you need to do so however does seem to be a failing on the part of the server software to properly federate and populate posts.

#SelfHosting, #FediAdmin, #Mastodon, #MastoAdmin, #ServerAdmin, #SocialMedia, #AskFedi, #FediMeta, #Fedi, #Federation, #Fediverse.

@saorsa@neondystopia.world it's not a "Mastodon vs the world" issue, you'll encounter similar issues with Mastodon accounts on other servers, especially those with few followers.

But you're not entirely wrong, depending on the software the content federates ... less well, shall we say, and each different platform does things a bit differently.

The gist of it is, ActivityPub is complicated enough that nobody really has a chance of implementing it 100% to spec. There's Mastodon flavoured ActivityPub, NodeBB flavoured AP, WP flavoured AP, Lemmy flavoured AP, etc...