• Hypx@fedia.io
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    9 months ago

    I’ve noticed that a large number of communities on Lemmy.world aren’t visible here. You only get a 404. I’ve noticed this when looking at US state communities:

    https://fedia.io/m/washington@lemmy.world https://fedia.io/m/oregon@lemmy.world https://fedia.io/m/illinois@lemmy.world https://fedia.io/m/georgia@lemmy.world https://fedia.io/m/indiana@lemmy.world https://fedia.io/m/florida@lemmy.world https://fedia.io/m/wisconsin@lemmy.world

    And I’m sure there are others. What’s weird is that some are visible, but others are not. There doesn’t seem to be any pattern that I can see.

        • jerry@fedia.ioM
          link
          fedilink
          arrow-up
          4
          ·
          9 months ago

          Ok. I don’t know why this works, but if you search for the magazine (ie search for oregon@lemmy.world) it’ll return a result. After that, the links you posted starts working.

          • Hypx@fedia.io
            link
            fedilink
            arrow-up
            4
            ·
            9 months ago

            Yes, it’s coming up now, but no content is being federated. So it is unfortunately showing up as an empty sub.

            • eruraindil@fedia.io
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              9 months ago

              Remote magazines only get new posts from the point in time when they are created locally. It won’t pull old posts off the originating server.

              Update: Maybe not. I thought that’s how it works but I see content in the Florida one. Curious. I don’t know then. ¯\(ツ)

              Update 2: comment from e-five could explain how old posts show up on new communities.

                • e-five@fedia.io
                  link
                  fedilink
                  arrow-up
                  4
                  ·
                  edit-2
                  9 months ago

                  Make sure to subscribe to communities you want. It’s not just searching for it and loading it, but if there are no local subscribers it won’t get updates (and the last subscriber unsubbing would put it in this situation).

                  This became a bit harder to tell ever since mbin switched to showing real subscriber numbers rather than local like kbin has. There is an active PR to try to address this issue so users are able to tell when data isn’t coming in

              • jerry@fedia.ioM
                link
                fedilink
                arrow-up
                2
                ·
                9 months ago

                The Florida one does because I followed it and there has been posts since then

                • jerry@fedia.ioM
                  link
                  fedilink
                  arrow-up
                  2
                  ·
                  9 months ago

                  actually, I’m wrong - the posts that appeared after I followed it are weeks old. I can’t explain that.

          • AchtungDrempels@fedia.io
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            7 months ago

            I can’t seem to get a result for f.e. bicycle_touring@lemmy.world

            I searched for it in magazines. Do i need to search for it elsewhere?

            edit: Oh yeah, i guess i needed to search from just the main search. Found it.

    • jerry@fedia.ioM
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      Also, I checked the source and there have been no new posts since. I’ll keep an eye on it.

      • ciferecaNinjo@fedia.ioOP
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        Thanks for the investigation and tips. I was able to see it by querying the substring you mentioned.

        I didn’t even think this thread herein posted. Got the 500 error a couple times when posting here and in mdev, and gave up. I forgot that error 500 often happens /after/ the task executes, hence some dupe threads.