• sunaurus@lemm.ee
      47·
      1 year ago

      The problem is that if you have two communities with exactly the same purpose, then that will encourage people to duplicate posts to both. This splits up discussions into two separate comment threads. Also, merging these communities at the client end will cause you to see any duplicated posts twice 😅

      • I_Miss_Daniel@kbin.social
        71·
        1 year ago

        True. But if the client can see the duplicate and merge the post plus the comments from both posts into one on the user’s device, it would be transparent to the user. We’re just not there yet.

        I think the same would also be useful where the same article (post) is made on multiple subs (communities / magazines) within a certain time window. It’s annoying seeing the same post multiple times in /all.

        • CoderKat@lemm.ee
          3·
          1 year ago

          Yeah, I really hate the fragmentation because of that. Reddit admittedly had this problem too, but it didn’t feel like the same degree.

          I think it also is a barrier to growing a community because it can sometimes take some time for it to be clear which community is the biggest one. To avoid duplication, I usually only join the biggest community of each “type” and it’s not always obvious which one that is.

      • sigmaklimgrindset@sopuli.xyz
        5·
        1 year ago

        I mean it was like that on Reddit too. I would see the same articles posted on r/gaming, r/gamers, r/truegamers, etc. It’s not really a problem unique to Lemmy/Kbin