this post was submitted on 26 Jun 2023
144 points (97.4% liked)

Lemmy.world Support

3234 readers
131 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

To open a support ticket Static Badge


You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.


Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world



founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] krayj 4 points 1 year ago

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.