You cannot assume that communities with the same name are meant to be on the same topic.
Say I set up an instance focused on discussing parties at home. There are fun in-person games you can play with your friends when many of you are over, so I would create a community c/games for discussing them. Now, what if I want my instance to federate with lemmy.world? They already have a c/games that is dedicated to videogames. Maybe I also would need a community dedicated to videogames, but I’d have to call it c/videogames, because I already have a c/games.
Some human intervention would be required to let the network know that the local c/videogames is the one that has to federate with lemmy.world’s c/games, and not the local c/games.
Maybe an automatic suggestion would be fine as a starting point, but it would be more useful that communities themselves could explicitly establish which remote communities they are associated with, without depending on the names.
You cannot assume that communities with the same name are meant to be on the same topic.
Say I set up an instance focused on discussing parties at home. There are fun in-person games you can play with your friends when many of you are over, so I would create a community c/games for discussing them. Now, what if I want my instance to federate with lemmy.world? They already have a c/games that is dedicated to videogames. Maybe I also would need a community dedicated to videogames, but I’d have to call it c/videogames, because I already have a c/games.
Some human intervention would be required to let the network know that the local c/videogames is the one that has to federate with lemmy.world’s c/games, and not the local c/games.
Maybe an automatic suggestion would be fine as a starting point, but it would be more useful that communities themselves could explicitly establish which remote communities they are associated with, without depending on the names.