Like when i look at communties it doesn’t show other big ones out there. And also all the subscribed counts are super duper off. On top of that all doesn’t even seem to see some of the biggest posts of the day from across lemmy. Anyone know whats uyo with that?

    • michael@yall.theatl.socialMEnglish
      1·
      1 year ago

      The subscriber count (if you are viewing through a web browser) is going to be the number of subscribers from this instance to the community on lemmy.ml. This server is working fine - perhaps if you joined lemmy.ml instead of yall.theatl.social, you may have a better experience!

      • ArtificialLink@yall.theatl.socialOPEnglish
        1·
        1 year ago

        I’ve joined several instances. Im simply pointing out an error or bug. You instance does not seem to be properly federating with other instances. I like this instance because I wanna be part of an instance that is closer to “home” but that said the browsing experience is significantly off. A lot of posts that show on all do not show on this instances of all. As well as the other issues i mentioned earlier about posts from communities being days old despite those communities being very active. Some of those communities that have thousands of subscribers don’t show up in the community browser even. I’m just trying to sus out whats up? Or potentially point out a major bug and issue y’all are having?

        • michael@yall.theatl.socialMEnglish
          1·
          1 year ago

          I’ve reviewed the logs and it appears the issue is that some instances (such as the ones you were attemping to view) are using a newer version of Lemmy than the official release. The latest tag for Lemmy software is 0.18.2, while the last release is 0.18.1. I try releases and not tags, so perhaps dev forgot to do so.

          I’ll update, and presume that things will federate properly afterwards.

          • michael@yall.theatl.socialMEnglish
            2·
            1 year ago

            So, all updated - the issue is that Lemmy (currently) does not pull older posts or other metadata from a community from another server until a subscription is made to that community/server.

            So when you join a community from another server, you’re not going to see a lot, until that server “pushes” new posts to yall.theatl.social

            That behavior may change with software changes, but it is what it is for now. The same issue occurs on Mastodon too. If you are on a larger server, you won’t have this issue, because it’s likely that larger server has been receiving posts all along.