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.
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 [email protected], 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.
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
So to be clear, we're fairly certain this is a technical issue and not because of something other instances are doing?
It's almost certainly technical issues relating to scalability. The user I mentioned above has created a community for tracking several performance issues that are likely impacting the platform now that user and post counts have increased exponentially.