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 62, it isn't just me, June 4 it was called out - and promptly ignored while every Lemmy server was crashing on June 4... 25 days before Reddit shut down. Social hazing. (lemmy.ml)

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

10 comments fedilink hide all child comments

June 4 GitHub issue:

This has to be social hazing.

top 6 comments

sorted by: hot top controversial new old

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

June 4, social hazing is the only thing that makes any sense to me. It is July 26 now. Sunday, July 23 I used the words EMERGENCY, and they don't work on Sunday - so Monday morning the project leaders promptly removed my words "EMERGENCY" on my pull request to fix server crashes caused by TRIGGER FUNCTION hidden away by PostgreSQL and hard to read Diesel migrations!!! The evidence of all this is here, June 4.... Issue on GitHub. Not by me, I didn't open that issue.

It was pretty clear that a end-user advocate was needed. And Day 62 of watching a social hazing go on against all of Reddit and Twitter users who visit Lemmy and find it crashing and unresponsive.

It has to be hazing. I can't believe they would ignore a GitHub issue that I saw after starting to use Lemmy seriously on May 25. The servers were SCREAMING with errors, worse than any website I've used in the past 3 years. Every hour of every day, crashes. I couldn't even create a login on May 25, the sites were crashing and throwing errors so badly.

This is the response today by developers who ignored the issue since June 4 who are hazing me:

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

I started out this adventure on May 25, they ignored the June 4 GitHub issue, and by June 19 I was so alarmed at the approaching June 30 Reddit API cutoff, I created this post on the developers flagship, Lemmy.ml instance:

it's hard to believe the depth of the social hazing going on against Reddit and Twitter users who have been trying out Lemmy all year. They are off starting a new Rust front-end when there are already a dozen active front-end projects gong on - but hey, leave that GitHub issue from June 4 ignored by June 19 and hang out on Matrix Chat, avoding your own dog-food code of Lemmy where someone is begging you June 19 to start looking into PostgreSQL internal data on the Big Servers.

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

June 4 GitHub issue ignored. June 19 posting on [email protected] ignored, crashes going on constantly as described in the June 4 issue related to deletes.

And I even made more noise, again jumping up and down about delete problems with the code - which the June 4 issue was about DELETE problems in the code... all the same code pathways.

July 18, my pull request, still not merged. Enhanced testing. Imagine that, adding more testing to show flaws in DELETE. It is now July 26, they have gone home for the day.

This is the most epic public/world-wide social hazing I have ever seen played. Watching it go on for the 62 days I've been here, since May 25 when I became a daily Lemmy end-user, has been a wild ride. Like Mr. Bones Wild Ride. The end-users of Twitter and Reddit have really been hazed in a way I could never imagine without actually DRAWING ATTENTION to the poor quality of the lemmy_server DELETE logic and code... my own self, and watching it get ignored, no matter how much I said "EMERGENCY". They even removed the word "EMERGENCY" PROMPTLY on Monday, very prompt in editing out the word "EMERGENCY" in my Pull Request. It's the most amazing social hazing I can imagine.

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

We are all Just Prisoners Here, of our Own Device!

We are Rust programmed to receive, you can check out any time you like, but the DeleteAccount won't ever work, and your "full delete" promise will never replicate to all the Instances ;)

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

Please Release a FIX!!!!

My comment just now:

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

I said the same basic thing after watching them NOT release on Monday July 24 all day, first thing July 25 Tuesday I made this comment about releasing 0.18.3 as fast as possible:

load more comments