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.