RoundSparrow @ BT@bulletintree.comM to Lemmy Project Priorities Observations@bulletintree.com · 11 months ago

Watching Beehaw, established more than a year before June 4, 2023 - crash all June - I really regret I took the wrong approach, a crisis of faith it seems :(

9

2

Watching Beehaw, established more than a year before June 4, 2023 - crash all June - I really regret I took the wrong approach, a crisis of faith it seems :(

RoundSparrow @ BT@bulletintree.comM to Lemmy Project Priorities Observations@bulletintree.com · 11 months ago

9

June 4, 2023 is when I felt I had to get involved. And June 8, 2023 is when I crated my own testing-focused experimental Lemmy install that compiled Main from GitHub source and ready to test the changes I thought were surely going to come to the SQL because of GitHub issue 2910. I wanted to test the code that that developers who had been working and running lemmy.ml for over 4 full years - would surely address. It was June 4 with Issue 2910, the June 30 Reddit API cutoff deadline countdown was well under way. Lemmy.ml put in major hardware upgrades on June 13, 2023 - and I was puzzled why such an easy 2 or 3 hour fix for Issue 2910 wasn’t put in… but I still had hope that everyone would see the pending countdown to June 30 API deadline and a fix could go in within 10 days - by June 23… for some slack time before June 30…

Watching Beehaw, up and running for 17 months on Lemmy - crashing constantly… I thought, surely the developers were seeing Issue 2910 happening over there… but June 28 came, June 29 came, June 30… nothing. With 4 years of experience on the Rust code base and such, they were the ones to fix Issue 2910… but from June 4 to June 30, it just didn’t happen.

Chat

RoundSparrow @ BT@bulletintree.comOPM
link
fedilink
arrow-up
2·
11 months ago
have a good weekend

Lemmy Project Priorities Observations@bulletintree.com

lemmy_project_pri@bulletintree.com

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.

1 user / day
1 user / week
1 user / month
1 user / 6 months
1 local subscriber
97 subscribers
74 Posts
216 Comments
Modlog