Day 32 again - and why I am so frustrated with the Lemmy project ignoring lost data and peer replication

@adminsagMA to Lemmy Project Priorities Observations • 1 year ago

Over 20 years ago I was building social media messaging systems with an e-mail MTA.

e-mail MTA’s send messages back to senders that their messages never got delivered. And Lemmy to Lemmy does no such thing. If you send a reply to someone, no “bounce” message comes if delivery fails.

It’s sad to me to think users are there replying to each other like two ships passing in the night, no idea that the person even responded.

The queue not being saved on server shutdown and just tossing out undelivered messages to peers is something I never imagined. Again, e-mail systems in 1993 didn’t just throw out delivery retry queues on a server reboot.

You must log in or register to comment.

Chat

Lemmy Project Priorities Observations

!lemmy_project_pri@bulletintree.com

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: !lemmy_project_pri@bulletintree.com

I’ve raised my voice loudly on meta communities, github, and created new !lemmyperformance@lemmy.ml and !lemmycode@lemmy.ml 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
98 subscribers
74 Posts
250 Comments
Modlog