I’m still learning the quirks of federation and the behaviors of communities hosted on different instances, so I apologize if this is something that’s been asked repeatedly.

I made a post to a community I am subscribed to at lemmy.ca, from my home instance at slrpnk.net. Public posts on that community (as well as the post that I made) are not showing up from my home instance. My profile page on my home instance does not show any record of the post that I made.

I was only able to find existence of the post that I made by going to lemmy.ca, and then finding the community that I posted to from there.

!woodworking@lemmy.ca

    • technomad@slrpnk.netOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      The language settings are set to auto.

      I’m using the Photon frontend if it helps.

      • poVoq@slrpnk.net
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        2 months ago

        The auto-setting is about what the language the frontend uses, what Blaze meant is the language visibility setting in your profile.

        Edit: hmm, I can’t actually find that setting in Photon, but what ever you set it in the classic lemmy-ui might still effect visibility on Photon.

        Edit: https://slrpnk.net/post/14775569

        • Xylight@lemm.ee
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 months ago

          I need to add language settings to communities and profiles. I really dislike how lemmy handles this though.

          If you change it in lemmy-ui, it will propagate to Photon because it’s an account wide setting.

          • poVoq@slrpnk.net
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 months ago

            Ah, so that confirms my suspicion that is propagates from lemmy-ui, thanks.

            I agree that the way this is currently handled in lemmy-ui is really bad, but I am not sure how to do it better either. At the very least “undetermined” should probably always enabled and not possible to accidentally unselect.