On Mastodon, when you follow another user on another instance, your instance will send a request to the other, to be notified of new posts made by that user, as well as posts they’ve boosted. When such a new post arrives, a copy will be created on your instance so it can be displayed without nagging the original instance again for the post’s content and such.

Lemmy is similar of course, since it uses the same underlying protocol (ActivityPub). Think of communities as “special users”. Whenever someone creates a post or reply, the community will boost it, so it ends up on every instance where a user has subscribed to that community.

Because you can’t follow / subscribe to users on Lemmy, the posts of Mastodon users that don’t involve Lemmy never end up being “federated”, meaning Lemmy instances don’t get notified of these posts, so they don’t end up being “copied”. This is the same on Mastodon by the way. Unless your instance sends out a request to fetch posts from an unknown user, it doesn’t know about their posts, since nobody so far has cared about them.

This makes sense because if you were to try and store all the content from the fediverse you would need a LOT of storage for little gain. Similarly it would be bad to never store the content and always fetch it, because that would generate a bunch of additional traffic, which especially small instances would suffer from.

To summarize: Lemmy doesn’t display Mastodon posts because it doesn’t have a mechanism to subscribe to those users.