Just like they do not work on weekends, and first thing Monday their priority on GitHub was to EDIT a pull request to remove the word "EMERGENCY" (server crashes) and then go on to add low-importance new features all week.
PostgreSQL related crashes and mistakes in the Lemmy Project back-end are a pattern, as June 4 2023 GitHub issue 2910 clearly documents - which sat ignored for months.
As fast as possible, closing and brushing under the rug GitHub Issue 3756 that was field-testing of the Lemmy 0.18.3 release (there was also NO CALL or Announcement by the project leaders to test 0.18.2 or 0.18.3 - there is no quality assurance on the project from all that I have seen).
If the developers of the program do not grasp PostgreSQL - why constantly cover it up? Why brush SQL problems under the rug? It's the core of Lemmy, where all the data is stored.
I have some new books on order to better understand social hazing.
From Scratch Installs
It is the long-term Linux and operating system experienced people who are gong to do "From Scratch Install". The people who know how to watch disk I/O, CPU usage of PostgreSQL, etc. And now that is the group who will be hit bu this 0.18.3 upgrade that was not tested for "From Scratch" installs. My reply on GitHub:
For the past 2 months, I've seen the project leaders do everything they can to encourage more and more newcomers to install new servers, new Instances of Lemmy. But all this has done is make PostgreSQL TRIGGER bombs from bots creating thousands of accounts while Captcha was turned off by project leads. The crashing servers, PostgreSQL going to 100% CPU and causing everything in the site to error out - has been sitting there since June 4 with Issue 2910.
Now there are so many abandoned dead-servers out there because people have given up. Lemmy.ml stopped creating new users and communuities. The project leaders kept suggesting that the solution to scaling was to do all the labor and overhead of installing 1000 new instances in June ad July, new servers to Lemmy. But all along the scaling problem has been brushing PostgreSQL under the rug by ignoring GitHub Issue 2910 and hanging out on Matrix Chat ignoring Lemmy's own communities like [email protected] and [email protected] and [email protected] - eat your own dogfood, use Lemmy to discuss Lemmy's largest server-crashing data-loss technical problems.
Now Lemmy presents newcomers with 1000 poorly run and managed servers, many of which shut down without any means for users to keep their old posts and comments. Look at the cleanup labor that has only just started: https://sh.itjust.works/post/1823812
Brushing PostgreSQL issues under the rug and hanging out on Matrix Chat, avoiding Lemmy technical discussions on Lemmy platform....
The levels of social hazing being done against the social media societies of Reddit, Twitter, etc is on a mythological scale.