The fix of comment delete not making it to 1498 subscribed servers out of 1500 went in. I’m working on testing to confirm the same for moderator remove and other actions (testing did get several merges this week, not sure where problems like feature/sticky in a community for all 1500 servers go).

I am contemplating if some kind of existing-data cleanup could be done for all the comment deletes that never got sent out. If an admin API could be added to trigger a undelete then delete again if comment = local. Crawl them. Probably too many other fixes.

Will the server-crashing fix go in before the weekend?

  • RoundSparrowOP
    1·
    1 year ago

    Yesterday, Day 62, comments and posts I made on this community…

    The striking thing about Lemmy is that the developers have pushed back on anything I would consider “battle hardened”, “robust”, “fault-tolerent”, “defense against”, “stress testing”. May 25, day 1 of my Lemmy journey, all the servers were crashing and the June 4 GirHub Issue 2910 spelled out the bomb inside Lemmy PostgreSQL TRIGGER: https://github.com/LemmyNet/lemmy/issues/2910

    I couldn’t believe that the June 4 issue was being ignored, the words made about the PostgreSQL TRIGGER logic-bomb were very clear to developers/project leaders: "Is causing performance to blow out. Its nonsensical, and doesn’t work as intended. ". Again, by Monday June 19 I was up in arms with the approaching June 30 Reddit API cut-off date.

    It is the most committed social hazing of the entire USA technology community, Reddit and Twitter, that I could imagine. Developers who avoid eating their own Dog Food, using Lemmy, who hang out on Matrix Chat - while watching a June 4 GitHub issue about server crashes go ignored. It has been one wild ride to experience this social hazing.