Right now there are similarely named communities across the fediverse.
“fediverse@xxx”, “Linux@xxx”, “asklemmy”, “askkbin”…etc…
I’m on kbin and I’m having a hard time figuring out how to use the fediverse more productively, by reaching the largest amount of people for asking questions, solving problems, simply put: to engage… like I used to do on Reddit?
As @flloxlbox said, it will either happen organically or users will decide to merge communities, like the Android community did. It’s the way federation works, it’s not something that can be forced on people.
I would like to see some kind of “canonicalization” feature in Lemmy to support this, similar to CNAME in DNS.
For example, [email protected] recently merged into [email protected], where lemdro.id is the canonical server.
So it would be awesome if [email protected] was entirely equivalent to [email protected]. But as it stands, the lemmy.world community had to lock and everyone had to individually migrate themselves.
Essentially, in a case like this, I just want to call it !android (or c/android) and not need to care about which server it is hosted on. But as it is currently, I always have to reference the canonical domain since it is different than the one my account is on.
Aliasing is a thing on Mastodon user accounts. There’s no conceptual reason it couldn’t be extended groups on other platforms, too.
At the same time, if group aliasing became a thing, one should not expect that one group become an alias of another. Centralizing communities doesn’t always make sense, and our Love of Large Numbers is something we should actually actively push back against.
Aliasing makes sense when you have a dozen tiny communities, none of which are large enough to be self-sustaining. Once communities have crossed the critical limit and become viable all on their own, we really shouldn’t actually want them to merge with other viable communities. Smaller communities are easier to moderate, are generally friendlier spaces, and the promote a larger diversity of opinion and active, meaningful discussion.
Bigger ones devolve rapidly into jockeying for attention.
If you’re only going to read 10 or 15 posts in a community, be it one of 1000 users or one of 10,000,000, then you’re generally going to be better off with the 1000. Anything big enough to make it to the top of the big blog will probably be discussed in the small one, too. But the opposite is just not going to be true.
This is how Threads would take over the Fediverse and eventually win when they decide ActivityPub development is too slow and holds them back.
Boom all your communities are now empty.
Federation works because we’re spread out. Just subscribe to all the small communities.
Now, what might be a better idea is a cross post functionality where the crosspost has a single identifier of its own so it only will show up once in your feed (I guess as your local instance)
That way you can have the ability to reach everyone as if you had posted a bunch of times, but a big popular corporate instance can’t gather up all the communities and then defederate and wall them off.