baraza - 0.14.1 lemmy.ml - 0.14.3

I am posting from @halo@lemmy.ml to !africa@baraza.africa. Baraza is also federating with mastodon.social. A mastodon account, @mbiruiru@mastodon.social follows baraza.africa/c/africa community.

When the mastodon account replies to the post made by the lemmy account on baraza community, the reply goes to lemmy only and is not propagated to baraza.

will comment on this post with observed changes.

  • haloOP
    2·
    3 years ago

    Update after 18 hours or so:

    This post did not federate to c/Africa on Baraza even though it appears like so on Lemmy.ml. I updated the install from 0.14.1 to 0.14.3 and new posts made from lemmy to baraza did federate. Proximate cause for non-federation could then be different lemmy installations. But I was getting content on Baraza from lemmy, just not posts made directly to communities there.

    Even after updating, a post to Baraza from Lemmy is not federating:

    I will observe this issue and probably make a proper issue on Github.

    • haloOP
      2·
      3 years ago

      Did you try to follow Baraza communities via Mastodon? I did see that “Cancel Follow Request” sporadically and now it seems resolved (displaying “Unfollow”). The mastodon federation is still at the community level. I will check in with @nutomic@lemmy.ml on what that means exactly. Is there a role for the remote Mastodon admin to play so that “Cancel Follow Request” move to full “Unfollow”.

      • nutomicA
        3·
        3 years ago

        For Mastodon to follow Lemmy communities, you need to change the Lemmy nginx config like this.

        • haloOP
          2·
          3 years ago

          Before I make the changes, what does that mean in practice? I have an account on Mastodon and it sees posts from baraza communities. I am on lemmy0.14.3 if that helps. Was this nginx config a requirement when updating? I did not see it in the docs, unless it was baked in during the updates.

          • nutomicA
            1·
            3 years ago

            Its a change we made for Mastodon to be compatible with Lemmy. So it was part of the v0.14 release, but we forgot to mention it in the changelog. Without it, Mastodon wont be able to fetch Lemmy posts/communities etc when you search the url on Mastodon. But that is working fine with your instance.

            There is something wrong with your inbox though, meaning activities sent to your instance dont arrive. Make sure you also have this line (with correct port). Ansible takes care of that automatically btw. If the nginx config looks fine, try to capture some logs on your instance while sending an activity (eg create comment or vote) to baraza, using docker-compose logs -f lemmy -t 100.