Over the past few days, I’ve witnessed a remarkable surge in the number of communities on browse.feddit.de. What started with 2k communities quickly grew to 4k, and now it has reached an astonishing 8k. While this exponential growth signifies a thriving platform, it also brings forth challenges such as increased fragmentation and the emergence of echo chambers. To tackle these issues, I propose the implementation of a Cross-Instance Automatic Multireddit feature within Lemmy. This feature aims to consolidate posts from communities with similar topics across all federated instances into a centralized location. By doing so, we can mitigate community fragmentation, counter the formation of echo chambers, and ultimately foster stronger community engagement. I welcome any insights or recommendations regarding the optimal implementation of this feature to ensure its effectiveness and success.

  • Barbarian@sh.itjust.works
    link
    fedilink
    arrow-up
    34
    ·
    edit-2
    1 year ago

    Damn, this is a lot of discussion and I don’t see a single person actually volunteering to actually go code the feature. It’s open source, you know? If anyone cares about the feature, go learn rust (like I’m trying to do now) and code it up.

    EDIT: In case anyone reads this, please look at entitlement in open source. It’s an eye-opening read for those not familiar with the headaches involved.

    • OptimusPrime@lemmynsfw.comOP
      link
      fedilink
      arrow-up
      10
      ·
      edit-2
      1 year ago

      I’m honestly more confused than I was before. With so many opinions, I don’t know how this could ever be implemented in a way that satisfies people.

      • Barbarian@sh.itjust.works
        link
        fedilink
        arrow-up
        18
        ·
        1 year ago

        It’ll be solved the same way anything gets solved in open source: those that can code make the final decisions.

    • Ajen@sh.itjust.works
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      “An ounce of planning is worth a pound of cure.”

      Nothing wrong with rushing into projects when you’re learning a new language, but on big OSS projects it’s a good idea to make sure you’re working on something that the maintainers are willing to merge. Getting community consensus is a good thing.

    • Discoslugs@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Thanks for the article. I really like the overall message about maintainers setting strong boundaries and being able to walk away.

      I love open source. And it is so sad when good projects hit snags because of a toxic user-maintainer relationship.