Day 34 - since independently-run production servers have been failing me for 34 days, every single day, DRASTIC changes to the API - return failure counts to that error path

RoundSparrow@lemmy.ml to Lemmy Project Priorities Observations@bulletintree.com · 1 year ago

A user on 0.18.1-rc6 on Lemmy.world reported an upvote error.

I think the API should have a counter of the error and that the API should return the count. If it isn’t saved, fine, but maybe return system uptime on errors too.

This puts the power more in the hands of clients instead of server operators to know what is gong on internally with the Lemmy servers that are falling flat on their face performance-wise in the 0.18.1 era.

You must log in or register to comment.

Chat

Lemmy Project Priorities Observations@bulletintree.com

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.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

0 users / day
1 user / week
1 user / month
1 user / 6 months
0 local subscribers
0 subscribers
21 Posts
0 Comments
Modlog

mods:
adminsag@bulletintree.com