Otherwise, if we have a lot of medium sized instances but the most popular communities are hosted on just a few huge instances, doesn’t that defeat the purpose of distributing load across many instances?

If that’s the case, how do we solve the cumbersome user experience of having to subscribe to the same community over and over again across a ton of medium instances?

    • Meldrik@lemmy.wtf
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      1 year ago

      We need something like “Multi-subreddits”, where you can combine communities into the same entity. Only issue is that a lot of the same posts are posted a cross all the same communities.

      • untitled_liar_liar_sequel@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I’ve been thinking about this all morning and have come up with this:

        When the link is the same, we can just union on the thread and sort it as any other thread.

        When the link is not the same, but the content is similar, I wonder if you could run a semantic comparison (I’m only just starting to learn about this), and when the comparison scores above a certain threshold, union the threads.

        Self-text posts might just make sense to leave alone.

    • RoundSparrow@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      A multi-community feature like multi-reddit wouldn’t be that hard to implement. Basically build a subscribe list that isn’t owned by a specific user and come up with a way to link them by name and ID. Being able to share community subscribe and block lists would seem a useful evolution of Lemmy.