There has to be a better way to keep the strengths of federating without partitioning the community smaller and smaller until there is no community left.
Can you imagine Lemmy with a similar amount of Reddit users? Anytime you'd post, you'd have to replicate it between X number of instances (for visibility). Conversations would be fragemented and duplicated, votes would be duplicated. To me this almost sounds like "work"...
There has to be something better.
For example, instead of "every instance is an island". Meaning the current hierarchy is "instance" - > "community" - > "post" - > "threads". We could instead have "community (ie: asklemmy)" - > "post (ie: this post)" - > "instance (Lemmy.ml, Lemmy.world, etc)" - > "threads (this comment)".
From a technical perspective, it would mean that each instance would replicate the community names and posts. Which is already beginning done (this post is a perfect example), but as long as each instance would share a unique identifier to associate the two communities/posts as "the same thing" (and this could simply be the hash of the community /post name). Everything else would be UX. Each instance would take ownership of the copy of the community and post, which means they could moderate it according to their standards.
I think it's related to this issue (re: lemm.ee is fetching and caching images (to improve performance) , but often get is throttled (because the Lemmy's cache implementation was not designed to work with larger Lemmy instances ), which results users seeing broken images).