Over the past few days, I’ve witnessed a remarkable surge in the number of communities on browse.feddit.de. What started with 2k communities quickly grew to 4k, and now it has reached an astonishing 8k. While this exponential growth signifies a thriving platform, it also brings forth challenges such as increased fragmentation and the emergence of echo chambers. To tackle these issues, I propose the implementation of a Cross-Instance Automatic Multireddit feature within Lemmy. This feature aims to consolidate posts from communities with similar topics across all federated instances into a centralized location. By doing so, we can mitigate community fragmentation, counter the formation of echo chambers, and ultimately foster stronger community engagement. I welcome any insights or recommendations regarding the optimal implementation of this feature to ensure its effectiveness and success.
There’s an advantage to splitting the load amongst multiple instances. If [email protected] has issues, the subscribers to community can still access [email protected].
Further, preventing centralization is a core focus of the fediverse, with all the pros and cons that come with it. The reddit migration is a testament to that philosophy.
If an in-fight happens between two instances’ communities, host1 won’t be able to boot host2’s entire existence, just their agreement to be in sync. Voluntary syncing of communities seems to me a natural extension of the federated philosophy.
I don’t have links handy, but the devs have said multiple times that federation replication load is not a limiting factor. It’s the browsing load that matters, which is already spread across the instances that subscribers hail from. There isn’t a performance issue here to fix, at least around the current network size.
Again, user-account federation already provides this. If the host where the community resides is down, I can still read existing posts, and post and comment with users on my local instance. I don’t see significant further benefits in splitting the community hosting.
I don’t disagree with this, the challenge is that the federated philosphy makes everything it touches very complicated. A sprinkle of federation in the core of an ecosystem brings enormous resilience against the ecosystem getting coopted against the will of its users. A heaping spoonful of federation makes it an unusable mess. The complexity of federated design needs to bring very big benefits to “pull its weight” in complexity. The tradeoff looks positive for me for federated replication even though the cost in complexity is large, but I don’t for meta-communities. They seem like cosmetic improvements over the existing capabilities.
But fair enough, I see where you’re coming from. It’s not madness, on-balance it’s just not something I see providing value in proportion to its conceptual complexity.
Can you help me understand how that all works? I ran into this today where an instance wouldn’t let me submit due to performance issues, and I jumped instances to be able to provide some (potentially) important breaking news to “community.” If they were fully in-sync and one instance didn’t “own” the community, when things stabilized, my content would have replicated instead of being stranded on a lonely instance. As it stands, that content will never be part of the “real” community.
Right on. I’m still new to the fediverse and am probably missing some foundational concepts still. Love where it’s headed though.
I’ll preface this by saying I haven’t read the code and it’s certainly possible there are errors in my mental model, but my belief is:
It’s possible I’m mistaken about 3-5, but if you had trouble posting… my guess would be that your own user-instance was struggling and slow. But if you’ve rules that out maybe the update behavior when the community-instance is down works differently than I think it does. The reading in step 2 I’m quite certain about though.
I’m pretty sure you can’t post to community-instance if they’re down/having issues to the local DB. The instance I’m on is very stable and every time I think it may be an issue, it turns out to be the other instance.
It sounds like a lot of the “sync” behavior I was thinking of is already built-in if we can just expand on it a bit.