Howdy,

I’ve been federating with lemmy.ml for a couple/few days now, and have just found that a post on lemmy.ml to /c/lemmy has not federated over to lemmy.ca.

Is there any way to check on how or why that might be occurring? And, is there any expectation of things being fixed if I, say, search for the community again on lemmy.ca?

Thanks!

  • nutomicA
    4·
    4 years ago

    Are you following !lemmy@lemmy.ml from the other instance? If not, new activities (including posts) wont be delivered to your instance.

    • kinetix
      2·
      4 years ago

      Yes, believe I am. https://lemmy.ca/community/8

      You’ll notice too that on this post I posted it from lemmy.ca, and the responses haven’t federated back.

      Federation seemed to be working for a short bit - in fact it may well still be working on some communities, like c/asklemmy.

      I had another node start federating !canada@lemmy.ca and that’s worked fine so far (all couple of comments worth).

      Hope the extra details are somewhat helpful.

      • DessalinesMA
        1·
        4 years ago

        I just checked, the DB says you are only subbed to !asklemmy@lemmy.ml . You have to subscribe to the other communities to get updates from them. You may need to re-subscribe.

        • kinetix
          1·
          4 years ago

          There’s an issue with federation keeping in sync with this then, as I was subscribed on lemmy.ca.

          I have unsubscribed from them and then re-subscribed. Do you see any difference on your end now?

            • kinetix
              2·
              4 years ago

              Interesting… ok, well, glad that got it going. Should I file an issue about (what I’m presuming) is kind of a race condition here where someone can subscribe to a remote/federated community before it’s actually allowed from the remote end?

              My actions on my end were to search for each of those communities, and I was apparently allowed to subscribe to them before they were able to actually federate.

              • nutomicA
                3·
                4 years ago

                Yes you can open an issue. We need to expose subscribe errors through the API, and handle them in the frontend, currently they are just ignored.