I’ve made some comments and posts on a community on another instance, and I just realized they’re not showing up on the other instance at all. Eg. I made this comment on !suomi@sopuli.xyz, but it’s not visible on the original instance. The same has happened with all comments and posts I’ve made on sopuli.xyz for the past few days, which leads me to believe it’s due to sopuli upgrading to 0.18

edit: looks like some of my comments on 0.18 communities have gone through, but none of my posts have. Eg. this post is not visible on !science@mander.xyz

edit 2: return of the edit: actually no, none of my comments on 0.18 instances show up on the instances themselves, I just thought some did since they had at least one upvote but they might just be from people who were eg. browsing through Beehaw or another 0.17 instance

edit 3: revenge of the edit: turns out this isn’t a 0.18.x problem but a wider Lemmy problem due to the backend and design simply being unable to scale: https://github.com/LemmyNet/lemmy/issues/3101

edit 4: the new edit:

https://github.com/LemmyNet/lemmy/issues/3435#issuecomment-1615977831

It should improve a lot as more of the network upgrades to 0.18.1 - messages sent from 0.17.4 are currently disregarded if they’re older than 10 seconds (which is one of several causes for federation issues) and this lifetime is significantly increased in 0.18.1!

edit 5: the edit strikes back: unfortunately 0.18.x doesn’t seem to have helped too much, and it also breaks outbound federation with non-Lemmy services at least to some degree

  • Yeah, I’m kind of surprised Lemmy is struggling to scale considering the claims of the codebase. If 2000 monthly users can kill a server, I honestly don’t think the server is built well.

    Hacker News runs on a potato can and services many many more people everyday