• lutillian@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      1 year ago

      Because currently lemmy doesn’t substitute links to rewrite them from your own community.

      Eg. !cats@sh.itjust.works would refer to https://lemmy.one/c/cats@sh.itjust.works From your instance. If people don’t link correctly though it’ll direct to https://sh.itjust.works/c/cats which you wouldn’t be able to join

      Essentially as long as your instance isn’t actively defederated from a given instance, you can typically join your instances “mirror” of that community.

    • fieldhockey44@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Two likely possibilities with further detail about each below:

      1. The link you clicked took you to the community on the host instance rather than the copy on your local instance, or

      2. The community is on an instance that’s defederated with your home instance.

      When you view and interact with communities and content hosted on another server, you’re technically interacting with a copy of that community/content that’s hosted on your home server and kept in sync with the main copy. So if I want to subscribe to /c/technology hosted on lemmy.world even though my home instance is sh.itjust.works, I need to visit the copy on shitjustworks at sh.itjust.works/c/technology@lemmy.world

      If I went to lemmy.world/c/technology, I couldn’t interact because I don’t have an account on the lemmy.world site.

      As I said above, communities and content are copied between Lemmy instances and kept in sync across the copies. But sometimes an instance will ‘defederate’ with another, ie cutting the direct connection between them that lets them copy and sync content. In that case, there’s no local copy for me to subscribe to or interact with.

      The incorrect link is far more likely to be the issue than defederation, so whenever you run into that issue check the link and make sure it’s the copy on your instance.