Lemmy Project Priorities Observations
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.
view the rest of the comments
Its' really hard to not conclude that there are people attracted to Lemmy because it is so constant-crashing unstable and so feature lacking compared to Reddit.
It gives them power, their instance importance, that errors in SQL update statements hit 1500 rows of site_aggregates - and the Rust community in general seems to ignore that Lemmy is written in Rust and how to make the best of fixing SQL issues in Diesel, etc.
Someone against multi-reddit / multi-community coding because they want to keep away the unwashed masses of Reddit.... instead of adding features to better acclimate users to their communities before posting/commenting, they want the entire Lemmy code base for all instances to be held back on a new feature to making switching Playlists more difficult.
It just doesn't seem to be in their imagination that the feature could have been coded 2 years ago... and how you manage the problem of engaging the audience of your community is one to address directly... not by trying to run off programmers trying to add obvious features to the code.