2
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Jun 2023
2 points (100.0% liked)
Asklemmy
43401 readers
689 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
There are other issues with comments not syncing across instances that I am seeing with my community. Comments and posts from Lemmy.ml cant be seen by lemmy.world. It didn't used to be like this prior to the reddit blackout. I think the amount of traffic and the various issues with BE 0.17.4 are likely to blame. I think some Lemmy instances are even still on version 0.17.3 because I believe 0.17.4 has bugged Hot and Active scores, among other issues.
The Lemmy devs just posted a big blog post where they said they are working on the next version (rumored to be 0.18) which is going to bring some substantial changes to the codebase.
https://join-lemmy.org/news/2023-06-17_-_Update_from_Lemmy_after_the_Reddit_blackout
Tldr: "At the moment we are urgently working to solve major issues, such as optimizing slow database queries, ripping out the inefficient websocket API, and fixing a major security vulnerability"
So I'm going to chalk up all these issues under known bugs that will be fixed in the next update or worked out over time.
Fingers crossed they fix it on their next release. Thanks for the info!