The end, though, is the same. lemmy.ml well still want their version, so they can have their own content rules. What you’re suggesting is functionally centralization, which is already an issue for Lemmy based on its design; consolidation would aggravate it.

Eventually, lemmy.ml !linux users would want to have their own community to enforce rules programming.dev won’t. Diaspora is inevitable. Consolidation fixes the wrong problem - a better solution would facilitate less centralization.

So:

• Lemmy provides the information
• It’s the client responsibility to do the interleaving

Yeah?

Hmm. Would that be good, though? Different rules, different moderators. Wouldn’t an aggregation system based on subscription be better? Consolidating would result in a consolidation of power into the hands off a few.

Consolidation would also encounter trouble when server admins disagree with moderators about community rules. When conflicts happen - which they inevitably would - we’d have a situation where the community would split as some moderators recreate a new community on a different server. It was hard enough when lemm.ee shut down, and that have communities no option but to switch; if the reason for a move is policy and not server shutdown, the chaos would be far worse.

The more I think about it, the worse consolidation sounds.

I figured it might be a client thing. Someone else did mention Piefed does this.

This might be the impetuous to fire up a self-hosted instance.

Neat! So, I have to switch to a Piefed account or run my own Piefed server? Does this mean that Piefed performs this aggregation in your feed when you’re browsing your subscriptions?

Please fucking no. Karma is responsible for all that is bad on Reddit. Lemmy, so far, seems to be avoiding the worst of that.

For the love of the platform, no.