For developers so concerned to keep you “on topic” and “not to bring up things outside the scope of their issue” on GitHub… they sure do not seem to care about the technical reputation of Lemmy as a platform throwing errors all over the front page, app clients, and the delivery of messages, meeting their own promise of deleting (“full delete”), and their own promise of “high performance”. Crashes caused directly by the Account Delete are in fact what the fixes I pull requested on Sunday are intended to address. Very concerned with how a human being interacts on GitHub comments, they are very concerned you use Matrix to talk to other developers (and ignore Lemmy postings about server crashes / constant SQL related failure errors), but not at all concerned about the unwashed non-developer masses of people who try to use Lemmy and get crash errors.

I still think it’s a form of social hazing being played on newcomers. Some kind of anti-establishment social hazing, to watch for over 2 months as flocks of users come from Reddit frustrations and Elon Musk “X” renaming - to not have any sense of priority in fixing the SQL with server crashes. Tuning off aggregate counting PostgreSQL triggers would have been an immediate crisis mitigation. The developers know the 4 year history of all the code and how those April 2022 TRIGGER functions can be removed, but they seem to want the hazing social approach to play out on the newcomers from Reddit, Twitter, etc.