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

2023-09-03

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

The only instance with significant creation activity that isn’t all bot content… had to resort to cloudflare due to the data performance… and now the problems with that solution have started to be taken on… https://lemmy.world/post/4366376

Chat

RoundSparrow @ BT@bulletintree.comOPM
link
fedilink
arrow-up
1·
10 months ago
It is the squandered experience of over 4 years of development that I’ve witnessed the most… the people who knew how to do the required changes to scale the app fed the problem apathy.

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.

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