Skip Navigation

How are you managing your interaction with redundant communities?

For example, I'm on Lemmy.ml and I've joined !photography@lemmy.ml, !photography@lemmy.world, and !photography@kbin.social. In this example, it's not very different from the number of similar groups on Flickr but, in comparison to Reddit, it seems like the decentralized platform can be a little unruly.

How are you going about joining different communities and managing your engagement? Are you only participating on the community on your instance? Are you joining and posting in as many instances that seem relevant?

59 comments
  • For now I subscribe to multiple communities, but I really hope the Lemmy devs figure out a way to let each user create a community group.

    The way I envision it is that you can create a group where you can combine communities on your end, and you can then cross-post to these communities when you post to that community group.

    On the other hand, there would need to be a way to ensure that cross-posts aren't generating a ton of duplicates to those subscribed to multiple communities, and I'm not sure how the comments on these cross-posts should be dealt with. Maybe the comments should be kept separate per cross-post, or maybe if you have these communities in a group there could be a way to display the comments from there multiple posts together, to ensure all those crossposts have a change to get some interaction on other instances?

    Then there's also the possibility of spammers abusing the system.

    There is still place for improvement.

  • My guess is the various Android & iOS clients will add this feature to combine similar communities and view all of their content together in one feed (like multireddits on reddit).

    But I hope this feature is implemented at a system level in the Lemmy software itself.

    I think many people may have already requested this as a feature on official GitHub issues.

    • To me this is basically a necessary feature of a fediverse app that wants to be similar to Reddit.

      Smaller communities are fantastic, but one of the unique appeals of Reddit was that for the largest communities, they were likely one of the most populated communities for each topic available. So posting to that community ensured the broadest reach, and greatest likelihood of engagement or getting one's questions answered.

      I hope we can find a federated way of providing a similar experience. Perhaps via replication between instances.

      • From a user front-end standpoint, just collate all posts with identical links and then make a tabbed system for comments. Lemmy.ml comments are on this tab, kbin.social comments are on this tab, etc etc. Seems like by far the easiest way to present it without (accidentally or otherwise) force-federating all of the source material. This could even pretty easily ("easily", yeah I'll get right on that) be done within the app if not done in the lemmy/kbin source code directly.

  • If it's a niche interest such as photography, I would just subscribe to all and see which one is the best over a few weeks.

    If it's a more dynamic topic such as technology, I will go for the most curated version if it (Beehaw communities are usually good ones, at least to me), and only subscribe to one. Otherwise I'm getting overwhelmed with multiple occurrences of the same article.

  • It's not too bad, minus people crossposting the same content across each instance

  • The way I see it, some communities will thrive and others will die. No need to worry about the mess in the process. For now during this early stage just post to all of them or pick one you like and stick with it.

  • I don't even know man this shit is so confusing. I used to just comment and upvote when I saw shit I liked but now how will I know if the shit I liked came from one server or another. This is just madness we can't keep treating people this way!

59 comments