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.

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

Just clicked on a Futurama related post on Lemmy.world front page, it opened wtih this MLB Game Thread as content instead of what I clicked on. **This is happened more than once. Previously I thought I derp clicked on the wrong item **

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.

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.

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.

That's pretty much what I yesterday called the lemmy.world bubble.

To add some specificity to this:

I've been unable to post to [email protected] or [email protected] 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 [email protected] for... at least 20 minutes now. Suspiciously long times to get that resolved.

If it was reposted and worked that’s not a federation issue right? Could it be that world isn’t on .18 yet?

There should be a fix in a day or two, there was an issue with captcha to my understanding.

I'm very new to Lemmy and have already been experiencing this problem just testing how commenting to a federated community on another server works. It doesn't/hasn't worked for me yet in controlled testing. I've been assuming it was a problem with the other lemmy instance where the community is created/hosted but now I'm rethinking that assumption.

Usually, not assigning sufficient resources at a workload just causes the backlog queue to get longer, but in the case of lemmy it seems to result in some items never getting processed at all. That's an odd behavior for a backlog to have.

I've had difficulties with responding or commenting on posts on federated servers. Comments work just fine if I'm on this instance, but threads on others it just never posts.

I got a report earlier that my community wasn't showing up on https://browse.feddit.de earlier as well, but it's back now. I'm not sure how it works but I assume it's related.

This is why its a bad idea to have massive servers