I’m curious, if I’m subscribed to a community on an instance, why doesn’t Lemmy “unlock” all of the communities on said instance. I’ve found that despite being subscribed to a few on an instance, my instance seems ignorant of other stuff happening on the instance.

  • ඞmir@lemmy.mlEnglish
    0·
    10 months ago

    Scalability. This is much better for people running a lemmy instance without terabytes of disk space.

    • sabreW4K3@lemmy.tfOPEnglish
      0·
      10 months ago

      You shine a torch at someone in the dark, you can see more than just them though

          • maegul (he/they)@lemmy.mlEnglish
            0·
            10 months ago

            So im guess you’re asking why things behave this way?

            There are two parts.

            1. Synchronising all of the data from all of the communities would consume more data and network resources. So instead, it’s only done if a user subscribes. Should help save on some data and synchronisation.
            2. You may also want to know that a community exists on another instance even though you’ve never subscribed to it. And that’s fair IMO. Being able to explore what’s on another instance directly from yours makes sense. But that’s what the other instance is for. Go to their web page and explore from there. This is a decentralised system. Sure there are some rough edges … like being able to subscribe directly from the other instance should help smooth over the UX (and I think this might have been added in v0.19?)