• eruraindil@fedia.io
    1·
    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.

    • jerry@fedia.ioM
      2·
      9 months ago

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

      • jerry@fedia.ioM
        2·
        9 months ago

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

        • e-five@fedia.io
          3·
          9 months ago

          It looks like someone from the remote liked it recently, which, and I’m channeling Benti here because I’m not as good at the AP side of things, announced to subscribers which brought it in here. At least that’s my best guess

      • e-five@fedia.io
        4·
        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

        • Hypx@fedia.io
          2·
          9 months ago

          Thanks. That seems to resolve the issue. Though, for a lot of smaller communities, no one is going to subscribe to them here, effectively making them invisible here.

          • e-five@fedia.io
            3·
            9 months ago

            I don’t completely disagree, hopefully the PR I linked, once complete, will make it a lot more obvious to people when this scenario occurs. I think from an instance owner perspective, they wouldn’t want to constantly be paying the overhead on communities no one has an actual interest in viewing (edit: this isn’t worded well, so forgive me, obviously people may want to view it but not have it show up in their sub feed, so perhaps another action item is a way to split subscription lists, which I think was already requested), as it has a very real financial cost to them. But I will keep this in mind, I meant to investigate how lemmy works (whether they also require a subscriber, I mean they do because this is how AP works but they might make a fake user or something, I never had a chance to look, but I’d be curious what tools they have to stop incoming messaging for when an instance owner wants to save bandwidth)

        • e-five@fedia.io
          3·
          9 months ago

          I mentioned in the adjacent post but if you do see magazines acting oddly, it could be there are no local subscribers. Hopefully we get a UI fix in soon with the PR I had mentioned, because it’s a bit of a bad user experience now. (I noticed world from lemmy world on debounced’s instance was getting no posts, or rarely a post with no likes, and subscribed, and suddenly everything came in fine.) So probably a good idea for people, if you want to see posts from somewhere, make sure to subscribe.

          (This was technically always true, but a while back admins were auto subscribed so a magazine would always have 1 subscriber. That changed, and that change was even backported to kbin by ernest, so it should be like that back in kbin too for new magazines.)