2024-01-10 - Lemmy Release v0.19.2 - More Federation Fixes
join-lemmy.org

We just deployed the latest version of Lemmy 0.19.2 where the github code includes a possible fix for the outgoing federation issues we have been having.

But lets see before we celebrate. Help us test if outgoing federation seems to work now by making comments, posts and upvotes and see if they appear on other instances.

Of course if the other instances are on Lemmy 0.19.0 or 0.19.1, they could have issues with outgoing federation still until they update.

Release notes for 0.19.2: https://join-lemmy.org/news/2024-01-10_-_Lemmy_Release_v0.19.2_-_More_Federation_Fixes

  • mrmanagerOPMA
    2·
    9 months ago

    Hi!

    I looked and I can see the posts if I sort by New (default sort is Top Day I think):

    https://lemmy.today/c/retrogaming@lemmy.world?dataType=Post&sort=New

    That page has all the posts you mention above from the looks of it? Correct me if im wrong or if Im misunderstanding something.

    And of course we can create a lemmytoday community, sounds like a great idea. A place to bring up issues about the instance. I agree with you about the name also. Meta doesnt sound good, and also its related to that Zuckerberg place… :)

    • tal
      1·
      9 months ago

      Hi!

      I looked and I can see the posts if I sort by New (default sort is Top Day I think)

      Hmm. I’m sure that I checked sorted by New.

      investigates further

      Okay, this is more confusing. It looks like what happens is that when I am logged in to lemmy.today, I cannot see the newer posts via lemmy.today. When I am not logged in, I can. That means that it can’t be a federation problem, that something else is going on.

      I’ve got no idea what would cause that. I don’t have my account set up to block anything at all. I don’t think that there’s some kind of remote per-user blacklist or even if there were, any idea why I’d be on it.

      considers

      If there is some sort of blacklist, I assume that I wouldn’t be able to comment there.

      checks

      It looks like I can comment in the community there just fine, and that a comment made on lemmy.today promptly propagates to lemmy.world:

      https://lemmy.world/comment/7332440

      Hmm. Well, now I am definitely puzzled.

      If you don’t mind me asking, when you viewed the page and were successfully able to see the newer posts, were you logged in to lemmy.today? I’m half-inclined to go create a second account on lemmy.today to see whether it is also affected, but if your account is impacted as well, that’s at least one more data point, and then I’m not just creating throwaway accounts.

      My understanding is that lemmy very recently got per-user instance blocking added as a feature – kbin has had this for some time – and I am wondering if maybe something might not be working correctly related to that. I can’t imagine what else would cause the user account involved to be an input.

      Thank you for looking at this.

      EDIT: Maybe if there is something in the stack that caches generated webpages and those aren’t being invalidated, since user might be an input there, but then…no, that can’t be it, because I also don’t see the newer posts in Jerboa.

      • mrmanagerOPMA
        1·
        9 months ago

        Hi,

        I just checked and I see the same thing both logged in and logged out. Try clearing your cookies for lemmy.today completely, maybe its something weird going on with those? They changed authentication code in 0.19-something.

        • tal
          1·
          9 months ago

          My apologies. This may just be a combination of an error on my part and Lemmy not working as I had thought it worked.

          There are two retrogaming communities, one on lemmy.world and one on kbin.social. I had thought that I was subscribed to both, but I was only subscribed to the one on kbin.social. lemmy uses subscriptions to determine whether to cause posts to propagate.

          What I still don’t understand is why being logged is a factor. I definitely could see the posts when not logged in, so they made it to lemmy.today.

          I just subscribed with my lemmy.today account, made a post with another account (on kbin.social), then unsubscribed and made another post with that second account. Both posts were visible to my account.

          So I still don’t understand why being logged in is a factor for the earlier posts, but at the time that I was seeing the problem, I wasn’t subscribed, and lemmy doesn’t guarantee that propagation happens in that scenario, so I’m not going to complain about that.

          thinks

          Maybe when you browse a remote community not logged in – since it’s not possible for a guest user to subscribe – lemmy fetches the posts directly when the community is viewed, rather then having them pushed to it. Otherwise, it wouldn’t be possible to do much as a guest user with remote communities. And if nobody on lemmy.today was subscribed, that would explain the lack of popagation. That’d produce that behavior, where a guest user can see posts, but a logged-in user can’t unless they’re subscribed.

          I don’t know why different logged-in accounts would see different sets of posts, but.

          Well, I’m sorry for bothering you. Probably just user error, and me being too ready to flag something as a bug after seeing earlier federation breakage. Thanks for your time.

          • mrmanagerOPMA
            2·
            9 months ago

            Its ok, Im happy if you find a bug in Lemmy so we can report it to the developers. There are many bugs on their github issues page, so I wouldnt be surprised if you encounter some… :)