131

How should we deal with similarly named communities? (kbin.social)

submitted 1 year ago by adonis@kbin.social to c/fediverse@lemmy.world

86 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[-] OldFartPhil@lemmy.world 88 points 1 year ago

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.

[-] cbarrick@lemmy.world 26 points 1 year ago* (last edited 1 year ago)

I would like to see some kind of "canonicalization" feature in Lemmy to support this, similar to CNAME in DNS.

For example, !android@lemmy.world recently merged into !android@lemdro.id, where lemdro.id is the canonical server.

So it would be awesome if !android@lemmy.world was entirely equivalent to !android@lemdro.id. 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.