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
My regrets compounded when I sort of forgot about https://github.com/derivator/tafkars like everyone else did by early July... a month after it had been created... and it would have been a way for me to channel my skills instead of hoping the situation with Issue 2910 would turn around quickly. Even after 30 days, a few-hour fix to 2910 hadn't been put in.
Did I get caught up in all the "Fuck Spez" negativity of Lemmy community? Beehaw was the most positive and had been up for 17 months with their positive approach. Did I get sucked into the hate of Reddit and hate of Elon Musk emotions and not see it?
I really regret when I go back and see the June 7 creation of https://github.com/derivator/tafkars - that I didn't either think of it myself or jump in with contributions to a fully independent project that would offer a solution that didn't require the two entrenched developers of lemmy_server to change their pace or focus. Beehaw was on fire, and tafkars project would at least have been a way to view all this from an API perspective.
Did the negativity of hating Spez and corporate power - even the massive hate that everyone was screaming on Lemmy platform about Zuckerberg and "Threads" coming along on July 5... did it get into my head?
I should have been reading my Finnegans Wake and keeping my mind clear. The Reddit HiveMind clashes, the Lemmy platform HiveMind hate towards Threads and Twitter....
Beehaw is like a lighthouse in all the hate-oriented surges of people motivated by anger and hate, and I see now I lost my way in the competing waves of hate-focused HiveMind reactions.
This is a test comment to see how front-end gets notification.
do you get this comment reply?
https://github.com/derivator/tafkars
This API proxy approach could be useful for more intelligent rate-filtering than built-in Lemmy has, API redirection for specific calls, and even the basis for spam filtering. I haven't seen people remark about the lack of spam on lemmy. On Reddt, I've seen routine bots hit communities with t-shirt selling spam, etc. I wonder if other parts of the federated network have had to implement spam filtering.