Instructions for running your own lemmy instance.

For the moment, lemmy.ml is using an explicit allowlist for instances we federate with. If you currently run an instance, and would like to be added to join.lemmy.ml:

  • Let us know either on !lemmy_instances, or commenting here.
  • We’ll add you to our allowlist.
  • Add this block to your server’s lemmy.hjson config (for open federation):
federation: {
  enabled: true
  tls_enabled: true
  # allowed_instances: lemmy.ml,other_instance.tld,... uncomment this to use an allowlist
}
  • Type !announcements@lemmy.ml into your server’s search box, and subscribe to it to connect the two instances.
  • This is very good news! Have been looking forward to this for long time already.

    But it’s seeming that some things aren’t working right (Maybe it’s transfer problems? New posts seem to be working fine).

    For example, here the same post viewed from Lemmygrad:

    and from “main” Lemmy:

    Apparently the upvotes and some of the comments don’t show up when looking at it from Lemmygrad. This isn’t a single problem in only that post, you can look at !asklemmy@lemmy.ml for some more, or for example this post with no comments and 2 upvotes when viewing from Lemmygrad and 101 upvotes (and 32 downvotes lol) and lots and lots of comments when viewing from “main” Lemmy.

              

    On another note, are there plans to make the search search across instances? At the moment, it seems to not find posts from another instance:

    • @nutomic@lemmy.mlM
      link
      fedilink
      03 years ago

      The search is only local, but you can search the URL of a remote post/comment/user/community, and it will fetch that.

      • Helix
        link
        fedilink
        13 years ago

        does that still work? If so, how? Just entering it into the search box doesn’t seem to work (anymore) for me.

        • @nutomic@lemmy.mlM
          link
          fedilink
          13 years ago

          Yes, if its not working then either that instance is not on the allowlist of your instance, or the remote instance is misconfigured.