or maybe at least the posts wouldn’t be replicated, but there would only be one community, and when you visit it, posts for the community are downloaded from your primary instance, as well as other instances based on some configuration that makes sense.
I think this is going to be the main bottleneck in the end. The principle of it might be great, but too many people won’t like this hurdle i’m afraid.
I don’t understand how this is a hurdle or a problem when it’s brought up. I subscribe to both in this situation (already am with these two).
I do think it would be cool if communities across instances could essentially link their feeds. But I don’t think that should be forced. Or maybe implement a user feature to group communities so you can click to see their combined feeds.
Just saying that 99% of users will not get this part of Lemmy. It will split all users across multiple communities where most will not even be aware of others.
I can be totally wrong, but this is my gut talking.
yes, that’s pretty much what i’m saying. in the background, that is what would be happening, but on the frontend, the user just sees “communityname” and a bunch of posts that are pulled from all instances that have a community matching that name.