Lemmy Project Priorities Observations

5 readers

1 users here now

I've raised my voice loudly on meta communities, github, and created new [email protected] and [email protected] communities.

I feel like the performance problems are being ignored for over 30 days when there are a half-dozen solutions that could be coded in 5 to 10 hours of labor by one person.

I've been developing client/server messaging apps professionally since 1984, and I firmly believe that Lemmy is currently suffering from a lack of testing by the developers and lack of concern for data loss. A basic e-mail MTA in 1993 would send a "did not deliver" message back to message sender, but Lemmy just drops delivery and there is no mention of this in the release notes//introduction on GitHub. I also find that the Lemmy developers do not like to "eat their own dog food" and actually use Lemmy's communities to discuss the ongoing development and priorities of Lemmy coding. They are not testing the code and sampling the data very much, and I am posting here, using Lemmy code, as part of my personal testing! I spent over 100 hours in June 2023 testing Lemmy technical problems, especially with performance and lost data delivery.

I'll toss it into this echo chamber.

founded 1 year ago

MODERATORS

[email protected]

Day 63 - the comment delete bug fix went in (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

16 comments fedilink hide all child comments

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?

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 1 year ago* (last edited 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.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

Just now, time of this comment...

it is stunning the level of social hazing being played upon the world-wide Twitter and Reddit communities, the whole Internet. Since May 25, I have personally witnessed every single lemmy server I visit (dozens) crashing with PostgreSQL problems that the June 4 GitHub Issue 2910 called out - and lemmy.ca became so frustrated that July 22 they started running EXPLAIN on their own server data (lemmy.ml - the lead developer's production server with real-world data - crashing constantly, never seems to do this since May 25 that I've been around)... In response to lemmy.ca sharing EXPLAIN runs against real-world data on Saturday, I put together a clearly-labeled "EMERGENCY" pull request on Sunday. The lead developers of Lemmy don't work Saturday and Sunday since I came along May 25, and first thing Monday their only action about network-wide server crash fix was to edit my pull request to remove the word "EMERGENCY". I'm not kidding. - Issue 2910 is not my personal issue, and ignored since JUNE 4th (53 days and counting for a server-crash cause, identified in detail)!

here we are, well into Thursday, and they are adding more restrictions to the Lemmy project about the space vs. tab formatting correctness of SQL statements... instead of issuing an immediate 0.18.3 or 0.18.2.1 production fix!

This has to be the most sophisticated social hazing I have ever seen played against societies. This goes beyond my world travels to multiple Islamic nations as a white American post-9/11. It is wild to witness this level of social hazing against end-user populations. They KNOW the PostgreSQL TRIGGER is causing server crashes every hour of every day, but they won't make a release for the non-programmer server operators out there. And end-users, of course, can't update the servers they are using their own self. The sophistication of the social hazing is of the highest order. Mythological level.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

I think it is also note-worthy that they didn't really make a GitHub release since July 7, 0.18.2 was rush installed by many server operators, but the project started offering confusing release numbers.

As of the time of this comment, this is the GitHub status of releases:

Again, not my issue, but someone else called this out on July 12 in GitHub issue 3602: https://github.com/LemmyNet/lemmy/issues/3602

load more comments