RoundSparrow to Lemmy Project Priorities [email protected] • 1 year ago

lemmy.ml GitHub Issue 2910, WHY since June 4?

-5

lemmy.ml GitHub Issue 2910, WHY since June 4?

RoundSparrow to Lemmy Project Priorities [email protected] • 1 year ago

Chat

RoundSparrowOP
link
fedilink
1•1 year ago
June 4

June 4, 2023: https://github.com/LemmyNet/lemmy/issues/2910

Lemmy Project Priorities [email protected]

[email protected]

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]

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.

1 user / day
1 user / week
1 user / month
1 user / 6 months
5 subscribers
74 Posts
207 Comments
Modlog