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 64 - my June 24 request to have developers please document the obfuscated SQL TRIGGER logic in the Rust lemmy_server project.... (lemmy.ml)

submitted 1 year ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

June 24, a full week before the Reddit API delay and my June 13 post in [email protected] about paying more attention to the PostgreSQL code they had put into Lemmy Server that was causing constant crashes as called out June 4 by GitHub issue 2910

The effort developers have made to DISCOURAGE focus attention on the PostgreSQL TRIGGER code: https://github.com/LemmyNet/lemmy-docs/issues/233

Removing "emergency" in the fix first-thing Monday after not working on a weekend was how out-of-the-way the project leaders have been to AVOID the TRIGGER code getting scrutiny and fixed since June 4 call-out in issue 2910

top 2 comments

sorted by: hot top controversial new old

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

June 24

One week before Reddit API shutdown

The social hazing to keep developers from studying the TRIGGER logic in PostgreSQL.... it truly is amazing the labor and effort made to haze the entire social media community to the wildest mythological depths. Reddit API is shutting down in 7 days, it's June 24, discourage PostgreSQL study by the Lemmy communities! Elon Musk is renaming "Twitter" to "X" and getting tons of press about alternates to Twitter.... edit out "emergency" about easy PostgreSQL TRIGGER fixes someone made for you on Sunday when you aren't working. Wild.

[–] [email protected] 1 points 1 year ago

Very first thing Monday, after having days off work the weekend, a fix pull-request is waiting for them created on Sunday.... this is what project leads felt was the most important thing to do with SQL TRIGGER statements crashing server.... edit out the word "emergency":

The effort developers have made to DISCOURAGE focus attention on the PostgreSQL TRIGGER code: https://github.com/LemmyNet/lemmy-docs/issues/233

load more comments