So let’s take this actual example: There’s !canada@lemmy.ml and !canada@lemmy.ca. They talk about the same thing, but are treated by the current federation implementation as separate instances.
How would you feel if there was a moderation feature to import another federated instance’s community into your own, so that the posts from the other instance automatically show up in the same feed? That way, you only have to subscribe to one community on one instance, but you get content from multiple instances. I’m not talking about crossposting or mirroring/duplicating posts between communities, only displaying the posts from another instance the community’s home server federates with, with moderator discretion.
Makes sense not to do it by default, but I think the option to form a single coherent community across servers is crucial to avoiding platform-killing fragmentation. Otherwise what’s even the point of being “federated?” It’s just a bunch of separate servers.
You can add !canada@lemmy.ca as a subscription to your account on lemmy.ml and it will be treated more or less as if it was a (!) community on lemmy.ml. This is what federation was always about.
What the OP is suggesting is more like distributed communities, a bit similar to matrix.org chat rooms. Federated content is AFAIK already replicated on the connected server, so it seems feasible to implement something like that, but there are probably some details in the ActivityPub specs that make it difficult to do so (for example: I think AP does not allow substituting the sender).
Sure, but again I come back to the question of, what’s the point of being federated then? I may as well just be using a local client to present me with a set of RSS feeds from different websites or something.
And that’s how I’d assumed Lemmy was going to work until I saw this post. It seems intuitive to me that subs of the same name would at least have the option to “sync” across servers.
Why would !main@startrek.com be synced in any way with !main@starwars.com ? They have nothing to do with each other. Communities should stand on their own, and it should be the users choice which federated communities they subscribe to.
then what’s the point of lemmy? a federated community is in a sense centralizing communication through multiple isolated servers. if each one is isolated from the other, and we have 10 different discussion hubs focusing on !chocolatecakes@cooking.com, !chocolatecakes@cookies.com etc, then the community is severely fractured and lemmy as a platform doesn’t work as it doesn’t take advantage of the integration at all. for it to work as a platform, cooking.com should be able to choose if it wish to include !chocolatecakes@cookies.com.
The point is you can follow federated communities from any server. Not that those communities are “shared” by several instances. What you’re talking about isn’t federated, it’s merging. Does mastodon let you merge users across instances?
precisely, so a !main@startrek.com community makes very little sense for how communities are integrated through federation, a !startrek@mywebsite.com makes a lot more sense, but when there is a !startrek@mywebsite.com and a !startrek@yourwebsite.com you’ve fractured the community if both lemmy servers are federated. a !tng@mywebsite.com and a !ds9@yourwebsite.com makes more sense. you can’t really compare it to how mastodon as it’s an entirely different type of community platform.
Both use the same protocol, and Lemmy communities are ActivityPub actors just like Mastodon users are. We could do something so !startrek@mywebsite.com would share posts from !startrek@yourwebsite.com, but the way Apub works, they will always be separate.
that sounds like a good way to avoid fracturing communities but how would it work in ways of moderation?