Lemmy Project Priorities Observations

5 readers

1 users here now

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.

founded 1 year ago

MODERATORS

[email protected]

-3

I was wrong about PostgreSQL priority in Lemmy. "Dr. Strangelove or: How I Learned to Stop Worrying and Love the Bomb" comes to mind (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

I clearly have failed to understand how integral to the social identity of the Lemmy community server crashes have become. The "little guy taking on Reddit and Twitter" for 4 years.

I have personal DB2 and PostgreSQL experience in production "mission critical" applications. I should have seen that for 4 years the developers had all the social experience of social -- like Hollywood films or Music Industry labels.

My brain damaged mind was WORRIED about the June 4, 2023 GitHub Issue 2910 so much that I started organizing [email protected] on June 13 after lemmy.ml upgraded hardware and I saw more crashes.

It's cultural. I should not have looked into the kitchen and let my personal DB2 and PostgreSQL memories haunt me that this was "production" system crashing.

I fucked up, and I've wasted 2 months in WORRY about the Reddit API deadline the first month, and now the Elon Musk X rename, and I admit - I didn't get the social experience the developers have for 4 years working "social communities".

I study religions, I should have interpreted it using that hat instead of "production PostgreSQL or DB2".

It's been a bad year for me, and I've made several big mistakes. I had to drink to clear my mind for the first time this year since New Years. Those memories of running "mission critical" servers had to be shut off, stop applying them to socially-driven Lemmy culture. The developers have been running this site for 4 years, they know modern audiences and what works - I've just been pissing into the wind with the wrong interpretation :(

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago

So, this is a new phase of my brain damage experience.

I previously would have caught on to Elon Musk and realized what the Lemmy developers expectations were. Elon knows how to build a loyal following, people follow all his organizations.

My brain damage experience of the past 2 months was to not use Elon as an experience, not to see how ChatGPT was the biggest new success ever (while constantly crashing), and to be haunted by 2009 memories of running PostgreSQL in production - and haunted by 1992 memories of DB2 in production, etc. My brain damage did not let me see the "Music Industry" and "Film Industry" way of doing things.

I would be worried about how a musician runs their computers, or how a mosque runs their computers. It's an entirely different Interpretation / mindset. And I brought the WRONG ATTITUDE.