With 0.18.2, 0.18.3 there were changes in the behavior of comment sorting and delete / remove behavior. It is entirely possible that behavior changed, intentional or otherwise.
There is a !test@lemmy.ml community where you could create comments, do some screen shots before and after delete.
The real war is hate media memes and messages that trickle down to those obedient to voices from the clouds, electric voices these days. In the old days, books that said burning bushes gave out signals.
Keep in mind with 0.18.3 there is a new "dead server" check that cuts off communication that won't show up on the block list. There have been reports in !fediverse@lemmy.ml recently that this has caused some issues. notable posting: https://lemmy.ca/post/2626714
BE: 0.18.0
that isn't that long ago, as in July 1 Reddit API app deadline
NASA statement this week opened my mind up to non-human intelligence on Earth. I started looking into when dinosaurs were really taken seriously, and it wasn't until 1800. Think about how many humans ignored that evidence. Maybe some intelligence evolved on Earth and had brains that found natural physics and chemistry more teachable than our learning in school classrooms, found ways to open dimensions and just left Earth for some place better, but still comes back to check us lower species, ha.
But each additional row in site_aggregates table was causing the instability itself. The SQL code had major flaws. Adding more servers actually made Lemmy crash more.
docker compose down &&
Looks like the & parsing in code blocks is another bug in 0.18.3 like the post title one. I'll add your comment to the GitHub issue.
Thank you for sharing.
I’m finding issues with communities not loading posts, comments or general sync issues.
Lemmy's Rust code uses an ORM called Diesel that masks the SQL statements and you really have to watch the PostgreSQL server independently to verify that the SQL isn't doing wild things like loading thousands of records when you only needed 3. Just today people are finally sharing some information out of the big servers (lemmy.world) as to what PostgreSQL side says is actually happening. Hopefully the biggest mistakes are going to get cleaned up quickly.
I have, weeks ago.
I did share a link to GitHub, is that not good enough or something? Here is a screen shot for you.