As per this post, it seems Lemmy World is having federation issues. I’ve had some of my posts and comments get suspiciously low response, so I’ve looked into it and it turns out that many of them aren’t showing on other instances.

Here’s an example: my Payday 3 post is only visible on Lemmy.world:

Meanwhile, in other instances, it doesn’t show up at all:

It’s not clear if this issue is exclusive to this instance but I thought I’d give people a heads up. I reposted and now it showed up in other instances. If you feel like you’re getting no response from other communities, check on another instance if your content is visible, otherwise repost it.

  • thayer@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    ·
    2 years ago

    It isn’t just Lemmy.world, and isn’t limited to v0.17 either. Lemmy.ca, which has been running v0.18 for days, is also not seeing a lot of federated content, nor accurate community subscription counts from other instances, including lemmy.ml and others running v0.18. I’m posting this from my .world alt because .ca is showing zero comments in this thread.

    There have been several not-so-friendly comments made about the issues by someone in !lemmy_administration@lemmy.ml, calling out the site admins of .world and .ml for not sharing their server logs, and the overall silence on the issue. The user’s concerns are genuine, but I don’t agree with their behaviour.

    I suspect the devs were/are completely overwhelmed by the mass influx of redditors these past two weeks. I assume someone is looking into it, but frankly I wouldn’t blame anyone if they chose to step away for a few days. I think a lot of folks (particularly “the masses”) forget that these are largely volunteer efforts, by people with day jobs.

    • Ruud@lemmy.worldM
      link
      fedilink
      English
      arrow-up
      25
      ·
      2 years ago

      Thanks for your reply. This site isn’t even a month old and the user growth is spectacular. Lemmy hasn’t ever been tested with these amounts of users.

      I’m sure the devs are doing their best in getting it all more performant. Meanwhile the team at lemmy.world is trying to get a grip on what’s happening with federation. There’s not much to be found in logs, anyone who can help troubleshoot this let us know. The only real adjustable setting is the federation workers. We’ve apparently either set that too high or too low. I’m gonna set the log level back to info on the hopes we get some queue stats…

      To be continued

      • thayer@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 years ago

        No worries, and I completely sympathize with the situation. My hat is off to you site admins, and the lemmy devs, for keeping things afloat these past couple of weeks, often at great expense of both time and money. I am confident that all of these kinks will be ironed out in the coming months, and in the meantime, I am happy to have a few alts to hold me over.

      • danc4498@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 years ago

        Back in my day 1 month old sites had 0% downtime and no reported glitches. 1 million daily active users! There’s no need for beta software either cause 2.0 was always the perfect release.

        Those were the days!

      • sadreality@kbin.social
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        2 years ago

        Thanks for the response.

        Most people here know we are in alpha. Shit will happen. Gonna take a while to get these systems ready to take over reddit.

      • deweydecibel@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 years ago

        So to be clear, we’re fairly certain this is a technical issue and not because of something other instances are doing?

  • ericjmorey@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 years ago

    Lemmy.world is definitely having federation issues. Lemmy in general is having a lot of federation issues, but it looks like lemmy.world is being effected more so due to the number of accounts and activity on lemmy.world in combination with different versions of lemmy handling messages a bit differently with different implicit assumptions.

  • Bobby Bandwidth@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    2 years ago

    Correct me if I’m wrong but .18 lemmy doesn’t support captcha, so lemmy.world is waiting for a patch before updating so we don’t get flooded with bots.

    Edit: fixed typo

  • static@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    2 years ago

    Workaround, I had to do the same on kbin.

    Editing your comment triggers another sync, often an edit will make the comment or post synchronise to all other instances.

  • RCMaehl [Any]@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 years ago

    I believe this is a side effect of the 0.17 vs 0.18 split which unfortunately wasn’t backwards compatible. Once 0.18.1 rolls out with readded captcha everything should be hunky-dory again.

  • dragontamer@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 years ago

    To add some specificity to this:

    I’ve been unable to post to !arduino@lemmy.ca or !avr@lemmy.ca successfully. And the comments seem to be failing to load at all.

    Here’s to hoping its the .18.x vs .17 issue. But I figured I need to post an official report of my problems somewhere, and this topic seems the most applicable location.

    I’ve also been “Subscription pending” on !avr@lemmy.ca for… at least 20 minutes now. Suspiciously long times to get that resolved.

    • dragontamer@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 years ago

      5 hours later, I’m still “Subscription pending”. I dunno if this is related to the issues, but I figure I should document the problem here.