I recently made a community, [email protected]. The community can be seen from this instance, but isn’t accessible from other ones.

For example, if I go to https://lemmy.one/c/[email protected] , I get an error.

Is there some requirement communities have to reach before they appear on other instances? Is this a bug?

Sorry if the answer is obvious or has been asked before, but I couldn’t find any info on this.

  • @BarbarianEnglish
    7•1 year ago

    (even though I understand it’s probably a performance or otherwise concern)

    Yes, exactly that. It’s to enable smaller servers to exist without having to download every post & comment from every community on every instance (including some troll spam communities that would inevitably spring up if it was done this way), filling the storage and immediately dying.

    That seems kinda like it’s a second-class experience for anyone on a different instance unless I’m missing something.

    Ideal setup atm is lots of mid-sized instances, especially if grouped by interest. If 1 person or 10,000 people are subscribed to the same community, it’s the same footprint. It’s actually a relatively efficient way of doing things.

    The solution I guess is creating an account on the other instance if you want to see all the older top posts, but then you’re starting to make accounts on multiple instances which is not my personal preference.

    Best workaround yet is lemmy.directory. It’s a bot instance that just subscribes to every community it can find. Signups disabled so the server doesn’t explode xD They’ve enabled signups? The absolute madlads.

    • @[email protected]English
      1•1 year ago

      Ahhh I see. That makes sense.

      I guess a bunch of big severs downloading everything from smaller servers would also create an issue too just like the other way around huh?

      • @BarbarianEnglish
        1•1 year ago

        Yeah, pretty much, except for the fact that big servers are more likely to have the hardware to deal with it.